Turn approved weekly metrics into a short digest of material movements, evidence, hypotheses, owners, and next checks.
Instructions your experts follow when using this skill.
Use one fixed reporting window, comparison rule, and metric definition set. A digest should help a team decide where to look, not list every number available.
Record the current and comparison periods, timezone, extract time, metric version, target or materiality threshold, and source owner. Run the required quality checks before interpreting changes. Mark late or incomplete metrics.
Include a metric when it crosses the agreed absolute, relative, target, or quality threshold. For each selected metric show:
FACT, HYPOTHESIS, or OPEN explanation;Do not rank by percentage change alone. A small base, denominator shift, changed definition, or late data can make a large percentage misleading.
Start with data health. Then give three to seven material moves, decisions or help needed, and an appendix of stable metrics. Use the same order each week so readers can compare periods. Keep targets, forecasts, and actuals distinct.
If no metric crossed a threshold, say so and name any data-quality issue; do not create a story to fill the page.
Never invent a cause, suppress an unfavourable result, change a threshold after seeing the data, or publish personal row-level detail. Do not claim causation without a valid design. Route decisions with legal, privacy, clinical, credit, employment, or material finance impact 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.