ab-test-setup

Guides A/B test design with mandatory gates for hypothesis, metrics, and sample size.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill ab-test-setup-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test-setup
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/ab-test-setup
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill ab-test-setup-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often launch A/B tests with vague hypotheses, undefined metrics, or insufficient traffic, leading to invalid results and wasted effort. This Skill enforces a rigorous pre-launch workflow so every experiment is statistically sound before any code is written. ## Core Features & Use Cases - Hypothesis Lock Gate: Forces explicit confirmation of the hypothesis, target audience, primary metric, and Minimum Detectable Effect before design begins. - Metrics & Guardrails Framework: Defines one frozen primary metric, contextual secondary metrics, and guardrail metrics that block harmful wins. - Sample Size & Duration Planning: Requires baseline rate, significance level, and power to estimate sample size and test duration upfront. - Use Case: A product manager wants to test a new checkout button color. The Skill walks them through locking the hypothesis, verifying traffic can detect the expected effect, setting guardrails like page load time, and only then approving implementation. ## Quick Start Ask the assistant to help you design an A/B test for a specific product change and follow the guided gates through hypothesis, metrics, and execution readiness.

Frequently Asked Questions about ab-test-setup

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

FAQPage Schema
How do I set up a valid A/B test before launch?

Start by locking a single hypothesis with a defined audience, primary metric, and Minimum Detectable Effect. Then calculate required sample size from baseline rate, significance level, and power, set guardrail metrics, and verify tracking before implementation.

What makes a good A/B test hypothesis?

A valid hypothesis includes an observation or evidence, one specific change, a directional expectation, a defined audience, and measurable success criteria. It must be explicitly confirmed and locked before designing variants or metrics.

When should I use multivariate testing instead of A/B testing?

Use multivariate testing only when you need to measure interaction effects between multiple changes and have very high traffic. Default to a simple A/B test for a single change, since MVT requires substantially larger sample sizes.

Why is peeking at A/B test results early a problem?

Stopping a test early because results look good inflates false positive rates and invalidates statistical conclusions. The Skill enforces committing to a pre-calculated duration and forbids stopping early or redefining success criteria mid-test.

What are guardrail metrics in A/B testing?

Guardrail metrics are measurements that must not degrade during a test, such as page performance or revenue. A significant guardrail failure blocks shipping the variant even if the primary metric wins.

When should I refuse to run an A/B test?

Refuse when the baseline rate is unknown, traffic is insufficient to detect the MDE, the primary metric is undefined, or multiple variables change without proper design. In these cases, delay or redesign the experiment first.