ab-test-setup

Plan and execute A/B experiments with hypothesis definition and sample-size calculation.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/devCharuzu/philfida-taskmanage --skill ab-test-setup-devcharuzu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test-setup
Source: https://github.com/devCharuzu/philfida-taskmanage/tree/main/.windsurf/skills/ab-test-setup
Command: npx skills add https://github.com/devCharuzu/philfida-taskmanage --skill ab-test-setup-devcharuzu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The A/B Test Setup Skill helps teams plan and design experiments that yield statistically valid, actionable results, reducing guesswork in product decisions.

Core Features & Use Cases

  • Hypothesis framework and structured planning to ensure clear, testable predictions.
  • Support for common test types (A/B, A/B/n, MVT, split URL) with guidance on when to use each.
  • Sample size estimation, statistical rigor, and pre-defined metrics (primary, secondary, guardrails).
  • Guidance on designing variants, traffic allocation, and implementation approaches (client-side vs server-side).
  • Running, monitoring, and analyzing results, plus standardized documentation templates.

Quick Start

Define a test hypothesis, select a primary metric, and implement a single, controlled change to 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 calculate sample size for an A/B test to ensure statistical significance?

Sample size calculation requires defining your primary metric, expected conversion rate lift, and significance threshold. This Skill provides structured estimation workflows to ensure your A/B test gathers sufficient data for statistically valid results before analysis.

What is the best way to structure an A/B test hypothesis for product experiments?

A structured A/B test hypothesis predicts the causal impact of a single-variable change on a specific metric. This Skill enforces a formal framework to define clear, testable predictions for landing pages, checkout flows, and pricing pages.

How do I choose between A/B, A/B/n, and multivariate tests for my landing page?

A/B tests compare a single variant against control, A/B/n tests multiple variants, and MVT evaluates multiple variables simultaneously. This Skill guides you on when to use each test type based on your experiment's scope and traffic constraints.

Do I need to define guardrail metrics before running a pricing page experiment?

Yes, defining primary, secondary, and guardrail metrics before execution prevents unintended negative impacts. This Skill helps you pre-define these metrics to monitor performance and maintain statistical rigor during pricing page tests.

How should I allocate traffic for a server-side checkout flow experiment?

Traffic allocation for checkout flow experiments depends on your sample size requirements and risk tolerance. This Skill provides guidance on splitting visitors and choosing between client-side and server-side implementation approaches.

Why does my A/B test result lack statistical validity despite reaching sample size?

Statistical validity can be compromised by poor variant design, multiple comparisons, or early peeking at results. This Skill enforces a formal workflow for structured results interpretation and standardized documentation to prevent these issues.