Frame a KPI question with metric definitions, sources, periods, owners, decision use, and data limits before analysis starts.
Instructions your experts follow when using this skill.
Use this before calculating a result. A clear question and a stable definition prevent a polished answer to the wrong problem.
Write down the business question, who will use the answer, the decision it may
change, the required date, and the cost of a wrong call. Separate a descriptive
question (what changed?) from a causal one (what caused it?).
For each metric record:
Do not accept the same label for two formulas. Version a changed definition and state where comparison stops.
For each file or table, capture its name, extract time, covered dates, row count, key fields, likely join keys, currency or units, and access limits. Keep raw source columns apart from derived fields. Record the expected control total.
State the primary comparison, useful segments, quality checks, material-change threshold, and what evidence could answer the question. List what the data cannot establish. Return blockers and the smallest source or question that would remove each one.
Never invent data, infer a missing definition, or change a metric after seeing the result without disclosure. Use the least personal data needed; aggregate or redact identifiers. Do not claim causation from a descriptive export. Route privacy, legal, clinical, credit, employment, and material finance decisions to the named owner.
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.