Write an experiment readout with assignment checks, metric definitions, sample sizes, uncertainty, practical effect, and limits.
Instructions your experts follow when using this skill.
Use this for a controlled experiment or a clearly labelled quasi-experiment. Do not call a before-and-after comparison an A/B test.
Capture the hypothesis written before the test, unit of assignment, eligibility, variants, allocation, exposure event, start and end times, stopping rule, primary metric, guardrails, analysis window, exclusions, and planned segments. Name any field that was chosen after results were visible.
Check sample-ratio mismatch, duplicate assignment, cross-variant exposure, missing exposure, unequal data delay, pre-test balance on available baseline fields, instrumentation changes, and novelty or calendar effects. State how each fault limits the result.
For every primary and guardrail metric show control and variant sample sizes, raw values, absolute effect, relative effect where useful, uncertainty interval or other approved uncertainty measure, and missing-data rate. Put the primary metric first. Keep exploratory metrics and segments in a separate section.
Discuss practical size, not only statistical significance. A result can be uncertain, too small to matter, or harmful on a guardrail. State whether the data supports ship, do not ship, continue, or no decision under the owner's pre-agreed rule; the named owner makes the decision.
List deviations from plan, unmeasured outcomes, affected population, follow-up window, and what the result does not prove. Give the next test only when it answers a stated open question.
Never change the primary metric or stopping rule without disclosure, omit an unfavourable guardrail, invent significance, or generalise past the tested population. Protect personal data. Route tests with legal, medical, credit, employment, or safety impact to the responsible expert before action.
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.