Experiment Runner

Design and execute A/B tests with statistical analysis and structured reports.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill experiment-runner-strategicmilk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Experiment Runner
Source: https://github.com/StrategicMilk/Vetinari-Orchestrastor/tree/main/vetinari/skills/catalog/worker/experiment-runner
Command: npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill experiment-runner-strategicmilk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Development decisions often rely on intuition or isolated observations, causing wasted effort and unreliable improvements. The Experiment Runner offers a systematic approach to design, execute, and analyze controlled experiments, ensuring changes are proven with statistical confidence.

Core Features & Use Cases

  • Hypothesis formulation and experiment design with clear control and treatment groups.
  • Sample size calculation based on statistical power to guarantee sufficient data.
  • Automated data collection and statistical analysis (t‑tests, chi‑square, effect size) delivering a structured JSON report.
  • Use cases include comparing LLM model tiers, evaluating prompt modifications, tuning system parameters, or validating performance hypotheses before deployment.

Quick Start

Ask the worker to run an experiment comparing two model tiers for code review and return the summarized results.

Frequently Asked Questions about Experiment Runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an A/B test to compare different LLM model tiers?

To run an A/B test comparing LLM model tiers, specify your hypothesis, define control and treatment configurations, set the sampling size, and collect metrics. The experiment outputs a structured JSON report with significance testing and effect size.

What is the best way to validate prompt modifications with statistical confidence?

Validating prompt modifications requires designing controlled experiments with clear control and treatment groups. The system calculates sample size based on statistical power and applies t-tests or chi-square analysis to prove changes with statistical confidence.

How do I calculate the sample size needed for an A/B test?

Sample size calculation for an A/B test is based on statistical power to guarantee sufficient data collection. You must specify the hypothesis and metric collection parameters during experiment design to ensure the test detects meaningful effects.

Can I use this to evaluate system parameter settings before deployment?

Yes, you can evaluate system parameter settings before deployment by formulating a performance hypothesis and running a controlled experiment. It compares configurations using automated data collection and statistical analysis to validate improvements.

What statistical analysis methods are applied to the experiment data?

Statistical analysis methods applied to the experiment data include t-tests, chi-square tests, and effect size calculations. These methods process the automated data collection to deliver a structured report with significance testing.

Why does my system performance hypothesis need a controlled experiment?

A controlled experiment is needed because development decisions often rely on intuition or isolated observations, causing unreliable improvements. Systematic hypothesis validation ensures parameter changes are proven with statistical confidence before deployment.