menkesu/metrics-frameworks
Defines right metrics using North Star framework, AARRR, and leading vs lagging indicators. Use when choosing metrics, instrumenting products, creating dashboards, or distinguishing vanity metrics from actionable ones.
npx skills add https://github.com/menkesu/awesome-pm-skills --skill metrics-frameworks
Claude uses this skill when:
Definition:
> The ONE metric that best captures the core value you deliver to customers
Good North Star:
Examples:
Pirate Metrics:
# Metrics Dashboard: [Product/Feature]
## North Star Metric
**Metric:** [name]
**Current:** [value]
**Target:** [goal]
**Why this metric:** [captures core value]
## Supporting Metrics
### Acquisition
- Signups: [X per day]
- Channels: [breakdown]
- Cost per acquisition: [$X]
### Activation
- Activation rate: [X]%
- Time to first value: [X minutes]
### Retention
- Day 1: [X]%
- Day 7: [X]%
- Day 30: [X]%
### Revenue
- ARPU: [$X]
- LTV: [$X]
- Conversion rate: [X]%
### Referral
- K-factor: [X]
- Referral rate: [X]%
## Leading vs Lagging
**Leading (predict future):**
- [Metric that predicts outcome]
**Lagging (measure past):**
- [Metric that measures result]
Choose Metrics:
Implement:
Amplitude:
> "The best metrics measure value delivery, not just activity."
Sean Ellis:
> "If you can't measure it, you can't improve it."
Take menkesu/metrics-frameworks from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.