ab-testing

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

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Nurdiansyah0/nurdiansyahlabs-react --skill ab-testing-nurdiansyah0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ab-testing
Source: https://github.com/Nurdiansyah0/nurdiansyahlabs-react/tree/main/.agents/skills/ab-testing
Command: npx skills add https://github.com/Nurdiansyah0/nurdiansyahlabs-react --skill ab-testing-nurdiansyah0

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 provides a structured methodology for planning, running, and analyzing A/B tests so decisions are based on statistically valid evidence. ## 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. - Growth Experimentation Program: Covers ICE prioritization, experiment velocity tracking, cadence rituals, and a reusable experiment playbook for compounding wins. - Use Case: A team wants to test a new pricing page headline. The Skill calculates required sample size from their baseline conversion rate and traffic, defines metrics, warns against stopping early, and produces a documented test plan. ## Quick Start Ask the assistant to help 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, 95% significance, and 80% 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.

Why is it bad to stop an A/B test early when results look significant?▼

Peeking at results and stopping early inflates false positive rates because early significance can reflect regression to the mean, day-of-week effects, or audience mix shifts. Pre-commit to a sample size, or use sequential testing methods if early stopping is required.

What is the difference between an A/B test and a multivariate test?▼

An A/B test compares two versions with a single change, while a multivariate test (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 must not get worse. This prevents wins on one metric from hiding harm elsewhere.

What can I do if my site does not have enough traffic for A/B testing?▼

Options include increasing your minimum detectable effect, reducing variants, testing higher-traffic pages earlier in the funnel, combining traffic across similar pages, or relying on qualitative research instead of a formal test.