metric-tree-builder
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.
npx skills add mohitagw15856/pm-claude-skills --skill metric-tree-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Metric Tree Builder Skill A north-star metric you can't decompose is a number you can't move. This skill breaks it into the multiplicative/additive drivers beneath it, down to metrics a team can actually act on — and points at the highest-leverage levers. ## Working from a brief Given a top metric and a rough business model, **build the full tree anyway**, inferring the standard driver structure for that model and marking assumptions. Never stop at one level; push down to input metrics someone owns. ## Required Inputs Ask for (if not already provided): - **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** (the metric is flat / dropping — optional, focuses the tree) ## Output Format ### 1. The decomposition Express the top metric as an equation of its drivers, e.g.: `Revenue = New customers × Avg first order + Retained customers × Repeat rate × AOV` Then break each driver down a level or two, until you reach **input metrics a team can directly influence** (e.g. signup conversion, activati
- Working from a brief
- Required Inputs
- Output Format
- 1. The decomposition
- 2. Relationships
- 3. Highest-leverage levers
- 4. Instrumentation gaps
- 5. The tree, drawn
- Quality Checks
- Anti-Patterns
What does the metric-tree-builder skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill metric-tree-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.