North star
Skill Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/north-star
A curated pack of custom Claude Code skills for developers — installable as a Claude Code plugin marketplace.
npx -y skills add Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack --skill north-starAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
When to activate: north star metric, NSM, input metrics, leading indicators, metric tree, metric framework, product health metric, vanity metrics
SKILL.md
6.0 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it
North Star Metric
What Is the North Star Metric
The NSM is the single metric that best captures the core value your product delivers to customers — and predicts long-term revenue.
NSM Criteria (must satisfy all)
- Reflects customer value: measures the value customers get, not just usage
- Leads to revenue: correlates with retention, expansion, or acquisition
- Actionable: product team can move it through their work
- Understandable: any team member can explain it in one sentence
- Measurable: can be tracked with existing or buildable instrumentation
- Not a vanity metric: moving it means something real
NSM vs Revenue
Revenue is a lagging indicator — it tells you what happened. NSM tells you what's coming.
NSM (leading) → Retention → Revenue (lagging)
If NSM is growing: revenue will follow
If NSM is flat: revenue growth will slow
If NSM is falling: revenue problem is coming
NSM Examples by Business Model
| Product | NSM | Why |
|---|---|---|
| Slack | Messages sent per active team | Measures real collaboration value |
| Airbnb | Nights booked | Captures value for both hosts and guests |
| Spotify | Time spent listening | Reflects engagement and habit formation |
| Weekly active users who view a feed story | Captures core network value | |
| HubSpot | Contacts reached per week | Measures marketing activity value |
| Duolingo | Daily Active Users completing a lesson | Habit + progress |
| Figma | Collaborators on a file | Network effect and value delivered |
NSM Definition Workshop
Step 1: Value Moments (30 min, team exercise)
"When does a customer get undeniable value from our product?" Write each moment on a sticky note. Cluster by theme.
Step 2: Candidate Metrics (20 min)
Convert top value moments to measurable metrics. For each: can we measure it? does it lead to retention?
Step 3: Filter Against Criteria (20 min)
Score each candidate 1–5 on: reflects value / leads to revenue / actionable / understandable / measurable. Drop any below 3 on any criterion.
Step 4: Validate with Data (1 week)
Correlate candidates with D90 retention in your data. Pick the one with strongest correlation.
Step 5: Gut Check Questions
- Would we be comfortable if this was the only metric our board saw?
- Could every team (eng, design, CS) explain how their work connects to it?
- If this metric goes up while revenue goes down, would we be worried?
Input Metric Tree
The NSM is influenced by input metrics. Map them as a tree.
NSM: Weekly active projects per team
│
├── Acquisition inputs
│ ├── New team signups per week
│ └── Invite acceptance rate
│
├── Activation inputs
│ ├── % teams creating first project in Day 1
│ └── Time-to-first-project (median)
│
├── Engagement inputs
│ ├── % teams with ≥1 active project per week
│ └── Projects created per active team
│
└── Retention inputs
├── D30 team retention
└── % teams returning after 2-week gap
Input Metric Rules
- Each input must have a clear owner (team or person)
- Inputs should be measurable independently of the NSM
- Prioritize inputs by: impact on NSM × ease of improvement
- Review tree quarterly — inputs drift as product evolves
Leading vs Lagging Indicators
| Type | Timing | Example |
|---|---|---|
| Leading | Predicts future | Feature adoption, activation rate |
| Coincident | Moves with business | DAU, weekly sessions |
| Lagging | Confirms what happened | Revenue, churn rate, NPS |
Diagnostic Sequence
When NSM drops:
- Check acquisition inputs → is volume down?
- Check activation inputs → are new users failing to activate?
- Check engagement inputs → are existing users using less?
- Check retention inputs → are teams churning faster?
- Segment by: cohort, plan, geography, acquisition channel
Vanity Metric Identification
Vanity Metric Signals
- Metric always goes up regardless of product decisions
- Team cannot take a direct action to improve it
- Improvement doesn't correlate with revenue or retention
- Easy to game without delivering value
Common Vanity Metrics → Better Alternatives
| Vanity metric | Better alternative |
|---|---|
| Total registered users | Weekly active users |
| Total page views | Sessions per user |
| App downloads | DAU |
| Email opens | Replies or clicks |
| Press mentions | Referral traffic from press |
| Social followers | Engagement rate |
NSM-to-Roadmap Alignment
Every roadmap item should connect to the NSM.
Connection Template
Initiative: [Project name]
Problem: [What user pain or behavior gap exists]
Hypothesis: If we [do X], [input metric Y] will improve by Z%,
which will contribute to [NSM] improving by ~N%.
Measurement: [How we'll know it worked]
Roadmap Review Checklist
Before adding a project to roadmap:
- Which input metric does this improve?
- How does that input connect to the NSM?
- What's the estimated NSM impact?
- How will we measure success?
Metric Decay Detection
NSMs can become obsolete as the product evolves.
Signs Your NSM Needs Updating
- NSM is growing but revenue is flat or declining
- NSM can be gamed without delivering real value
- Product has evolved significantly since NSM was defined
- New user segments have different value patterns
- NSM correlation with retention has dropped below 0.7
Update Cadence
- Review NSM relevance annually
- Full redefinition workshop every 2–3 years or after major pivot
- Document the old NSM and why it was changed