ab-test-setup

Design and validate A/B tests with hypotheses, sample sizes, and metrics.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/samzzi/dotfiles --skill ab-test-setup-samzzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test-setup
Source: https://github.com/samzzi/dotfiles/tree/main/config/claude/skills/ab-test-setup
Command: npx skills add https://github.com/samzzi/dotfiles --skill ab-test-setup-samzzi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan, design, and run rigorous A/B tests to determine the most effective changes and reduce guesswork in product and marketing decisions.

Core Features & Use Cases

  • Hypothesis framing and documentation to ensure test rationale is explicit.
  • Test design, type selection (A/B, A/B/n, MVT), and sample size estimation with guardrails and metrics.
  • End-to-end workflow templates for plan, execution, analysis, and reporting across product, marketing, and UX experiments.

Quick Start

Draft a full test plan by defining a hypothesis, selecting a test type, estimating the sample size, and outlining success criteria.

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 plan with hypothesis and sample size estimation?

To design an A/B test plan, frame your hypothesis explicitly, select a test type, estimate sample size, and outline success criteria. This structured workflow provides templates to document test rationale, metrics, and reproducible analysis formats for rigorous experiments.

What is the difference between A/B, A/B/n, and MVT test types for experimentation?

A/B tests compare one variant against a control, A/B/n compares multiple variants simultaneously, and MVT evaluates multiple variable combinations. Selecting the right experimentation type depends on how many changes you need to validate and the traffic required for significance.

When do I need guardrail metrics and primary metrics for an A/B test?

You need guardrail metrics to prevent unintended negative impacts on business health during an A/B test, while primary metrics directly measure the hypothesis. Structuring both ensures experiments validate impactful changes without degrading core user experience.

Can I use this A/B testing workflow for product, marketing, and UX scenarios?

Yes, this A/B testing workflow applies across product, marketing, and UX scenarios. It enforces a structured process with test plans, pre-launch checklists, and documentation templates to ensure auditable experiments regardless of your specific domain.

What's the best way to document A/B test results for reproducible analysis?

The best way to document A/B test results is using structured reporting templates that capture hypothesis, metrics, variants, and outcomes. Reproducible analysis formats ensure your experiments are rigorous, auditable, and transparent for future review.