ab-testing

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often run experiments without clear hypotheses, adequate sample sizes, or disciplined analysis, leading to false positives and wasted traffic. This Skill guides the design, execution, and analysis of A/B tests and builds a continuous experimentation program with statistically valid, actionable results. ## Core Features & Use Cases - Hypothesis-Driven Test Design: Structures hypotheses with observation, predicted outcome, audience, and measurable metrics, then selects the right test type (A/B, A/B/n, MVT, split URL). - Sample Size & Duration Planning: Provides quick-reference tables, duration formulas, and sequential testing guidance to prevent underpowered tests and the peeking problem. - Growth Experimentation Program: Covers ICE prioritization, experiment velocity tracking, cadence rituals, and a playbook for compounding winning patterns. - Use Case: A team wants to test a new pricing page headline. The Skill calculates required sample size from baseline conversion and traffic, defines primary/secondary/guardrail metrics, and produces a documented test plan. ## Quick Start Ask the assistant to design an A/B test for a specific page change, providing your current conversion rate and monthly traffic.

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, 95% significance level, and 80% statistical power. Use the quick reference tables in the sample size guide or calculators like Evan Miller's or Optimizely's to get per-variant requirements.

How long should I run an A/B test?▼

Run until you reach the 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.

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.

Why is my A/B test showing significance after only a few days?▼

Early significance is often misleading due to the peeking problem, regression to the mean, and audience mix shifts across days. Checking results before reaching sample size inflates false positive rates, so commit to the full pre-calculated duration or use sequential testing methods.

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

Use a three-tier framework: one 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 cherry-picking and protects against harmful side effects.

When should I not run an A/B test?▼

Skip testing when traffic cannot support detecting a meaningful effect within a reasonable duration, or when the change is too small to matter. Alternatives include increasing the minimum detectable effect, testing higher-traffic funnel steps, or deciding based on qualitative research.