Read an ad test by sample size and spread, and say whether there is a winner yet.
Instructions your experts follow when using this skill.
Use this for one test between two or more ad variants.
State what was tested, the one idea that differs, the dates, the audience, and the measure agreed before the test began. Check that variants got a fair share of spend, ran over the same days, and pointed to the same page. If the setup was uneven, say so first. For more than two variants, name the one comparison set before the test, or choose a method that accounts for all comparisons.
For each variant show impressions, clicks, conversions, spend, and the rate being judged. Give the gap between variants and whether it is larger than the noise at this sample size. Use a stated method and show it. Before calling a winner, state the baseline rate, minimum effect worth detecting, power, and confidence level used to estimate the required sample. For more than two variants, call a winner only for the comparison set before the test, or after using and showing a test that accounts for all comparisons.
Say one of:
Recommend keep running, stop, or roll out, and the next idea worth testing.
Do not pause, scale, or edit ads yourself; recommend for approval. Never call a winner early or invent figures to fill a thin test.
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.