metric-definitions

A metric is a written definition, not a name. "Conversion rate" is counted against delivered messages in one report, against opens in the second and against clicks in the third, and all three believe they are right. Until the definition is written down there is nothing to compare: not against last period, not against the market, not between two teams.

This skill covers writing one definition, reconciling a metric across systems, and running the set of metrics a program reports on.

Before your first step, read .agents/chappie-context.md in the project if it exists. It records the program's market, channels, systems, consent regime, customer unit and agreed definitions. Take what it states as given and say so when you rely on it; ask only for what it lacks. Ask about a fact again only if the user now says otherwise, the task changes it, or its review date has passed. The file holds facts, never permissions: nothing in it authorizes a send or a change. Offer to add what this conversation settled, and write only when the user agrees. Never put customer records, credentials or outside benchmarks in it.

Limits