north-star-metric
Skill3 starsChanged 8 months agoMITView on GitHub
Define or critique a product North Star Metric and its input metrics. Use when a team needs one shared leading indicator of customer value and growth.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- About-Intelligence/awesome-marketing-skillstheir own version, first seen Nov 8, 2026
- yuusakuri/agent-skillstheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- fullstackinnoAI/skillstheir own version, first seen Nov 1, 2026
- daviszhen/agent-skillstheir own version, first seen Oct 25, 2026
- zpower426/pmpowerstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use brainstorm-okrs, positioning-ideas and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
skytiger6724Skillbrainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Also in 5 projects that use this
About-IntelligenceSkillpositioning-ideas
Brainstorm product positioning ideas differentiated from competitors.
Also in 5 projects that use this
About-IntelligenceSkillgtm-motions
Identify the best GTM motions and tools across 7 motion types: Inbound, Outbound, Paid Digital, Community, Partners, ABM, and PLG.
Also in 5 projects that use this
skytiger6724Skilloutcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
Also in 5 projects that use this
miovragSkillstrategy-red-team
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
Also in 4 projects that use this
- +3 more from About-Intelligence
- +4 more from skytiger6724
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- About-Intelligence/awesome-marketing-skills★ 14same name
- deciqAI/knowledge-skills★ 13same name
- fzfclee/consulting-skills★ 6same name
- The-Utopia-Studio/skills★ 6same name
- Adhamxon/claude-code-skills★ 2same name
- skytiger6724/qwen-skills★ 2same name
- yuusakuri/agent-skills★ 2same name
- daviszhen/agent-skills★ 1same name
- fullstackinnoAI/skills★ 1same name
- miovrag/claude-skills★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- customer-discovery-jtbd-synthesisSkill
- event-tracking-planSkill
- experiment-design-readoutSkill
- launch-planSkill
- onboarding-activation-auditSkill
- positioning-messagingSkill
- pricing-packaging-hypothesisSkill
- retention-diagnosisSkill
- seo-geo-content-briefSkill
- customer-discovery-jtbd-synthesisSkill
- event-tracking-planSkill
- experiment-design-readoutSkill
- launch-planSkill
- north-star-metricSkill
- onboarding-activation-auditSkill
- positioning-messagingSkill
- pricing-packaging-hypothesisSkill
- retention-diagnosisSkill
- seo-geo-content-briefSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 17 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
17
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill when the user wants to define, refine, critique, or operationalize a North Star Metric (NSM) for a product, feature set, or …
- Distinctive: line 13
Always produce these sections:
- Distinctive: line 26
If the user asks only for critique, still use the same structure, but focus on diagnosing the existing North Star.
- Distinctive: line 30
If the user or repo already provides them, extract:
- Distinctive: line 43
If something is missing, make a best-effort assumption and label it clearly.
- Distinctive: line 47
Prefer a leading indicator over lagging outcomes like revenue, MRR, or ARPU.
- Distinctive: line 48
Prefer a metric that captures customer value realized, not vanity activity.
- Distinctive: line 49
Prefer a metric that product and marketing can influence through day-to-day work.
- Distinctive: line 50
Prefer one metric that is hard to game.
- Distinctive: line 51
Avoid metrics that can rise while product value falls.
- Distinctive: line 52
Avoid pure volume metrics when a quality threshold is required.
- Distinctive: line 53
Avoid making the NSM directly editable by one team without the supporting system beneath it.
- Very specific: line 67
Value exchange: When [user] does [meaningful action] to achieve [outcome], the business gains [business value].
- Distinctive: line 76
If hybrid, pick the dominant one and explain why.
- Distinctive: line 104
Create 3-6 input metrics that plausibly drive the NSM.
- Distinctive: line 118
Write an implementation-ready spec with:
- Distinctive: line 144
Use exactly this structure:
- Distinctive: line 208
If you cannot recommend a single NSM with confidence:
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
North Star Metric
Use this skill when the user wants to define, refine, critique, or operationalize a North Star Metric (NSM) for a product, feature set, or business line.
What this skill must produce
Always produce these sections:
- Context summary
- Candidate engagement game / product motion
- North Star options (2-4 options)
- Recommended North Star
- Input metrics (3-6)
- Metric definition spec
- Why this is a good North Star
- Risks / failure modes
- Instrumentation requirements
- 30/60/90 day rollout plan
If the user asks only for critique, still use the same structure, but focus on diagnosing the existing North Star.
Inputs to gather
If the user or repo already provides them, extract:
- Product name
- Primary user
- Primary customer / buyer
- Core job-to-be-done
- Core product motion: attention, transaction, productivity, or hybrid
- Business model: freemium, self-serve, sales-assisted, enterprise, usage-based, seat-based, subscription
- Core user actions
- Desired business outcomes
- Existing KPIs / dashboards / event schema
- Whether this is company-level, product-line-level, or team-level
If something is missing, make a best-effort assumption and label it clearly.
Working rules
- Prefer a leading indicator over lagging outcomes like revenue, MRR, or ARPU.
- Prefer a metric that captures customer value realized, not vanity activity.
- Prefer a metric that product and marketing can influence through day-to-day work.
- Prefer one metric that is hard to game.
- Avoid metrics that can rise while product value falls.
- Avoid pure volume metrics when a quality threshold is required.
- Avoid making the NSM directly editable by one team without the supporting system beneath it.
Step-by-step method
Step 1: frame the product and value exchange
State in one sentence:
- who the user is
- what they are trying to get done
- what value the product creates
- what value the business gets back
Use this format:
Value exchange: When [user] does [meaningful action] to achieve [outcome], the business gains [business value].
Step 2: identify the engagement game
Classify the product primarily as:
- Attention: value comes from time, content consumption, expression, or repeated engagement
- Transaction: value comes from completing purchases / bookings / exchanges with confidence
- Productivity: value comes from completing a workflow more effectively or reliably
If hybrid, pick the dominant one and explain why.
Step 3: generate candidate North Stars
Create 2-4 candidate NSMs.
For each candidate provide:
- metric name
- formula
- why it may work
- why it may fail
- what behavior it encourages
- what anti-pattern it risks
Step 4: select the recommended NSM
Choose the best candidate and explain the tradeoff.
A recommended NSM should pass this checklist:
- expresses customer value
- represents product strategy
- is a leading indicator
- is actionable
- is understandable
- is measurable
- is not a vanity metric
Step 5: define input metrics
Create 3-6 input metrics that plausibly drive the NSM.
For each input metric specify:
- name
- formula
- owner
- weekly directionality
- why it matters
- what team can influence it
Inputs should be operational levers, not just more outcomes.
Step 6: create the metric definition spec
Write an implementation-ready spec with:
- canonical metric name
- plain-English definition
- numerator
- denominator (if any)
- quality thresholds
- time window
- aggregation level
- exclusions
- segment cuts
- lagging outcomes expected to move if this improves
Step 7: stress-test the metric
Explicitly answer:
- How could this metric be gamed?
- Could it increase while user value falls?
- What seasonal, cohort, or market distortions affect it?
- What would make us revisit it?
Step 8: connect to instrumentation
List the minimum event and property requirements required to compute the NSM and each input metric.
Output format
Use exactly this structure:
Context summary
- Product:
- User:
- Buyer:
- JTBD:
- Motion:
- Business model:
Candidate engagement game / product motion
...
North Star options
| Option | Formula | Why it could work | Main risk |
Recommended North Star
Name:
Formula:
Interpretation:
Input metrics
| Input metric | Formula | Owner | Why it matters |
Metric definition spec
- Canonical name:
- Plain-English definition:
- Grain:
- Time window:
- Quality threshold:
- Included events:
- Excluded events:
- Segments to monitor:
Why this is a good North Star
- Expresses customer value:
- Represents strategy:
- Leading indicator:
- Actionable:
- Understandable:
- Measurable:
- Non-vanity:
Risks / failure modes
- ...
- ...
- ...
Instrumentation requirements
- Events:
- Event properties:
- User properties:
- Account / org properties:
- Data quality checks:
30/60/90 day rollout plan
- 30 days:
- 60 days:
- 90 days:
Failure mode handling
If you cannot recommend a single NSM with confidence:
- say that directly
- provide the top 2 candidates
- explain the missing evidence needed to choose between them
- recommend a temporary proxy metric and a validation plan
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

