Build a metrics framework for any product, team, or business. Use when asked for a metrics tree, KPI framework, North Star metric, AARRR funnel, HEART framework, or OKR metrics. Produces a structured metrics hierarchy from North Star down to leading indicators, with measurement guidance.
📚 Based on North Star Framework (Amplitude); Pirate Metrics / AARRR (Dave McClure)
“Build a metrics framework for [product]”“What should our North Star metric be?”“Create a KPI tree for [business]”“Give me an AARRR breakdown for [product]”“What metrics should our [team type] team track?”
What to give it
▸Product or business description — one paragraph is enough
▸Business model — SaaS / Marketplace / E-commerce / Consumer app / B2B / Other
▸Stage — Pre-PMF / Growth / Scale / Mature
▸Framework preference — (if they have one): North Star + Metric Tree / AARRR / HEART / OKRs / Custom
▸Primary goal this quarter — (e.g. grow activation, reduce churn, increase revenue) If no framework preference is given, recommend the best fit based on stage and business model.
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓North Star reflects customer value, not just business activity
✓Metric tree has 3–4 distinct drivers (not all one category)
✓Each L2 metric is classified as leading or lagging
✓Counter-metrics are included to prevent perverse incentives
✓Dashboard tiers are tailored to the product stage
✓All metric definitions are unambiguous (formula or clear description)
⚠️ What it refuses to do
Do not set a North Star metric that measures business activity (revenue, pageviews) rather than customer value delivered — this creates incentives misaligned with product quality
Do not define metrics without specifying the formula or data source — an ambiguous metric will be measured differently by different people
Do not skip counter-metrics — optimising any single metric without a guard rail will eventually produce perverse incentives
Do not include more than 4–5 metrics in a daily team view — a dashboard with 20 metrics is a dashboard nobody looks at
Do not classify all metrics as "leading" — be honest about which are lagging outcome metrics and which genuinely predict future outcomes
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp
Example output
Input: Define the metrics framework for a B2B analytics product: the north star, input metrics across acquisition/activation/retention/revenue, and guardrails. Stage: early growth, ~500 paying accounts. · generated by claude-sonnet-4-6