ads-test covers both ends of a paid media experiment. For setup it states the decision, causal hypothesis, treatment, control, randomization unit, population, primary metric, guardrails, minimum effect and stopping rule, and checks platform constraints, overlapping experiments, conversion lag, seasonality and interference.
For a readout it verifies assignment integrity and data completeness before estimating the effect and its uncertainty. Either way the result comes back as versioned JSON with a decision written in everyday language.
What You Get
- A test design with hypothesis, treatment, control, randomization unit and primary metric
- Sample size and duration estimates with their assumptions stated
- Guardrails, minimum effect and a stopping rule
- A readout with assignment integrity and data completeness checks
- Versioned JSON with a decision in everyday language
Common Use Cases
- Planning an A/B test of ad creative or audiences
- Deciding how long a split test must run
- Reading out a finished platform experiment
- Checking whether overlapping experiments or conversion lag undermine a result
What Makes It Unique
The instructions rule out common experiment mistakes: peeking repeatedly and stopping on a favorable result, calling underpowered noise a winner, and generalizing beyond the tested population. Exclusions and decision thresholds are fixed before the test, and approximations in the sample size math are disclosed.
Under The Hood
The skill is a short set of written instructions with no scripts of its own. The agent works from the test setup or results you provide and does the sample size calculation itself from your assumptions. It returns versioned JSON and does not call web services or run commands. It does not change any ad account or start a platform experiment.