ab-testing

Designs and analyzes A/B tests and growth experimentation programs with statistical rigor.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/usmangurowa/sifter --skill ab-testing-usmangurowa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-testing
Source: https://github.com/usmangurowa/sifter/tree/main/.agents/skills/ab-testing
Command: npx skills add https://github.com/usmangurowa/sifter --skill ab-testing-usmangurowa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often run experiments without clear hypotheses, stop tests too early, or misread results, leading to false conclusions and wasted traffic. This Skill guides you through designing statistically valid A/B tests, calculating sample sizes, selecting metrics, and building a continuous experimentation program. ## Core Features & Use Cases - Hypothesis-Driven Test Design: Structures experiments using a formal hypothesis framework with primary, secondary, and guardrail metrics. - Sample Size & Duration Planning: Provides quick-reference tables, duration formulas, and guidance for A/B, A/B/n, and multivariate tests. - Growth Experimentation Program: Covers ICE prioritization, experiment velocity tracking, and building a playbook of proven patterns. - Use Case: You want to test a new pricing page headline. The Skill helps you write a hypothesis, calculate that you need 12,000 visitors per variant at a 3% baseline, define guardrail metrics, and commit to a fixed duration to avoid the peeking problem. ## Quick Start Ask the assistant to help you design an A/B test for a specific page or change, providing your current conversion rate and traffic volume.

Frequently Asked Questions about ab-testing

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

FAQPage Schema
How do I calculate sample size for an A/B test?

Sample size depends on your baseline conversion rate, minimum detectable effect, significance level (usually 95%), and power (usually 80%). Use the quick reference tables in the sample size guide or online calculators like Evan Miller's to find the required visitors per variant.

How long should I run an A/B test?

Run until you reach your pre-calculated sample size, with a minimum of one full week to capture day-of-week variation. Avoid running longer than 4-8 weeks due to novelty effects and external factors, and never stop early based on peeking at results.

Should I stop an A/B test early if one variant is winning?

No. Stopping early based on peeked results inflates false positive rates because early significance can reflect regression to the mean or audience mix shifts. If you need early-stopping flexibility, use sequential testing methods supported by tools like Optimizely or VWO.

What is the difference between A/B testing and multivariate testing?

A/B testing compares two versions with a single change, while multivariate testing (MVT) tests combinations of multiple elements simultaneously. MVT requires dramatically more traffic since combinations multiply, so sequential A/B tests are often better for lower-traffic sites.

What metrics should I track in an A/B test?

Define three tiers: a primary metric tied directly to your hypothesis, secondary metrics that explain why the change worked, and guardrail metrics that should not get worse. This prevents wins on one metric from hiding harm elsewhere.

When should I not run an A/B test?

Skip testing when traffic cannot reach the required sample size within a reasonable duration, when the change is too small to detect, or when the risk of a bad variant is unacceptable. In these cases, rely on qualitative research or test upstream where traffic is higher.