north-star-metric

Define a North Star Metric and its input metrics. Classify the game your product plays, evaluate candidates against quality criteria, and build a connected metric system. Use when choosing a North Star, evaluating an existing one, or setting up a metrics framework.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

The content is a well-structured, highly actionable prompt-based skill with a clear sequenced workflow and a validation step. Its only weakness is conciseness: the Domain Context section explains conceptual background that Claude largely already knows and could be condensed.

Suggestions

Condense the "What a North Star Metric IS / IS NOT" Domain Context into a compact list of rules rather than explanatory prose, trusting Claude to know the underlying concepts.

Trim the three-functions and Three-Games explanations to one-line definitions with examples, keeping only the framework-specific framing (Breadth-Depth-Frequency-Efficiency) that Claude would not reliably reproduce.

Move any retained background context to a reference file and keep SKILL.md focused on the prompt steps, reducing the token footprint of the always-loaded body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and the framework framing (Three Games, Breadth-Depth-Frequency-Efficiency) earns its place, but the Domain Context section — "What a North Star Metric IS" with three functions and "What it is NOT" with explanatory prose — restates concepts Claude largely knows and could be tightened.	2 / 3
Actionability	The 6-step prompt gives concrete, specific guidance: each step specifies exact deliverables ("name + unit + time window", six named evaluation criteria with guiding questions, per-input-metric ownership and mathematical connection), which is copy-paste ready as an instruction-only skill.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced and Step 6 "Validate the System" provides an explicit validation/feedback loop ("If all input metrics improve, does the NSM necessarily improve?") with instruction to flag structural weaknesses, matching the level-3 anchor.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the skill is a single well-organized SKILL.md with clear sections (Domain Context, When to Use, Prompt, Tips, Further Reading) and only external URL references, satisfying the simple-skill allowance for a 3 with well-organized sections.	3 / 3
	Total	11 / 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, includes natural trigger terms, explicitly covers both what and when, and occupies a distinctive niche. Voice is consistently third-person imperative, incurring no penalty.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Define a North Star Metric and its input metrics", "Classify the game", "evaluate candidates against quality criteria", "build a connected metric system" — matching the level-3 anchor of several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (define/classify/evaluate/build) and when ("Use when choosing a North Star, evaluating an existing one, or setting up a metrics framework"), satisfying the level-3 anchor for both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	Natural user-facing terms appear in the trigger clause — "choosing a North Star", "evaluating an existing one", "setting up a metrics framework" — covering the phrases a user would actually say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The North Star Metric concept is a clear niche with distinct triggers unlikely to fire for unrelated skills; it would only overlap with closely related metrics skills, matching the level-3 anchor.	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.