ab-test-setup

Designs statistically valid A/B tests with hypotheses, sample sizes, and metrics.

10|10|Updated May 13, 2026
One-click install
npx skills add https://github.com/yuluyangguang1/openclaw-portable --skill ab-test-setup-yuluyangguang1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test-setup
Source: https://github.com/yuluyangguang1/openclaw-portable/tree/main/system/skills-zh/marketing-skills-zh/references/ab-test-setup
Command: npx skills add https://github.com/yuluyangguang1/openclaw-portable --skill ab-test-setup-yuluyangguang1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often run A/B tests without clear hypotheses, adequate sample sizes, or disciplined analysis, leading to false positives and wasted traffic. This Skill guides the full experiment lifecycle so tests produce statistically valid, actionable results. ## Core Features & Use Cases - Hypothesis Structuring: Builds strong hypotheses using an observation-change-effect-audience-metric framework. - Sample Size & Duration Planning: Provides reference tables and formulas for minimum detectable effect, significance, and power. - Metrics & Analysis Framework: Defines primary, secondary, and guardrail metrics plus result interpretation and documentation templates. - Use Case: A growth marketer wants to test a new pricing page headline. The Skill calculates required sample size from the baseline conversion rate, defines guardrail metrics like refund rate, and produces a complete test plan document. ## Quick Start Help me design an A/B test for my signup page headline with a 3% baseline conversion rate and 5,000 daily visitors.

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 (typically 95%), and statistical power (typically 80%). For example, detecting a 20% lift on a 3% baseline requires about 12,000 visitors per variant.

How long should an A/B test run?

Run tests for at least one to two full business cycles, usually one to two weeks, and until the pre-calculated sample size is reached. Avoid running too long to prevent novelty effects and external factors from skewing results.

What is the difference between A/B testing and multivariate testing?

A/B testing compares two versions with a single change, while multivariate testing evaluates multiple changes in combination to detect interactions. MVT requires significantly more traffic and more complex analysis.

Why is peeking at A/B test results early a problem?

Stopping a test early when results look significant inflates false positive rates and exaggerates effect sizes. Pre-commit to a sample size, or use sequential testing methods if you must monitor results continuously.

Should I use client-side or server-side A/B testing tools?

Client-side tools like Optimizely or VWO work well for marketing pages and copy changes but may cause flicker. Server-side testing suits product features and performance-sensitive pages but requires development work.