ab-testing

Designs A/B tests with hypothesis formulation, sample sizing, and statistical significance analysis.

3|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill ab-testing-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ab-testing
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/ab-testing
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill ab-testing-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running experiments without proper statistical methodology leads to false conclusions, wasted traffic, and bad product decisions. This Skill provides a rigorous framework for designing, sizing, and analyzing A/B tests so results are statistically valid and actionable. ## Core Features & Use Cases - Hypothesis & Test Design: Formulate measurable hypotheses using the if/then/because template and prioritize test elements by impact potential. - Sample Size & Duration Planning: Calculate required sample sizes from baseline conversion rate, minimum detectable effect, significance level, and power, with quick-reference tables. - Result Analysis & Decision Framework: Evaluate significance with p-values, confidence intervals, guardrail metrics, and a ship/extend/stop decision matrix. - Use Case: A growth team wants to test a new CTA button. Use this Skill to write the hypothesis, determine that 7,000 visitors per variant are needed for a 10% relative lift at 10% baseline CVR, run the test for two full weeks, and produce a structured analysis report with a ship-or-stop recommendation. ## Quick Start Ask the agent to design an A/B test for changing your checkout page headline, including the hypothesis, required sample size, and how to judge the results.

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 baseline conversion rate, minimum detectable effect, significance level (typically 95%), and power (typically 80%). For example, a 5% baseline CVR detecting a 10% relative lift needs roughly 15,000 visitors per variant.

How long should an A/B test run?▼

Run tests for at least one full business week and no more than four weeks. Continue until both the required sample size is reached and at least 7 days of data are collected to capture day-of-week effects.

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

A/B tests compare two variants of one element, multivariate tests examine interactions between multiple elements simultaneously, and bandit tests dynamically shift traffic toward winning variants during the experiment for faster optimization.

Why is peeking at A/B test results early a problem?▼

Peeking before reaching the planned sample size inflates false positive rates three to five times. Significance should only be evaluated at the pre-declared sample size or through sequential testing with alpha-spending corrections.

When should I not use A/B testing?▼

Avoid A/B testing for qualitative feedback collection, usability studies, or exploratory research where there is no clear metric hypothesis. It also fails when traffic is insufficient to reach statistical significance within a reasonable timeframe.