agentleFS
fzfcleefzfclee/consulting-skills/skills/north-star-metric/SKILL.md

north-star-metric

Skill6 starsChanged 4 months agoApache-2.0View on GitHub

Use when a product, service, or business needs one organizing success metric plus supporting driver logic. Use when applying the North Star Metric consulting method and when a user asks for North Star Metric, method execution, structured diagnosis, or action planning.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-okrs, positioning-ideas and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skytiger6724Skill

    brainstorm-okrs

    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.

    Also in 5 projects that use this

  • About-IntelligenceSkill

    positioning-ideas

    Brainstorm product positioning ideas differentiated from competitors.

    Also in 5 projects that use this

  • About-IntelligenceSkill

    gtm-motions

    Identify the best GTM motions and tools across 7 motion types: Inbound, Outbound, Paid Digital, Community, Partners, ABM, and PLG.

    Also in 5 projects that use this

  • skytiger6724Skill

    outcome-roadmap

    Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

    Also in 5 projects that use this

  • miovragSkill

    strategy-red-team

    Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

    Also in 4 projects that use this

  • +3 more from About-Intelligence
  • +4 more from skytiger6724

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to run North Star Metric as a practical consulting method, not as a generic framework explanation.

    line 9
  2. Distinctive:

    Add input metrics and guardrail metrics.

    line 14
  3. Very specific:

    If an input is missing, do not block automatically.

    line 25
  4. Distinctive:

    Do not use when customer value, product scope, or strategic objective is unclear, or when one metric would hide harm across segments.

    line 29
  5. Distinctive:

    Keep wording professional and plain enough that a smart non-specialist can use the output directly.

    line 86

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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

Use this skill to run North Star Metric as a practical consulting method, not as a generic framework explanation.

Method Notes

  • The metric should reflect recurring customer value and be a leading indicator of growth.
  • Add input metrics and guardrail metrics.

Required Inputs

Collect or infer these inputs before execution:

  • business model
  • user value proposition
  • growth goal
  • available metrics

If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use when customer value, product scope, or strategic objective is unclear, or when one metric would hide harm across segments. Pair the north star with explicit guardrails.

Adjacent Methods

  • metrics-tree: connect an outcome to input drivers and guardrails.
  • balanced-scorecard: manage several strategic perspectives rather than one value metric.

Step-by-Step Execution

StepRequired inputHow to executeOutput
Define core valueProduct/service value proposition and user segment.State the recurring customer value the product should create.Core value statement.
Propose NSMCore value, growth model, retention logic.Choose one metric that captures delivered value and predicts growth.North Star metric candidate.
Map input metricsUser behaviors and business drivers.Identify measurable behaviors that drive the NSM.Input metric tree.
Add guardrailsQuality, margin, risk, user trust, support burden.Define counter-metrics that prevent gaming or regression.Guardrail set.
Validate usabilityData availability, team ownership, actionability.Check whether teams can influence and review the metric.NSM operating plan.

Output Template

### 1. Core Value
User:
Value event:
Frequency:
Business linkage:

### 2. North-Star Candidate
Metric:
Formula:
Why it reflects value:
Manipulation risk:

### 3. Input Metrics And Guardrails
| Metric | Type | Mechanism | Owner | Threshold |
|---|---|---|---|---|
|  |  |  |  |  |

### 4. Operating Plan
| Review | Cadence | Decision | Validation / revision trigger |
|---|---|---|---|
|  |  |  |  |

### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:

Quality Gate

  • Produce the method-specific outputs for Core Value, North-Star Candidate, Input Metrics And Guardrails; do not substitute a generic framework summary.
  • Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption.
  • Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method.
  • Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal.
  • State missing inputs and the smallest validation action instead of inventing precision.
  • Keep wording professional and plain enough that a smart non-specialist can use the output directly.

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.