ab-testing

Designs and analyzes A/B tests and growth experimentation programs with statistical rigor.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/samuelgabrielsikorjak-sys/techscope-website --skill ab-testing-samuelgabrielsikorjak-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-testing
Source: https://github.com/samuelgabrielsikorjak-sys/techscope-website/tree/main/.claude/skills/marketingskills-main/skills/ab-testing
Command: npx skills add https://github.com/samuelgabrielsikorjak-sys/techscope-website --skill ab-testing-samuelgabrielsikorjak-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often run experiments without clear hypotheses, adequate sample sizes, or disciplined analysis, leading to false positives and wasted traffic. This Skill guides the planning, execution, and analysis of A/B tests so results are statistically valid and actionable. ## Core Features & Use Cases - Hypothesis-Driven Test Design: Structures experiments using a formal hypothesis framework, defines primary, secondary, and guardrail metrics, and selects the right test type (A/B, A/B/n, MVT, split URL). - Sample Size & Duration Planning: Provides quick-reference tables, duration formulas, and guidance on the peeking problem, sequential testing, and multi-variant adjustments. - Growth Experimentation Program: Supports building an ongoing experimentation engine with ICE prioritization, experiment velocity tracking, and a reusable playbook of winning patterns. - Use Case: A marketer wants to test a new pricing page headline. The Skill calculates the required sample size from the baseline conversion rate and traffic, defines metrics, warns against stopping early, and produces a documented test plan. ## Quick Start Ask the assistant to help design an A/B test for a specific page or change, providing your current conversion rate and traffic volume.

Frequently Asked Questions about ab-testing

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%). The Skill provides quick-reference tables by baseline rate and lift, plus links to calculators like Evan Miller's and Optimizely's.

How long should I run an A/B test?

Duration equals total required sample divided by daily exposed traffic. Run at least one full week to capture day-of-week variation, and avoid exceeding 4-8 weeks due to novelty effects and external factors.

Can I stop an A/B test early when results look significant?

Stopping early after peeking inflates false positive rates because early significance can reflect regression to the mean or audience mix shifts. Pre-commit to your calculated sample size, or use sequential testing methods offered by tools like Optimizely or VWO.

What is the difference between an A/B test and a multivariate test?

An A/B test compares two versions with a single change, while a multivariate test (MVT) tests combinations of multiple elements simultaneously. MVT requires dramatically more traffic since combinations multiply, so sequential A/B tests are often better for lower-traffic sites.

What metrics should I track in an A/B test?

Use a three-tier framework: one primary metric tied to your hypothesis for calling the test, secondary metrics that explain why the change worked, and guardrail metrics that must not get worse, such as support tickets or refund rates.

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

Options include increasing your minimum detectable effect, reducing variants, testing higher-traffic upstream pages, combining traffic across similar pages, or making decisions from qualitative data instead of running an underpowered test.