UX Metrics Skill

UX Metrics SkillHelps you choose and apply the right metrics at every stage of design work. The skill covers Attitudinal, Behavioral, and Performance metrics, and connects each one to the right stage, the right audience, and the right business outcome.Download the skill file and drop into your LLM chat., or install just this skill through your terminal:npx skills add https://github.com/zurb/glare-skillsWhat you getCoverswhat metrics are, why they matter, and how to use themIncludes Behavioral, Attitudinal, and Performance MetricsTeaches your AI to map design impact and build a measurement systemWorks with Claude Code, Cowork, and CodexExample OutputWhat the UX Metrics Skill DoesMost teams measure too late or measure the wrong thing. They track monthly active users and app store ratings — numbers that go up without telling anyone what to build differently. Or they wait for post-launch analytics that arrive after the sprint is already over.The UX Metrics skill fixes that by helping teams pick metrics with purpose before collecting any data.Every metric belongs to one of three types. A good measurement plan needs all three.TypeWhat it measuresExamplesAttitudinalHow users feelTrust, Satisfaction, Desirability, ConfidenceBehavioralWhat users doCompletion, Comprehension, Effort, EngagementPerformanceHow well the experience worksTime on Task, Error Rate, Drop-off Rate, RetentionUsing only one type distorts the picture:High satisfaction with low completion means users like the idea but cannot finish the taskStrong performance with low engagement means the system works but nobody caresHigh engagement with low trust means users are active but unconvincedAll three together tell the complete story.What It ProducesThe skill produces a clear metric plan for a product or workflow.The plan shows:which three metrics to track, one per typewhether each metric is a leading or lagging indicatorwhich stage each metric belongs to: predictive, proxy, or analyticsany mismatches to watch for between metric typesExample output for a mobile banking dashboard:FieldOutputAttitudinal MetricTrust: do users feel confident the balance shown is accurate?Behavioral MetricCompletion: can users locate transaction history within two taps?Performance MetricTime on Task: how long does it take to find and act on a recent transaction?Leading IndicatorComprehension score from prototype testing, collected before launchLagging IndicatorSession abandonment rate, confirmed after launchMismatch to WatchHigh satisfaction with low completion means users feel good about the app but cannot finish the task. Fix the flow before assuming the experience is working.How to Use ItThree common ways to get value from this skill.Fix a broken metric plan"We are updating our mobile banking dashboard and our current metrics are monthly active users and app store rating. Using the glare-ux-metrics skill, tell us whether these are the right metrics to track and recommend a replacement trio — one attitudinal, one behavioral, one performance — that would actually guide our next design decision."Best for: auditing an existing metric plan, sprint kickoffs where the success criteria feel vague, any situation where the team is measuring activity instead of outcomes.Choose the right metric for the right stage"We are about to run usability testing on our mobile banking dashboard before launch. Using glare-ux-metrics, help us identify which metrics to collect now as leading indicators, which ones to collect post-launch as lagging indicators, and how to use each to make a decision at the right time."Best for: pre-launch research planning, setting up a test with clear success criteria, building a measurement timeline across a product sprint.Diagnose a confusing result"After our last round of testing, satisfaction scores were high but task completion on the transaction history flow dropped to 61%. We are not sure what to do with this. Using glare-ux-metrics, explain what this mismatch means and which metric we should add to diagnose the root cause."Best for: making sense of conflicting data, preparing a findings summary for a design review, deciding which metric to add before the next round of testing.How UX Metrics Connect to the Rest of GlareThe UX Metrics skill works across the full Decision Map, not just inside Define.InDefine: choose the metrics that will prove a user need is being metInMeasure: use metrics to write falsifiable hypotheses and evaluate findingsInFocus: use a shared metric to compare versions fairlyInLead: connect Design KPIs to Product KPIs and Business KPIs in a chainA metric chosen at the Define stage becomes the signal that travels all the way to a business outcome in Lead. The skill is most powerful when used early and kept consistent across the whole project.