# Metrics Tree

> Define a north-star metric, decompose it into a driver tree, and produce an instrumentation spec engineers can implement. Use when the user says "define metrics for", "what should our north star be", "build a metrics tree", "KPI framework", or "what should we measure".

- **Type:** Skill
- **Install:** `agentstack add skill-ramanbamba-10x-pm-metrics-tree`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [ramanbamba](https://agentstack.voostack.com/s/ramanbamba)
- **Installs:** 0
- **Category:** [Data & Analytics](https://agentstack.voostack.com/c/data-and-analytics)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [ramanbamba](https://github.com/ramanbamba)
- **Source:** https://github.com/ramanbamba/10x-pm/tree/main/skills/metrics-tree

## Install

```sh
agentstack add skill-ramanbamba-10x-pm-metrics-tree
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Metrics Tree

Define metrics that measure *value delivered*, decompose them into drivers a team can move, and specify the events needed to compute them — so the metric exists in a dashboard, not just a slide.

## Before defining

1. Ask what the product's core value moment is — the thing a user does when the product has worked for them. The north star should count that, not activity around it.
2. Ask the business model. Ads, SaaS seats, usage-based, and marketplace products have structurally different trees.
3. Ask what's already instrumented. A beautiful tree over missing events is fiction.

## Workflow

1. **Propose the north star** with 2 alternatives considered and rejected (show the reasoning — the rejections teach the team what the metric protects against). Test each candidate: *Would this number go up if we made the product worse in a profitable way?* If yes, it's gameable — fix or guard it.
2. **Decompose into a driver tree**, 2–3 levels deep. Each node must be: movable by a team, measurable from real events, and arithmetically connected to its parent (state the relationship: sum, product, funnel rate).
3. **Assign input vs. output.** Teams own input metrics (drivers); leadership watches output metrics. Mark which is which.
4. **Add guardrails.** For each driver, name the metric that catches the ugly way to move it (e.g., driver: sessions/user; guardrail: task completion rate).
5. **Write the instrumentation spec.** For every leaf node: event name, trigger, properties, and current status (exists / needs adding). Use consistent `object_action` naming.

## Output format

```markdown
# Metrics — [product], [date]

## North star
**[Metric]** — [exact definition, including counting rules and time window]
*Why:* [ties to value moment]
*Rejected:* [alt 1 — why not] · [alt 2 — why not]
*Gaming check:* [how it could be gamed, and the guardrail]

## Driver tree
[Indented tree, each node with: metric, relationship to parent, input/output tag, owning team]

North star
├── Driver A (product: A = B × C) [output]
│   ├── Driver B [input — Team X]
│   └── Driver C [input — Team Y]
└── ...

## Guardrails
| Driver | Ugly way to move it | Guardrail metric |
|---|---|---|

## Instrumentation spec
| Metric | Event name | Fired when | Properties | Status |
|---|---|---|---|---|

## Baseline & review
[Current values where known; proposed review cadence; owner of the metrics doc]
```

## Quality bar — self-check

- **North star counts value, not activity.** Sign-ups, sessions, and page views fail unless the product's value literally is attention.
- **Every definition is exact.** "Active user" without the action + window that defines "active" fails.
- **The tree's arithmetic works.** Parent = stated function of children; no orphan vanity metrics.
- **Every driver has a guardrail.**
- **The instrumentation spec is implementable as written** — an engineer should not need a follow-up meeting to name the events.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [ramanbamba](https://github.com/ramanbamba)
- **Source:** [ramanbamba/10x-pm](https://github.com/ramanbamba/10x-pm)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-ramanbamba-10x-pm-metrics-tree
- Seller: https://agentstack.voostack.com/s/ramanbamba
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.