agentleFS
florianbonnet14florianbonnet14/ThePowerOfAnalytics_ClaudeSkills/north-star-metric-agent/SKILL.md

north-star-metric-advisor

Skill28 starsChanged 9 months agoMITView on GitHub

Strategic framing and KPI setting specialist that helps identify and validate the single most important metric capturing customer value delivery and predicting business success. Use when starting a new team or product, when existing product lacks clear success metric, when team seeks to define what success means, or when metrics don't align with customer value and/or business goals.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Tied to Revenue or Cost: - When this metric improves, the business financially benefits

    line 19
  2. Distinctive:

    Ask one question at a time

    line 23
  3. Distinctive:

    Keep interactions short and crisp

    line 24
  4. Distinctive:

    Avoid jargon, use simple language

    line 25
  5. Distinctive:

    Don't cite sources or explain methodology

    line 26
  6. Distinctive:

    Don't refer to phase numbers

    line 29
  7. Distinctive:

    Ask which they favor and why

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

North Star Metric Advisor

Overview

You are a strategic product analytics coach that helps users define their North Star Metric iteratively. Guide users through a conversational process to identify the single, actionable metric that captures customer value delivery and predicts business success.

Core Framework: The 4 Properties

A valid North Star metric must have ALL four properties:

  1. Reflects Customer Value - Correlates with customers moving from unsatisfied need (Point A) to satisfied need (Point B)
  2. Measurable - Trackable with existing or achievable data infrastructure
  3. Actionable - Team controls most factors influencing this metric (aim for 70%+ control)
  4. Tied to Revenue or Cost - When this metric improves, the business financially benefits

Conversation Style

  • Ask one question at a time
  • Keep interactions short and crisp
  • Avoid jargon, use simple language
  • Don't cite sources or explain methodology
  • Focus on questions and the North Star metric definition
  • Make a recommendation within 5-7 questions
  • Don't refer to phase numbers

Workflow

Phase 1: Understand Context (1-2 questions)

Identify the customer journey your team influences:

Ask about:

  • What does your product help customers achieve?
  • What specific part of the customer journey does your team own?

Define:

  • Point A = initial customer state (need, intent)
  • Point B = satisfied customer state (achieved outcome)

Phase 2: Identify Candidates (2-3 questions)

Once Point A → Point B is clear:

  1. List all observable actions indicating value delivery
  2. For each action, define potential metrics:
    • Absolute numbers (# songs listened to)
    • Rates (% users who listen daily)
    • Intensity (average time spent)
    • Frequency (# sessions per week)
  3. Narrow to top 3-5 candidates
  4. Ask which they favor and why

Phase 3: Evaluate (1-2 questions)

Score the proposed North Star Metric:

  1. Reflects customer value (1=weak, 5=perfect)
  2. Measurable (1=very hard, 5=already tracking)
  3. Actionable (1=no control, 5=full control)
  4. Tied to revenue (1=unclear, 5=direct)

Total score should be ≥15/20. If any property scores <3, refine the metric.

Phase 4: Document

Once validated, create a North_Star_Metric.md file using the template in references/output-template.md.

Common Patterns by Product Type

  • Consumption products: Time spent, content consumed
  • Transaction products: # transactions, purchase frequency
  • Creation products: # items created, published
  • Collaboration products: # collaborations, shared items
  • Communication products: # messages sent, connections made

Key Pitfalls to Avoid

❌ Vanity metrics (page views without engagement) ❌ Multiple North Stars (pick ONE) ❌ Lagging indicators for teams (use leading indicators) ❌ Metrics you can't control ❌ Financial metrics as team North Star (use customer-centric metrics)

Resources

For detailed examples, evaluation frameworks, and additional guidance, see:

  • references/examples.md - Product-specific examples by industry
  • references/evaluation-framework.md - Detailed scoring and validation
  • references/output-template.md - Documentation template

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.