ab-test-setup

Designs statistically valid A/B tests and growth experimentation programs with hypothesis frameworks and sample size guidance.

Updated May 11, 2026
One-click install
npx skills add https://github.com/javierbadapalacio6-beep/TACTIUM --skill ab-test-setup-javierbadapalacio6-beep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ab-test-setup
Source: https://github.com/javierbadapalacio6-beep/TACTIUM/tree/main/TACTIUM/.agents/skills/ab-test-setup
Command: npx skills add https://github.com/javierbadapalacio6-beep/TACTIUM --skill ab-test-setup-javierbadapalacio6-beep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often run A/B tests without proper hypotheses, sufficient sample sizes, or statistical discipline, leading to false positives, wasted traffic, and wrong product decisions. This Skill guides you through designing rigorous experiments and building a continuous experimentation program. ## Core Features & Use Cases - Hypothesis-Driven Test Design: Structures every test around a formal hypothesis framework with primary, secondary, and guardrail metrics. - Sample Size & Duration Planning: Provides quick-reference tables and duration calculators to determine how much traffic and time a test needs before launch. - Experimentation Program Management: Covers ICE prioritization, experiment velocity tracking, and a playbook format for compounding learnings across tests. - Use Case: You want to test a new pricing page headline. The Skill helps you write a strong hypothesis, calculate that you need 12,000 visitors per variant at your 3% baseline, define guardrail metrics like refund rate, and set a fixed 4-week duration to avoid the peeking problem. ## Quick Start Ask the assistant to help you design an A/B test for a specific page or change, providing your current conversion rate and traffic volume.

Frequently Asked Questions about ab-test-setup

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 online calculators like Evan Miller's to find the required visitors per variant.

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 element changes simultaneously requiring very high traffic. Choose based on your traffic volume and how many changes you need to evaluate.

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 calculated sample size and duration, or use sequential testing methods offered by tools like Optimizely or VWO if early stopping is necessary.

What metrics should I track for an A/B test?▼

Use a three-tier framework: one primary metric tied directly to your hypothesis, secondary metrics that explain why the change worked, and guardrail metrics that catch negative side effects. For example, a pricing test might track plan selection rate, time on page, and refund rate.

What should I do when my site lacks traffic for A/B testing?▼

Increase your minimum detectable effect to 20% or more, reduce the number of variants, test higher-traffic pages earlier in the funnel, or combine traffic across similar pages. If none work, rely on qualitative research instead of running an underpowered test.