ab-test-setup

Design statistically rigorous A/B test plans with hypotheses, metrics, and sample sizes.

3|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/BadTechBandit/skills --skill ab-test-setup-badtechbandit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test-setup
Source: https://github.com/BadTechBandit/skills/tree/main/marketing-skills-for-agents/skills/ab-test-setup
Command: npx skills add https://github.com/BadTechBandit/skills --skill ab-test-setup-badtechbandit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you plan A/B (and related) experiments so results are statistically valid, measurable, and decision-ready instead of confusing or misleading.

Core Features & Use Cases

  • Hypothesis-driven test design: Builds a clear hypothesis (what you expect to change and for whom) so your experiment has a measurable outcome.
  • Statistical rigor and planning: Guides primary/secondary/guardrail metric selection, sample size, and traffic allocation to reduce false positives and incorrect calls.
  • Practical execution and analysis: Covers implementation approaches (client vs server), pre-launch and QA checklists, analysis criteria, and the peeking problem to prevent premature wins.

Quick Start

Ask an agent to create an A/B test plan for your pricing or signup page by choosing a single change, writing a hypothesis, selecting metrics, estimating sample size and duration from your baseline conversion and traffic, and recommending how to run and interpret the test.

Frequently Asked Questions about ab-test-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design an A/B test with a valid hypothesis and sample size?

A/B test design starts with a single-variable change and a clear hypothesis. You then select primary, secondary, and guardrail metrics, calculate sample size from your baseline conversion rate, and estimate test duration based on daily traffic to achieve statistical significance.

What is the peeking problem in conversion rate optimization experiments?

The peeking problem in A/B testing happens when you check experiment results prematurely, which inflates false positives. You prevent incorrect calls by enforcing predefined confidence criteria, waiting for the planned duration, and monitoring guardrail metrics.

When should I use multivariate testing instead of a standard A/B test?

Use multivariate testing (MVT) instead of a standard A/B test when you need to evaluate the interaction effects between multiple page variables simultaneously. Standard A/B tests enforce a single-variable change, while MVT handles complex page-level optimization.

Can I run an A/B/n test plan for my pricing page with multiple variants?

Yes, you can run an A/B/n test for a pricing page by allocating traffic across multiple variants. The planning process calculates sample sizes and duration requirements to confidently identify the best performing variant for conversion rate optimization.

What metrics do I need for a split-URL test on a signup page?

For a split-URL test on a signup page, you need primary metrics to track the main conversion goal, secondary metrics for supporting insights, and guardrail metrics to monitor for unexpected negative impacts on user experience or business health.