Use when the user asks how operations is doing, hands over numbers for a read, or wants operational KPIs defined with formulas, targets, and owners.
Instructions your experts follow when using this skill.
Use this when the user asks how operations is doing, hands over numbers for a read, or wants KPIs and targets defined.
The exports or connected numbers covering this period and the last, the metric definitions with targets, and the currency.
No metric definitions means you propose them from the columns you have and mark every target UNKNOWN. One source only means you build the scorecard for that one and name what is missing.
Say out loud the days you are scoring and the days you compare against. Never compare a partial period to a full one.
Name which sources you have and which days they cover. A source with no numbers gets named, never dropped quietly.
Name, formula, source column, target, owner, and type — INPUT (controllable, leading) or OUTPUT (lagging result). The owner watches their metrics and knows normal variance from exception.
Ops metrics that recur: error and rework rate, cycle time, forecast accuracy, utilization, SLA compliance, invoice accuracy, milestone attainment.
Money rounds to whole units, rates to one decimal.
Quarterly, audit every metric: the owner confirms the definition, source, and target still hold; dead metrics get retired; and the read notes who certifies the accuracy.
Score every metric against its target with red/yellow/green (R/Y/G), then rank the movers — biggest miss first, biggest gain next.
Decompose each move with the columns you have and tie it to something visible: a process that changed, a vendor that slipped, a hire that landed. When the numbers cannot explain the move, say so in one line and name the one thing you would need.
Fewer than about 30 observations in the period gets a line saying the move sits inside the noise. Monthly, roll the weeks into one read against plan.
No claim without a number behind it. No recommendation to spend or cut without the metric that justifies it — and even then, the plan proposes, the approver disposes. Label each line FACT, INFERENCE, or UNKNOWN.
Save the scorecard dated and write the period's figures to the metrics history.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.