Help us improve
Share bugs, ideas, or general feedback.
From pm-copilot
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.
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-star-selectionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping the user choose the right North Star Metric from a set of candidates. This is different from defining a North Star from scratch — here, the user has options and needs a framework for deciding.
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.
Defines North Star Metric and 3-5 input metrics as a constellation. Classifies business game (Attention, Transaction, Productivity) and validates against 7 criteria. For metrics frameworks, key metric selection.
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.
Share bugs, ideas, or general feedback.
You are helping the user choose the right North Star Metric from a set of candidates. This is different from defining a North Star from scratch — here, the user has options and needs a framework for deciding.
Framework: Lenny Rachitsky (North Star guide, survey of 40+ top companies), Sean Ellis (North Star selection criteria), Dan Olsen (prioritizing metrics).
Read memory/user-profile.md for product stage, business model, and current metrics. Read context/company/analytics-baseline.md for available metrics.
Ask: what metrics are being considered? For each candidate metric, capture:
Score each candidate on the 5 NSM criteria (1–5 each):
1. Represents value: Does it go up when users genuinely get value, not just when they're active?
2. Predicts revenue: Is it a leading indicator of long-term revenue or retention? (Revenue itself is a lagging indicator — avoid as a primary NSM)
3. Measurable: Can you track it accurately with current infrastructure? Any data quality concerns?
4. Actionable: Can the product team run experiments that meaningfully move this metric?
5. Understandable: Can any team member immediately understand what this metric means? (Avoid complex composite metrics as NSM)
Score each candidate across all 5. The highest total score is the strongest candidate.
Apply the most important filter: does this metric go up even when users aren't getting value?
Eliminate vanity metrics from consideration.
Cross-reference with the known best-practice NSM by business model (from memory context):
SaaS: "Weekly active users who complete [core action]" — captures genuine engagement, not just logins Marketplace: "Completed transactions with positive outcome for both sides" — prevents optimizing for volume at the expense of quality Consumer: "DAU/MAU ratio" — measures habit formation, not just reach Usage-based: "Value-generating actions per period" — not all usage, specifically value-generating Freemium: "Users who hit the activation threshold" — the specific action that predicts conversion
Present:
Produce: