What do I need to use Metric Tree Builder?

The north-star / top metric; Business model; Where the team can act; Current pain (optional).

Is Metric Tree Builder free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Metric Tree Builder

Q: How do I know the Metric Tree Builder output is good?

The skill verifies itself against its own quality checks: The top metric is expressed as an actual equation of its drivers; The tree bottoms out in input metrics a team can act on, not more outputs; Multiplicative vs additive relationships are noted; Identifies the highest-leverage levers with reasoning.

🔵 Stable🕐 updated 2026-10-06 🔷 SkillSpec L3 pm-data

Decompose a north-star metric into a driver tree — the inputs and sub-inputs that actually move it — so a team knows which levers to pull. Use when asked to build a metric tree, break down a north-star metric, map metric drivers, or find the inputs behind an output metric. Produces a hierarchical tree from the top metric down to actionable input metrics, with the relationships, the highest-leverage levers, and what to instrument.

📚 Based on North-star metric / input-metric driver trees (Reforge, Amplitude)

▶ Run it free — no key needed 📝 Grade your existing draft 📱 Use as an app View SKILL.md ↗ What changed

🗣 Say this to your agent

“Build a metric tree.”“Break down a north-star metric.”“Map metric drivers.”“Find the inputs behind an output metric.”

What to give it

▸The north-star / top metric — e.g. weekly active revenue, MRR, GMV, activated users

▸Business model — subscription, marketplace, ads, transactional, freemium

▸Where the team can act — which teams own which surfaces

▸Current pain (optional) — the metric is flat / dropping — optional, focuses the tree

✅ 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.

✓The top metric is expressed as an actual equation of its drivers

✓The tree bottoms out in input metrics a team can act on, not more outputs

✓Multiplicative vs additive relationships are noted

✓Identifies the highest-leverage levers with reasoning

✓Flags metrics that need to be instrumented

⚠️ What it refuses to do

A "tree" that's just a flat list of unrelated KPIs

Stopping at output metrics no one can directly move

Ignoring how drivers combine (treating everything as additive)

No view on which lever actually matters most

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 -p pm-claude-skills pm-claude-skills-mcp

Related skills

🔌 Embed this skill

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

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

💬 Discussion

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