Metrics definitions
Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.
npx -y skills add shinzoxD/knackbox --skill metrics-definitionsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Define product and business metrics with precise numerators, denominators, and edge cases. Use whenever the user asks what to measure, how to define a KPI, North Star, activation, retention, churn, or event taxonomy for analytics — even for a rough product idea.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.0 KB, 350 tokens by cl100k_base, as published. Nobody here has run it
Metrics Definitions
A metric without a definition is a slogan. Write metrics so two analysts get the same number from the same warehouse.
Workflow
- Clarify decision the metric informs (grow activation? reduce churn?).
- Propose a small set: North Star (optional), input metrics, guardrails.
- For each metric: formula, grain, time window, filters, owners.
- Map required events/properties (tracking plan lite).
- List non-goals and common misreads.
- Suggest validation checks (reconciliation, anomaly thresholds).
Output format
## Metrics spec: <product/area>
### North Star (if any)
**Name:** …
**Formula:** …
**Why it matters:** …
### Input metrics
| Name | Formula | Grain | Window | Owner |
### Guardrails
| Name | Formula | Alert idea |
### Tracking requirements
- event.property …
### Edge cases
- …
### Anti-metrics / misreads
- …
Rules
- Always define numerator, denominator, and who is in the population.
- Prefer ratios with explicit windows (e.g. D7 retention) over vague "engagement".
- Separate leading indicators from lagging outcomes.
- Do not invent data you cannot collect; flag instrumentation gaps.
- One source of truth name per metric; note deprecated aliases.
- Call out gaming risk (metrics people will optimize naively).
Edge cases
- B2B seats vs accounts: state which entity is the unit.
- Marketplace: define both sides; avoid averaging away imbalance.
- Early stage: fewer metrics, higher instrumentation quality.