Agent skill · product strategy · borghei
north-star-metric
Define a North Star Metric (NSM) and its input metric tree, with leading indicators, anti-metrics, and counter-metrics. Includes a Python tool that renders the metric tree as a Mermaid diagram.
Why this skill is useful
Adds a Python tool that generates a metric tree diagram and JSON specifications, which are not commonly available in public resources.
What it needs
Requires python installed locally. About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
North Star Metric (NSM) Expert Overview A North Star Metric (NSM) is the single number that best represents the value your product delivers to its customers. Sean Ellis popularized the framing; Amplitude codified the playbook; Lean Analytics calls a related concept the "One Metric That Matters" (OMTM). The NSM is one number, not a dashboard. Its job is to align the entire team -- engineering, marketing, sales, support -- on a shared definition of "we won this quarter." This skill produces a complete NSM specification: the NSM itself, 3-5 input metrics the team can directly influence, the leading indicators that move days or weeks before the inputs, the anti-metrics (things that must NOT move in the wrong direction), and counter-metrics that guard against gaming. The Python tool (metrictreebuilder.py) emits the spec as JSON, Markdown, or a Mermaid tree diagram for a README or Confluence page. This is the first artifact a team should produce after defining strategy and before writing OKRs. Once the NSM is set, OKRs map directly to moving the input metrics, and roadmaps justify themselves by which input metric they target. Core Capabilities NSM selection — score candidates against the five tests (customer value, strategic alignment, leading, single number, movable) and the five Amplitude archetypes. Metric-tree decomposition — break the NSM into 3-5 input metrics with an explicit formula (multiplicative / additive / funnel / ratio). Leading indicators — assign 2-3 per input that move before the input does (the daily/weekly dashboard). Guardrails — anti-metrics (protect the customer) and counter-metrics (protect the business), each with explicit thresholds. Rendering — Mermaid tree, JSON dashboard config, or Markdown via the Python tool. When to Use New product or strategic direction -- before OKRs and roadmap, define the NSM and inputs. Strategic re-alignment -- the dashboard has 47 metrics and no one knows which to optimize. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/north-star-metric