Framework for defining a single, customer-centric metric that aligns teams and drives product decisions.
Works with
Measure value delivered to users, not revenue or internal activity; use proxy metrics like messages sent or nights booked that correlate with long-term outcomes
Ensure simplicity and universal understanding across the company; avoid composite scores and technical jargon that obscure meaning
Verify actionability by confirming teams can influence the metric through their work, and a
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwriting-north-star-metricsExecute the skills CLI command in your project's root directory to begin installation:
Fetches writing-north-star-metrics from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate writing-north-star-metrics. Access via /writing-north-star-metrics in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
Help the user define their North Star metric using frameworks and insights from 27 product leaders.
When the user asks for help with North Star metrics:
Itamar Gilad: "The North Star metric measures how much value we create for the market. WhatsApp measured messages sent because every message is incremental value. Airbnb used nights booked." Select a metric that tracks core utility provided to the customer, not business extraction.
Jess Lachs: "Retention is a terrible thing to goal on. It's almost impossible to drive in a meaningful way in a short term. Find a short-term metric you can measure that drives a long-term output." Identify proxy metrics that are sensitive to experimentation and correlate with long-term goals.
Jess Lachs: "If people understand it, if they have an intuition around it, if it's something people can talk about across the company, it's going to be a much better metric than your made up composite score that nobody understands." Avoid composite metrics with complex coefficients.
Jeff Weinstein: "What was the value we're trying to produce for the customer, and can we measure it from their perspective? We suggested 'companies with zero support tickets.'" Define metrics based on the absence of friction or the presence of success moments.
Hari Srinivasan: "Everything at LinkedIn is a very connected ecosystem, but decisions aren't difficult because we're all here to help people connect to economic opportunity." A clear company-wide mission serves as the ultimate tie-breaker for product decisions.
Jeff Weinstein: "Picking metric titles that make you feel something. 'Companies with zero support' - the brevity and customer mindset built into the chart name can become currency inside the company." Use simple, evocative names instead of technical database field names.
Manik Gupta: "Everyone will talk about the same metric but have different nuances. What is a daily active user? Pick a definition, instrument it, codify it. No confusion." Metrics only drive alignment when backed by precise definitions and accurate instrumentation.
Lauryn Isford: "An activation rate that falls in a lower percentage range, maybe 5-15%, is better than a high percentage because it means there's likely much higher correlation with long-term retention." High-bar activation metrics that few users reach are often more valuable.
Lauryn Isford: "A North Star metric should be a measure of what you plan to do. Revisit North Star metrics every 6-12 months to ensure they still align with business goals." Be willing to shift metrics if the strategy requires it.
Sean Ellis: "I think monthly purchases is great because it maps to value people are getting. Units of value from the customer perspective is more important than overall revenue." Revenue should be a product of doing things right, not the day-to-day guiding metric.
For all 35 insights from 27 guests, see references/guest-insights.md
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
writing-north-star-metrics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for writing-north-star-metrics matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in writing-north-star-metrics — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: writing-north-star-metrics is focused, and the summary matches what you get after install.
Keeps context tight: writing-north-star-metrics is the kind of skill you can hand to a new teammate without a long onboarding doc.
writing-north-star-metrics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend writing-north-star-metrics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
writing-north-star-metrics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
writing-north-star-metrics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
writing-north-star-metrics reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 35