metric-store: what it makes your agent do, and what it refuses.

metric-store is the semantic layer for agent built reporting: one versioned file holding the chosen definition, the formula, the anchor and the owner for every named metric. The agent consults it before computing anything named, so churn means one thing across every page and every export.

The job metric-store does

Two teams disagree about a number almost never because of arithmetic, but because the same word means different things in different rooms. Big platforms answer that with a semantic layer. This skill is that idea sized for an agent: a small, human readable, versioned file that is the record of definitional decisions. Each entry carries the display name, the definition in plain language, the fork it settled and why, the formula over processed fields, the anchor it reconciles to, the unit and format, and an owner. The agent consults the store first, stops and runs the contested metrics play when an entry is missing, and flags any figure whose entry is still contested. Changes are history rather than state, so a definition that moves leaves a dated trail.

What metric-store refuses

A skill is worth what it stops as much as what it produces. These are the refusals written into metric-store, taken from the rules and limits in its own file.

✓Computing a named metric that has no entry. A metric computed before it is defined is a wrong number waiting for its meaning.
✓A definition retyped per page. The text beside the number is sourced from the store, so two pages cannot drift apart quietly.
✓Quietly picking a side. An entry marked contested renders its figure with a visible flag rather than manufacturing the next argument.
✓Editing a definition in place. Changes are versioned and dated, because a store that forgets its own history cannot explain last quarter's number.

10 lines from the metric-store skill file, verbatim

From skills/metric-store/SKILL.md, unedited. Kymira skills are plain text you can read in full before you install them, which is the point of shipping a method rather than a binary.

- key: nrr
  display_name: Net Revenue Retention
  definition: |-
    Trailing-12-month cohort NRR: revenue retained from the customers we
    had 12 months ago, including their expansion, excluding all new logos.
  fork_resolved: |-
    Chose trailing-12 cohort over annualized-monthly (investor convention;
    the annualized figure overstated Q2). Library: /library/saas/nrr.
  formula: "sum(cohort_mrr_now) / sum(cohort_mrr_year_ago)"   # over processed fields
  anchor: "cohort base ties to the billing export's own period-close total"

The failure modes metric-store addresses

These entries in the catalogue of 51 observed failure modes name this skill as what addresses them. Every one was seen in a real build or in our own audits, and none was invented.

Gross, net, and total from one adminThe metric means something else Lift as a multiple or a percentThe metric means something else The calendar forkThe metric means something else The definition that drifted between copiesThe metric means something else The estimate outside its own intervalThe wrapper betrays the numbers

The tier metric-store ships in

Tier	Price	What the tier holds	metric-store
Free	$0	honest-dataviz and the eleven doctrine principles, published in full	Not in this tier
Core Pack	$199	the thirteen craft skills, one-time purchase, lifetime updates	Not in this tier
Everything	$349	all 22 skills, both libraries, the template bank, one-time purchase, lifetime updates	Included

Both paid tiers are a one-time purchase with lifetime updates, and all sales are final: the files are plain text you keep the moment they arrive, so judge the quality on the free skill and the published doctrine first. The pricing section states exactly what each tier contains.

Installing metric-store

A skill is a folder with a SKILL.md file in it. Installing one is copying that folder where your agent looks for skills, with no build step and no dependencies.

mkdir -p ~/.claude/skills
cp -R Kymira/skills/metric-store ~/.claude/skills/

Or open the unzipped pack in Claude Code and say install Kymira, which installs every skill in your tier, or double-click the installer for your system. Cursor reads the same skill as a rule file: copy metric-store.mdc into .cursor/rules/. Skills are read at startup, so start a new session and ask your agent which skills it has available.

Not for

The store makes definitions consistent, not correct: a bad definition applied consistently is consistently wrong, which is why every entry carries an owner and the fork it settled. Definitions rot slower than dashboards, and they still rot. It is a platform skill, so it ships in Everything only.

Last updated 2026-08-29 · Dylan, founder · one of 22 packaged skills, each one a method written down, not a product tour.

See the tiers → All 22 skills The doctrine The failure catalogue