Paid Media Experiment
Design and evaluate paid-ad experiments with hypotheses, randomization units, sample-size and duration assumptions, guardrails, platform experiment tools, analysis, and decision rules.
How to use it
- Hit Copy the whole skill.
- Claude: ⋯ → Download .md, then Customize → Skills → Add → Upload skill.
ChatGPT: make a Project and paste it into Instructions.
Neither? Paste it at the top of a new chat — it works for that chat. - Describe your job in plain words. The AI follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit AgriciDaniel/claude-ads/skills/ads-test#main ~/.claude/skills/ads-testFor one project only, change the path to .claude/skills/ads-test.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Show the full text22 lines
Paid Media Experiment
- State the decision, causal hypothesis, treatment, control, randomization unit, population, primary metric, guardrails, minimum effect, and stopping rule.
- Check platform constraints, overlapping experiments, conversion lag, seasonality, interference, and measurement quality.
- Calculate sample and duration from declared assumptions; disclose approximations.
- Change one decision surface unless the design explicitly estimates interactions.
- Pre-register exclusions, quality checks, analysis, and decision thresholds.
- For readout, verify assignment integrity and data completeness before estimating effect and uncertainty.
- Return setup or readout in versioned JSON with a plain-language decision.
Do not repeatedly peek and stop on a favorable result, call underpowered noise a winner, or generalize beyond the tested population.
| 1 | |
| 2 | name ads-test |
| 3 | description "Design and evaluate paid-ad experiments with hypotheses, randomization units, sample-size and duration assumptions, guardrails, platform experiment tools, analysis, and decision rules. Use for A/B test, split test, experiment design, hypothesis, statistical significance, sample size, test duration, or experiment readout." |
| 4 | |
| 5 | |
| 6 | # Paid Media Experiment |
| 7 | |
| 8 | State the decision, causal hypothesis, treatment, control, randomization unit, |
| 9 | population, primary metric, guardrails, minimum effect, and stopping rule. |
| 10 | Check platform constraints, overlapping experiments, conversion lag, seasonality, |
| 11 | interference, and measurement quality. |
| 12 | Calculate sample and duration from declared assumptions; disclose approximations. |
| 13 | Change one decision surface unless the design explicitly estimates interactions. |
| 14 | Pre-register exclusions, quality checks, analysis, and decision thresholds. |
| 15 | For readout, verify assignment integrity and data completeness before estimating |
| 16 | effect and uncertainty. |
| 17 | Return setup or readout in versioned JSON with a plain-language decision. |
| 18 | |
| 19 | Do not repeatedly peek and stop on a favorable result, call underpowered noise a |
| 20 | winner, or generalize beyond the tested population. |
| 21 | |
| 22 |
Discussion
Alternatives
Also in A/B testingA/B Test SetupWhen the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.Conversion Rate Optimization (CRO)When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'form abandonment,' 'nobody's converting,' 'low conversion rate,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups.Signup Flow CROWhen the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.A Free Giveaway That Grows Your Email ListTell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.