Test metric definitions and source data for freshness, coverage, duplicates, missing values, impossible values, and drift.
Instructions your experts follow when using this skill.
Run this before trusting a KPI, anomaly, cohort, funnel, or experiment result.
Record the source, covered period, extraction time, expected grain, primary or compound key, required fields, field types, allowed ranges, timezone, and known late-arrival window. State the metric formula and population separately from the file schema.
For each issue give the check, expected result, observed result, affected rows and periods, likely metric impact, severity, and owner. Show results before and after any proposed exclusion. Do not drop a bad row silently.
Use blocked when the issue can change the answer enough to affect the stated
decision. Use provisional when the result remains useful with a clear bound.
Never repair values by guess, backfill from an unrelated period, deduplicate on name alone, or hide a failed check. Avoid exposing raw personal or sensitive fields in the report. Treat a pipeline change as a possible cause of a metric move until an independent source confirms the business change.
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.