[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0MNVNXS9WN67BZ2C7AY3H":3,"skill-same:01M7F0MNVNXS9WN67BZ2C7AY3H":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F0MNVNXS9WN67BZ2C7AY3H","ux-metrics-measurement",null,"UX measurement: HEART framework, SUS, UEQ, SUPR-Q, task success and time-on-task metrics, A\u002FB testing statistics, AI-specific metrics, and design system ROI. Use when defining UX KPIs, building a measurement plan, interpreting a usability score, or proving UX impact.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fux-metrics-measurement\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: ux-metrics-measurement\ndescription: \"UX measurement: HEART framework, SUS, UEQ, SUPR-Q, task success and time-on-task metrics, A\u002FB testing statistics, AI-specific metrics, and design system ROI. Use when defining UX KPIs, building a measurement plan, interpreting a usability score, or proving UX impact.\"\nallowed-tools: Read, Grep, Glob\n---\n\n# UX Metrics & Measurement\n\n## Measurement Philosophy\n\nMeasure what matters, not what is easy. Vanity metrics (page views, downloads, time on site) tell you what happened but not whether the experience was good. Meaningful UX metrics connect user behavior to user satisfaction to business outcomes. Every metric in the system should answer one of three questions: Is it usable? Is it useful? Is it desirable?\n\n### The Measurement Hierarchy\n\n1. **Behavioral metrics** (what users do) are more reliable than **attitudinal metrics** (what users say).\n2. **Task-level metrics** (can users accomplish goals?) matter more than **session-level metrics** (how long did users stay?).\n3. **Leading indicators** (early signals of success\u002Ffailure) are more actionable than **lagging indicators** (outcomes measured after the fact).\n4. **Benchmarked metrics** (compared to industry or historical baseline) are more meaningful than **absolute metrics** (numbers without context).\n\n## HEART Framework (Google)\n\nGoogle's HEART framework maps product goals to signals to metrics across five dimensions: **Happiness** (CSAT, NPS, SUS), **Engagement** (DAU\u002FMAU, feature adoption), **Adoption** (activation, time to first value), **Retention** (churn, return rate), and **Task Success** (completion, time on task, errors).\n\n### Goals-Signals-Metrics Process\n\nFor each product area, work through three columns:\n\n1. **Goal:** What is the desired user outcome? (\"Users can find relevant products quickly\")\n2. **Signal:** What user behavior indicates progress toward the goal? (\"Users complete searches and click results\")\n3. **Metric:** How do you quantify the signal? (\"Search-to-click rate, average time from search to product page view\")\n\nThis process prevents metric selection from being arbitrary. Every metric traces back to a user goal.\n\n## System Usability Scale (SUS)\n\nThe most widely used standardized usability questionnaire. Ten questions on a five-point Likert scale, producing a score from 0-100.\n\n### Scoring and Interpretation\n\n- Raw score calculation: alternate positive\u002Fnegative items, subtract\u002Fadd from scale anchors, multiply by 2.5.\n- Average SUS score across studies: 68 (this is the 50th percentile, not a passing grade).\n- Adjective scale mapping: \u003C50 = Awful, 50-67 = Poor to OK, 68 = Passable, 68-80 = Good, 80-90 = Excellent, 90+ = Best Imaginable.\n- Grade scale: \u003C60 = F, 60-69 = D, 70-79 = C, 80-89 = B, 90+ = A.\n- Percentile benchmarks: 68 = 50th, 74 = 64th, 80 = 85th, 86 = 96th.\n\n## Choosing an Instrument\n\n- **SUS** (10 items): post-study, baselines, comparisons, longitudinal tracking. Perceived usability only; a thermometer, not a diagnosis.\n- **UMUX-Lite** (2 items, r = 0.83 with SUS): in-app pulse checks where survey fatigue matters.\n- **UEQ** (26 items, six dimensions): when hedonic qualities matter alongside pragmatic ones.\n- **SUPR-Q**: web-only percentile rank against 200+ sites.\n- **Task metrics** (success, time on task, errors, lostness) and **behavioral analytics** (funnels, cohorts, retention) for what users do; **A\u002FB or sequential tests** to prove causation.\n\n## AI-Specific UX Metrics\n\n- **Trust calibration score:** How closely does user confidence in AI output match actual AI accuracy?\n- **Appropriate reliance rate:** Percentage of times users correctly accept accurate AI outputs and correctly reject inaccurate ones.\n- **AI feature adoption:** Opt-in rate, prompt frequency, feature retention over time.\n- **Correction frequency:** How often users edit or override AI outputs.\n- **Time saved:** Measured difference in task time with AI versus without.\n\n## Routing\n\n- **Choosing and scoring a framework** — HEART in depth, SUS scoring and limitations, UEQ, UMUX-Lite, SUPR-Q, task and behavioral metrics, NPS\u002FCES\u002FCSAT in a UX context, analytics metric design, experimentation (sample size and MDE table, significance, duration, peeking and multiple-comparison errors, Bayesian vs frequentist, sequential testing, guardrails) and benchmarking, UX ROI, design system metrics and ROI, maturity models, dashboards: read `references\u002Fmetrics-frameworks-compendium.md`.\n- **Measuring an AI feature** — AI metric taxonomy, affective metrics, cross-platform measurement, experiments that survive non-determinism, continuous discovery, atomic research, AI experiment pitfalls: read `references\u002Fai-ux-metrics-experimentation.md`.\n\n## Cross-Referencing\n\n- For heuristic evaluation methodology, reference `nng-ux-heuristics`.\n- For research methodology, reference `ux-research-methods`.\n- For AI-specific metrics detail, reference `ux-metrics-measurement\u002Freferences\u002Fai-ux-metrics-experimentation`.\n- For design system metrics detail, reference `design-systems-architecture\u002Freferences\u002Fgovernance-scaling`.\n- For usability testing protocols that produce metrics, reference `ux-research-methods\u002Freferences\u002Fresearch-protocols`.\n- Design system maturity rubric and adoption thresholds: `design-systems-architecture`\n- Hallucination rate and confidence calibration metrics: `agentic-ai-generative-ux`\n- Notification effectiveness metrics: `performance-states-patterns`\n\n## Key Sources\n\n- Google HEART Framework (Rodden, Hutchinson, Fu)\n- Sauro, J. & Lewis, J.: \"Quantifying the User Experience\"\n- MeasuringU: 48 UX Metrics (2025)\n- Brooke, J.: SUS — A Quick and Dirty Usability Scale\n- Schrepp, M.: User Experience Questionnaire (UEQ)\n- Frontiers in Computer Science: UX Measurement Frameworks\n- Sparkbox: Design System ROI Research\n- NNG Group: UX Maturity Model, DesignOps 101\n","# UX Metrics & Measurement\n\n## Measurement Philosophy\n\nMeasure what matters, not what is easy. Vanity metrics (page views, downloads, time on site) tell you what happened but not whether the experience was good. Meaningful UX metrics connect user behavior to user satisfaction to business outcomes. Every metric in the system should answer one of three questions: Is it usable? Is it useful? Is it desirable?\n\n### The Measurement Hierarchy\n\n1. **Behavioral metrics** (what users do) are more reliable than **attitudinal metrics** (what users say).\n2. **Task-level metrics** (can users accomplish goals?) matter more than **session-level metrics** (how long did users stay?).\n3. **Leading indicators** (early signals of success\u002Ffailure) are more actionable than **lagging indicators** (outcomes measured after the fact).\n4. **Benchmarked metrics** (compared to industry or historical baseline) are more meaningful than **absolute metrics** (numbers without context).\n\n## HEART Framework (Google)\n\nGoogle's HEART framework maps product goals to signals to metrics across five dimensions: **Happiness** (CSAT, NPS, SUS), **Engagement** (DAU\u002FMAU, feature adoption), **Adoption** (activation, time to first value), **Retention** (churn, return rate), and **Task Success** (completion, time on task, errors).\n\n### Goals-Signals-Metrics Process\n\nFor each product area, work through three columns:\n\n1. **Goal:** What is the desired user outcome? (\"Users can find relevant products quickly\")\n2. **Signal:** What user behavior indicates progress toward the goal? (\"Users complete searches and click results\")\n3. **Metric:** How do you quantify the signal? (\"Search-to-click rate, average time from search to product page view\")\n\nThis process prevents metric selection from being arbitrary. Every metric traces back to a user goal.\n\n## System Usability Scale (SUS)\n\nThe most widely used standardized usability questionnaire. Ten questions on a five-point Likert scale, producing a score from 0-100.\n\n### Scoring and Interpretation\n\n- Raw score calculation: alternate positive\u002Fnegative items, subtract\u002Fadd from scale anchors, multiply by 2.5.\n- Average SUS score across studies: 68 (this is the 50th percentile, not a passing grade).\n- Adjective scale mapping: \u003C50 = Awful, 50-67 = Poor to OK, 68 = Passable, 68-80 = Good, 80-90 = Excellent, 90+ = Best Imaginable.\n- Grade scale: \u003C60 = F, 60-69 = D, 70-79 = C, 80-89 = B, 90+ = A.\n- Percentile benchmarks: 68 = 50th, 74 = 64th, 80 = 85th, 86 = 96th.\n\n## Choosing an Instrument\n\n- **SUS** (10 items): post-study, baselines, comparisons, longitudinal tracking. Perceived usability only; a thermometer, not a diagnosis.\n- **UMUX-Lite** (2 items, r = 0.83 with SUS): in-app pulse checks where survey fatigue matters.\n- **UEQ** (26 items, six dimensions): when hedonic qualities matter alongside pragmatic ones.\n- **SUPR-Q**: web-only percentile rank against 200+ sites.\n- **Task metrics** (success, time on task, errors, lostness) and **behavioral analytics** (funnels, cohorts, retention) for what users do; **A\u002FB or sequential tests** to prove causation.\n\n## AI-Specific UX Metrics\n\n- **Trust calibration score:** How closely does user confidence in AI output match actual AI accuracy?\n- **Appropriate reliance rate:** Percentage of times users correctly accept accurate AI outputs and correctly reject inaccurate ones.\n- **AI feature adoption:** Opt-in rate, prompt frequency, feature retention over time.\n- **Correction frequency:** How often users edit or override AI outputs.\n- **Time saved:** Measured difference in task time with AI versus without.\n\n## Routing\n\n- **Choosing and scoring a framework** — HEART in depth, SUS scoring and limitations, UEQ, UMUX-Lite, SUPR-Q, task and behavioral metrics, NPS\u002FCES\u002FCSAT in a UX context, analytics metric design, experimentation (sample size and MDE table, significance, duration, peeking and multiple-comparison errors, Bayesian vs frequentist, sequential testing, guardrails) and benchmarking, UX ROI, design system metrics and ROI, maturity models, dashboards: read `references\u002Fmetrics-frameworks-compendium.md`.\n- **Measuring an AI feature** — AI metric taxonomy, affective metrics, cross-platform measurement, experiments that survive non-determinism, continuous discovery, atomic research, AI experiment pitfalls: read `references\u002Fai-ux-metrics-experimentation.md`.\n\n## Cross-Referencing\n\n- For heuristic evaluation methodology, reference `nng-ux-heuristics`.\n- For research methodology, reference `ux-research-methods`.\n- For AI-specific metrics detail, reference `ux-metrics-measurement\u002Freferences\u002Fai-ux-metrics-experimentation`.\n- For design system metrics detail, reference `design-systems-architecture\u002Freferences\u002Fgovernance-scaling`.\n- For usability testing protocols that produce metrics, reference `ux-research-methods\u002Freferences\u002Fresearch-protocols`.\n- Design system maturity rubric and adoption thresholds: `design-systems-architecture`\n- Hallucination rate and confidence calibration metrics: `agentic-ai-generative-ux`\n- Notification effectiveness metrics: `performance-states-patterns`\n\n## Key Sources\n\n- Google HEART Framework (Rodden, Hutchinson, Fu)\n- Sauro, J. & Lewis, J.: \"Quantifying the User Experience\"\n- MeasuringU: 48 UX Metrics (2025)\n- Brooke, J.: SUS — A Quick and Dirty Usability Scale\n- Schrepp, M.: User Experience Questionnaire (UEQ)\n- Frontiers in Computer Science: UX Measurement Frameworks\n- Sparkbox: Design System ROI Research\n- NNG Group: UX Maturity Model, DesignOps 101\n",{"name":5,"description":7,"allowed-tools":24},"Read, Grep, Glob","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdesign-ops\u002Fskills\u002Fux-metrics-measurement","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill ux-metrics-measurement",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill ux-metrics-measurement",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill ux-metrics-measurement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fux-metrics-measurement\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fai-ux-metrics-experimentation.md","REFERENCE","参考文档",26263,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fux-metrics-measurement\u002Freferences\u002Fai-ux-metrics-experimentation.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fmetrics-frameworks-compendium.md",47894,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fux-metrics-measurement\u002Freferences\u002Fmetrics-frameworks-compendium.md",[58,64,71,78,85,92],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]