build-metric-tree

Decompose a top-line metric into a quantified metric tree with mathematical relationships, size each node, and identify where the real leverage is. Use when a PM needs to understand what drives a metric, where to focus, or where NOT to focus.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear, well-sequenced workflow and worked quantitative examples, but it carries some motivational padding that hurts conciseness and lacks any progressive-disclosure file structure to offload detail.

Suggestions

Trim motivational framing and rhetorical asides (e.g. 'You want to move a number but you're not sure where to focus', 'an unsized tree is just a diagram') to tighten conciseness while keeping the concrete instructions.

Move the full prompt template and/or the metric-quality checklist into a referenced file (e.g. references/prompt-template.md) and signal it from SKILL.md to improve progressive disclosure.

Add an explicit validation/verification checkpoint after Step 3 (sizing) — e.g. confirm every node is sized before proceeding to leverage analysis — to strengthen the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient instructional guidance, but includes motivational padding ('You want to move a number but you're not sure where to focus') and rhetorical asides ('an unsized tree is just a diagram') that could be trimmed without losing substance.	2 / 3
Actionability	Provides concrete executable guidance: explicit +/x math operators, a fully worked numeric tree example, computed leverage math ('Improving activation rate from 40% to 50% on 20,000 signups = 2,000 additional WAU'), and a specific metric-quality checklist.	3 / 3
Workflow Clarity	A clearly sequenced five-step process with numbered sub-steps and an explicit Output Format checklist; the 'where is it NOT' / 'don't be wishful' check functions as a verification step, and the task is analytical rather than destructive so no feedback-loop cap applies.	3 / 3
Progressive Disclosure	A single self-contained file with well-organized sections but no bundle references to offload detail; the ~107-line body and full inline prompt template could be better split, and no one-level-deep references are signaled.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong across all dimensions: it names concrete actions, provides explicit 'Use when' triggers in third person, and occupies a distinct niche with low conflict risk. It is concise yet complete.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Decompose a top-line metric into a quantified metric tree with mathematical relationships, size each node, and identify where the real leverage is' — matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('Decompose a top-line metric into a quantified metric tree...') and when via an explicit 'Use when a PM needs to understand...' clause.	3 / 3
Trigger Term Quality	Includes natural phrases a PM would say — 'understand what drives a metric', 'where to focus', 'where NOT to focus' — giving good coverage of terms users would actually use.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (metric/KPI tree decomposition for PMs) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: amplitude/builder-skills
Commit: 22b0634

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.