ab-test-setup

Design and run statistically rigorous A/B tests with sample-size calculations and decision criteria.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/Elimiz21/scam-dunk-re-write-claude-code --skill ab-test-setup-elimiz21
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test-setup
Source: https://github.com/Elimiz21/scam-dunk-re-write-claude-code/tree/main/.agents/skills/ab-test-setup
Command: npx skills add https://github.com/Elimiz21/scam-dunk-re-write-claude-code --skill ab-test-setup-elimiz21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

A/B Test Setup helps teams design and execute statistically valid experiments to determine whether changes to a product, feature, or message improve outcomes.

Core Features & Use Cases

  • Hypothesis-driven planning: formalizes a test plan with a clear hypothesis, primary/secondary metrics, and guardrails.
  • Sample size and duration planning: provides guidelines and references for calculating required sample sizes and estimating test duration.
  • Variant design and documentation: templates for documenting variants, analyses, and decisions across teams.
  • Use Case: when evaluating a homepage headline, pricing table, or onboarding flow, this skill guides the end-to-end CRO process from framing to decision.

Quick Start

Plan your first test by stating a hypothesis, selecting a primary metric, and outlining the expected sample size and duration.

Frequently Asked Questions about ab-test-setup

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

FAQPage Schema
How do I set up an A/B test with a hypothesis-driven workflow?

To set up an A/B test, formalize a clear hypothesis, define primary and secondary metrics, establish guardrails, document variants, and outline decision criteria to rigorously validate product changes.

What are primary, secondary, and guardrail metrics in A/B testing?

A/B testing metrics define experiment outcomes: primary metrics measure the main goal, secondary metrics track adjacent impacts, and guardrails monitor thresholds to prevent negative side effects during variant evaluation.

How do I calculate sample size and estimate test duration for an A/B experiment?

A/B test sample size and duration calculations use statistical significance guidelines to determine required observations, ensuring experiments run long enough to validate messaging, pricing, or user flow changes confidently.

Can I use this A/B testing workflow for pricing tables and onboarding flows?

Yes, this A/B testing workflow applies to evaluating homepage headlines, pricing tables, and onboarding flows, guiding the end-to-end conversion rate optimization process from hypothesis framing to final decisions.

What is the best way to document A/B test variants and decisions across teams?

The best way to document A/B test variants is using structured templates that record hypotheses, variant designs, metric definitions, and decision criteria, ensuring clear cross-team communication and experiment tracking.

Why do I need statistical significance and decision criteria for my A/B test?

Statistical significance and decision criteria are required for A/B testing to prevent false positives, ensuring that measured impacts between variants represent true effects rather than random sampling variation.