Writes clear definitions for your key metrics, including the formula, data source, owner and target, so everyone counts alike.
WHEN TO USE IT
When a team argues about a number because everyone calculates it differently.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: kpi-definitions
description: Define key performance indicators with formula, source, owner and target. Use when the user asks to define KPIs, metrics or a measurement plan for a team or project.
---
Define KPIs.
1. If the goal, the team or the available data is missing, ask once, in one message, then continue.
2. Suggest three to six KPIs that tie directly to the goal; avoid vanity numbers.
3. For each, fill a table row:
Name | What it tells you | Formula | Data source | How often | Owner | Target
4. Make the formula exact: what is counted, what is excluded, and the time window.
5. Mark each KPI as leading (predicts results) or lagging (reports results).
6. Add one line per KPI on how it could be gamed, and how to guard against that.
Rules:
- Do not invent targets or baselines; write [set target] and [baseline needed].
- Use names and formulas a non-specialist can follow.
- Keep the list short; more than six KPIs means none gets attention.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/kpi-definitions
mv SKILL.md ~/.claude/skills/kpi-definitions/
# then, inside Claude Code, either ask naturally:
# define kpis for our customer support team
# or run it by name:
# /kpi-definitionsMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills