ab-testing

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

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill ab-testing-ferrarifankid04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-testing
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/claude-code/skills/ab-testing
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill ab-testing-ferrarifankid04

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 provides a structured framework for planning, running, and analyzing A/B tests and building a continuous experimentation program. ## Core Features & Use Cases - Hypothesis & Test Design: Builds structured hypotheses, selects test types (A/B, A/B/n, MVT, split URL), and defines primary, secondary, and guardrail metrics. - Sample Size & Duration Planning: Provides quick-reference sample size tables, duration formulas, and guidance on the peeking problem and sequential testing. - Experimentation Program Management: Covers ICE prioritization, experiment velocity tracking, playbooks, and documentation templates for a continuous growth loop. - Use Case: A product marketer wants to test a new pricing page headline. The Skill calculates the required sample size from the baseline conversion rate, defines metrics, warns against stopping early, and produces a documented test plan. ## Quick Start Ask the assistant to help you design an A/B test for a specific 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, significance level (usually 95%), and power (usually 80%). 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. Divide total required sample by daily traffic to estimate duration, and avoid tests longer than 4-8 weeks due to novelty effects and external factors.

Can I stop an A/B test early when results look significant?

Stopping early after peeking at results inflates false positive rates and leads to wrong decisions. Pre-commit to your sample size and duration; if you need early-stopping flexibility, use sequential testing methods supported by tools like Optimizely or VWO.

What is the difference between A/B, A/B/n, and multivariate tests?

A/B tests compare two versions with a single change, A/B/n tests multiple variants requiring roughly 1.5-2x more traffic, and multivariate tests combine multiple elements simultaneously, multiplying combinations and demanding very high traffic volumes.

What should I do when my traffic is too low for A/B testing?

Increase your minimum detectable effect to 20%+ lift, reduce the number of variants, test higher-traffic pages earlier in the funnel, or combine traffic across similar pages. If none work, make decisions from qualitative data instead of running underpowered tests.

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

Define one primary metric tied directly to your hypothesis, secondary metrics that explain why the change worked, and guardrail metrics that must not degrade. For example, a pricing page test might track plan selection rate, time on page, and refund rate respectively.