PlaygroundCatalog › Metrics Framework
MF

Metrics Framework

🟢 Production-Ready🕐 updated 2026-07-14 ✅ 4.8/5 🔷 SkillSpec L3 pm-data

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)

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

🗣 Say this to your agent

“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

✅ 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

Start with

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="metrics-framework"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Metrics Framework is one of 1078 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog