measure

Defines UX success metrics, A/B tests, and funnel analysis frameworks.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill measure-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: measure
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/measure
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill measure-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship features without knowing whether they worked, or optimize the wrong metrics and end up with dark patterns. This Skill connects design decisions to observable evidence by defining what to measure, how to measure it, and how to act on what you learn. ## Core Features & Use Cases - Metric Selection with HEART: Applies Google's HEART framework (Happiness, Engagement, Adoption, Retention, Task success) per feature, with counter-metrics to catch harmful side effects. - Goal-Signal-Metric Mapping: Builds GSM chains so every metric traces back to a concrete user or business goal before launch. - A/B Test Design: Structures hypotheses, minimum detectable effect, sample size calculations, guardrail metrics, and common experimentation mistakes. - Funnel Analysis & Ethical Measurement: Defines precise funnel steps, segmentation, and qualitative triangulation, plus checks against Goodhart's Law and dark metric patterns. - Use Case: After launching a new checkout flow, use this Skill to define completion-rate targets, design an A/B test with proper sample size, and pair conversion metrics with post-purchase satisfaction to confirm the improvement is genuine. ## Quick Start Ask the assistant to define success metrics and an A/B test plan for your new feature using the measure skill.

Frequently Asked Questions about measure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define UX success metrics for a new feature?

Use the Goal-Signal-Metric framework: state the user outcome as a goal, identify observable behaviors as signals, then define quantifiable metrics with thresholds. Apply the HEART framework to pick the 2-3 dimensions that matter most for that feature.

How to design an A/B test with the right sample size?

Set your minimum detectable effect before the test, then calculate sample size from baseline conversion rate, 80% power, and 95% significance. Run at least 1-2 full weekly cycles and define guardrail metrics that must not degrade.

What is the HEART framework for UX metrics?

HEART stands for Happiness, Engagement, Adoption, Retention, and Task success. It is applied per feature rather than globally, since a checkout flow needs task success metrics while a content feed needs engagement and retention metrics.

Why do good metrics sometimes lead to bad product decisions?

Goodhart's Law states that when a measure becomes a target it stops being a good measure. Optimizing engagement alone can produce infinite scroll or notification spam, so every business metric should be paired with a user-outcome counter-metric.

When should I not rely on A/B testing for design decisions?

Avoid A/B tests when your traffic cannot reach the required sample size, when the change is structural rather than cosmetic, or when novelty effects dominate. In those cases use qualitative research such as usability sessions instead.