PluginBench
Skill
Pass
Audit score 90

ads-test

agricidaniel/claude-ads

Design and evaluate paid-ad experiments with rigorous hypothesis testing, sample sizing, and decision rules.

What is ads-test?

A framework for planning and analyzing A/B tests and split tests in paid advertising. Use this when designing experiments, calculating required sample sizes and duration, setting up guardrails, or reading out results with statistical rigor.

  • Define causal hypotheses, treatment/control groups, and randomization units
  • Calculate sample size and test duration from statistical assumptions
  • Identify platform constraints, seasonality, interference, and measurement risks
  • Pre-register exclusions, quality checks, and decision thresholds
  • Verify assignment integrity and data completeness before effect estimation
  • Output experiment setup or readout in versioned JSON with plain-language decisions

How to install ads-test

npx skills add https://github.com/agricidaniel/claude-ads --skill ads-test
Claude Code
Cursor
Windsurf
Cline

How to use ads-test

  1. 1.State the decision you need to make, your causal hypothesis, and the treatment vs. control
  2. 2.Specify the randomization unit (user, session, account), population, and primary metric
  3. 3.Declare your assumptions: minimum detectable effect, statistical power, baseline conversion rate, and test duration
  4. 4.Check for platform constraints, overlapping experiments, conversion lag, seasonality, and measurement quality issues
  5. 5.Calculate required sample size and duration; disclose any approximations or simplifications
  6. 6.Pre-register all exclusions, quality checks, analysis methods, and decision thresholds in writing
  7. 7.For readout: verify assignment integrity and data completeness, then estimate effect size and confidence intervals
  8. 8.Return the experiment design or results in JSON format with a clear plain-language recommendation

Use cases

Good for
  • Plan an A/B test for a new ad creative before launching on Facebook or Google Ads
  • Calculate minimum sample size and duration needed to detect a 10% lift in conversion rate
  • Review an experiment readout to confirm statistical significance and decide whether to ship a change
  • Identify potential confounds (seasonality, overlapping experiments) that could bias results
  • Document experiment design and decision rules for stakeholder alignment before running the test
Who it's for
  • Performance marketers designing paid-ad experiments
  • Product managers planning A/B tests for campaign optimization
  • Data analysts setting up experiment infrastructure and analysis
  • Growth teams evaluating ad creative, targeting, or bidding changes

ads-test FAQ

What is a randomization unit and why does it matter?

The randomization unit is what you randomly assign to treatment or control (e.g., user, session, account). It must match your causal question and avoid interference—if one user sees both variants, you have a problem. Choose the smallest unit that prevents spillover.

How do I calculate sample size for my experiment?

Sample size depends on baseline conversion rate, minimum detectable effect, statistical power (usually 80%), and significance level (usually 5%). Use a power calculator with your assumptions. Larger effects and higher baselines require fewer samples; smaller effects require more.

What is a guardrail metric and when should I use one?

Guardrails are secondary metrics you monitor to avoid harming the business (e.g., revenue per user, unsubscribe rate). If a guardrail drops significantly, you stop the test even if the primary metric wins. Set thresholds before the test starts.

Can I stop the test early if results look good?

No. Repeatedly checking results and stopping when favorable inflates false-positive rates. Pre-register your stopping rule (fixed duration or pre-specified sample size) and stick to it.

How do I know if my result is real or just noise?

Check statistical significance (p-value < 0.05 or 95% confidence interval excludes zero), effect size (is it practically meaningful?), and assignment integrity (were users actually randomized?). Underpowered tests produce noisy results; don't call them winners.

Full instructions (SKILL.md)

Source of truth, from agricidaniel/claude-ads.


name: ads-test 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."

Paid Media Experiment

  1. State the decision, causal hypothesis, treatment, control, randomization unit, population, primary metric, guardrails, minimum effect, and stopping rule.
  2. Check platform constraints, overlapping experiments, conversion lag, seasonality, interference, and measurement quality.
  3. Calculate sample and duration from declared assumptions; disclose approximations.
  4. Change one decision surface unless the design explicitly estimates interactions.
  5. Pre-register exclusions, quality checks, analysis, and decision thresholds.
  6. For readout, verify assignment integrity and data completeness before estimating effect and uncertainty.
  7. 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.