ab-testing

Designs and analyzes statistically valid A/B tests and growth experimentation programs.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/Tutitoos/seo-plugin --skill ab-testing-tutitoos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ab-testing
Source: https://github.com/Tutitoos/seo-plugin/tree/main/plugins/seo/skills/ab-testing
Command: npx skills add https://github.com/Tutitoos/seo-plugin --skill ab-testing-tutitoos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often run experiments without hypotheses, stop tests too early, or misread inconclusive results, leading to false positives and wasted traffic. This Skill provides a rigorous framework for planning, running, and analyzing A/B tests and building a continuous experimentation program. ## Core Features & Use Cases - Hypothesis-Driven Test Design: Structures every test around a formal hypothesis, with primary, secondary, and guardrail metrics tied to business value. - Sample Size & Duration Planning: Provides quick-reference tables, duration formulas, and guidance on multiple-variant adjustments and sequential testing. - Growth Experimentation Program: Covers ICE prioritization, experiment velocity tracking, cadence rituals, and a reusable playbook of winning patterns. - Use Case: A product team wants to test a new pricing page headline. The Skill calculates the required sample size from their baseline conversion rate, defines guardrail metrics, warns against peeking at early results, and produces a documented test plan. ## Quick Start Ask the assistant to design an A/B test for your page, providing your current conversion rate, monthly traffic, and the change you want to test.

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 to find the required visitors per variant.

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.

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. Checking results before reaching the planned sample size inflates false positive rates, so commit to the full duration or use sequential testing methods.

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

A/B tests compare two versions with a single change, while multivariate tests evaluate combinations of multiple elements simultaneously. MVT requires dramatically more traffic since combinations multiply, so sequential A/B tests are recommended for lower-traffic pages.

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 must not get worse. This prevents shipping wins that quietly harm other parts of the business.

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 those cases, rely on qualitative research or bolder single changes.