| name | experiment-validation-skill |
| description | Design or audit an experiment with explicit hypotheses, assignment, metrics, power, stopping rules, and reproducible checks. |
| allowed-tools | ["read_file","list_dir","grep_search","glob_files","write_file","edit_file","apply_patch","notebook_edit","lsp","run_command","artifact_write"] |
Experiment validation
Overview
Make experiment conclusions trustworthy by defining the decision and analysis
before results are known, then checking assignment, instrumentation, statistical
assumptions, and practical significance.
When to Use
Use for A/B tests, model evaluations, benchmarks, simulations, causal claims,
or reviewing an experiment plan or reported result.
Workflow
- Specify the hypothesis, experimental unit, eligibility, assignment method,
primary metric, guardrails, minimum meaningful effect, and decision rule.
- Estimate required sample size or precision and define duration, exclusions,
multiple-comparison policy, and stopping criteria before observing outcomes.
- Validate instrumentation and assignment with sample-ratio, balance, exposure,
missing-data, novelty, and interference checks.
- Run the predeclared analysis first. Report effect sizes and uncertainty, not
only thresholded significance.
- Treat subgroup and post-hoc findings as exploratory unless independently
powered and predeclared. Check robustness to reasonable analysis choices.
- Record protocol deviations, limitations, reproducible artifacts, and whether
the evidence supports ship, iterate, stop, or gather more data.
Verification
Red Flags
- Repeatedly checking significance and stopping at the first favorable result.
- Changing the primary metric after seeing outcomes.
- Claiming general causality from a biased or underpowered sample.