Help us improve
Share bugs, ideas, or general feedback.
From pm-copilot
Use this skill when the user asks about "north star metric", "what should our north star be", "define our north star", "key metric", "one metric that matters", "choosing our success metric", "how do we define success", "our product metric", or wants to select or evaluate a single metric that best represents value delivered. Do NOT use this skill for dashboard design — use metrics/dashboard-structuring for that.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:north-starThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping the user select and define their North Star Metric (NSM) — the single number that best captures whether users are getting genuine value from the product.
Use this skill when the user asks "which metric should we focus on", "how do I choose between these metrics", "what's the best metric to track", "help me select our primary metric", "our metrics are confusing", "we have too many metrics", or wants to select a primary North Star from a set of competing metrics. This is the selection and evaluation skill; for defining and setting a North Star from scratch, use strategy/north-star.
Defines North Star Metrics and input metrics, classifies products into attention/transaction/productivity games, evaluates candidates against criteria, and builds connected metric systems. Use for choosing, evaluating NSMs, or metrics frameworks.
Defines North Star Metric and 3-5 supporting input metrics for businesses, classifies into Attention/Transaction/Productivity games, and validates 7 effectiveness criteria. Use for metric frameworks, key metric selection, or measurement decisions.
Share bugs, ideas, or general feedback.
You are helping the user select and define their North Star Metric (NSM) — the single number that best captures whether users are getting genuine value from the product.
Key principle from Lenny: "Your North Star Metric is your strategy, and your strategy is your North Star Metric." — Choosing Your North Star Metric, Lenny Rachitsky (2021)
Read memory/user-profile.md for product context, business model, and current bets. Read context/company/analytics-baseline.md for available metrics. Read context/product/roadmap.md for OKRs.
A good North Star Metric must pass all five criteria:
Guide the user toward the right metric category based on their business model (from memory):
SaaS / subscription: Focus on engagement + retention combination
Marketplace: Focus on successful transactions
Usage-based: Focus on value-generating usage (not all usage)
Consumer / social: Focus on engagement quality
Freemium: Focus on the conversion-driving behavior
For the user's specific product, decompose the NSM into its components — these become the leading indicator metrics the team can track and move:
North Star Metric
├── Breadth: How many users are reaching this state?
├── Depth: How thoroughly are they engaging with the core value?
├── Frequency: How often are they returning to get value?
└── Efficiency: Are they getting to value faster over time?
Check if the proposed NSM falls into a common trap:
Produce:
Example output format:
North Star: Weekly Active Completions
Definition: Unique users who complete at least one [core action] in a calendar week
Why this: Captures genuine value delivery; predictive of monthly retention; directly moveable by product team
Supporting metrics: Activation rate, return rate (D7), time-to-first-[action], feature adoption depth
Exclude: Total sessions (users can open the app without getting value)
Current: ~1,200/week
Target: 2,000/week by Q3
Offer to save the NSM to memory/user-profile.md and update the roadmap OKR context.