north-star-metric
This Claude Code skill helps product managers and strategists define a North Star Metric by classifying a business into one of three categories (Attention, Transaction, or Productivity) and validating candidate metrics against seven criteria including customer-centricity, measurability, and alignment with company vision. Use it when establishing a metrics framework, selecting key performance indicators to optimize, or evaluating whether potential metrics will serve as effective leading indicators of long-term business success.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/north-star-metric && cp -r /tmp/north-star-metric/pm-marketing-growth/skills/north-star-metric ~/.claude/skills/north-star-metricSKILL.md
# North Star Metric Identify a North Star Metric and 3-5 Input Metrics that form a metrics constellation. Classifies the business game being played and validates against criteria for an effective North Star. Use when defining key metrics, setting up a metrics framework, or choosing what to measure. ## Domain Context NSM is **NOT**: multiple metrics, a revenue/LTV metric (must be customer-centric), an OKR (that's a goal-setting technique), or a strategy (but choosing the right NSM is a strategic choice). NSM **IS**: a single, customer-centric KPI that reflects the value customers get from the product and serves as a leading indicator of long-term business success. You can use Key Results (OKRs) to express expected change in NSM. Free resource: [The North Star Framework 101 (PDF)](https://learn.productcompass.pm/nsm101) ## When to Use - Defining your company's key metric framework - Setting up a metrics tracking system - Choosing what to measure and optimize for - Evaluating potential North Star candidates - Triggers: North Star metric, north star, key metric, what to measure, metrics framework, OMTM ## The Three Business Games Before identifying your North Star, classify your business into one of these three games: - **Attention Game**: How much time do customers spend using your product? (Examples: Facebook, Spotify, YouTube, TikTok) - **Transaction Game**: How many transactions occur between customers and your platform? (Examples: Amazon, Uber, Airbnb, PayPal) - **Productivity Game**: How efficiently can someone complete their work or achieve their goals? (Examples: Canva, Dropbox, Loom, Notion) ## Prompt You are a metrics strategist specializing in North Star metrics and growth measurement frameworks. Given the following business context: $ARGUMENTS **Step 1: Classify the Business Game** Determine which game this company plays: Attention, Transaction, or Productivity. **Step 2: Identify the North Star Metric** Suggest a single metric that meets all seven criteria for an effective North Star: 1. **Easy to Understand**: Clear definition that everyone in the organization comprehends 2. **Customer-Centric**: Reflects value delivered to customers, not just revenue or activity 3. **Sustainable Value**: Indicates habits and long-term customer engagement 4. **Vision Alignment**: Represents meaningful progress toward the company's vision and mission 5. **Quantitative**: Measurable with clear, numeric tracking 6. **Actionable**: Teams can directly influence it through product, marketing, and operational changes 7. **Leading Indicator**: Predicts future business success and revenue growth **Step 3: Identify Input Metrics** Define 3-5 Input Metrics (also called leading indicators) that most directly influence and drive the North Star Metric. Each input metric should: - Be easier to move in the short term - Directly contribute to the North Star outcome - Help identify where optimization efforts should focus ## Tips for Best Results - Provide details about your business model and revenue model - Share your company's vision, mission, or long-term goals - Include current metrics you're tracking - Mention key customer segments and use cases - Describe the primary value you deliver to customers --- ### Further Reading - [The North Star Framework 101](https://www.productcompass.pm/p/the-north-star-framework-101) - [AARRR (Pirate) Metrics: The 5-Stage Framework for Growth](https://www.productcompass.pm/p/aarrr-pirate-metrics) - [The Google HEART Framework: Your Guide to Measuring User-Centric Success](https://www.productcompass.pm/p/the-google-heart-framework) - [The Ultimate List of Product Metrics](https://www.productcompass.pm/p/the-ultimate-list-of-product-metrics)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
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.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.