suede-ab-testing

Designs A/B tests with predeclared hypotheses, sample sizes, durations, and decision rules.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-ab-testing-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-ab-testing
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-ab-testing
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-ab-testing-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams routinely call A/B test winners too early, run underpowered tests, or skip hypothesis discipline, producing results that do not replicate. This Skill enforces a predeclared experimentation process so test outcomes are statistically valid and actionable. ## Core Features & Use Cases - Hypothesis and Test Design: Structures hypotheses in a because-we-believe-we-will-know framework, classifies tests as A/B, A/B/n, MVT, or split URL, and defines primary, secondary, and guardrail metrics. - Sample Size and Duration Planning: Provides quick-reference sample size tables by baseline conversion rate and minimum detectable effect, plus duration rules covering day-of-week cycles, B2B business cycles, and sequential testing options. - Experiment Program Management: Supports ICE prioritization, experiment velocity tracking, playbook documentation of winning patterns, and weekly-to-quarterly review cadences. - Use Case: A marketer wants to test a new pricing page headline with 15,000 monthly visitors and a 3.2% signup rate; the Skill calculates the required sample per variant, sets a minimum two-week duration, defines the decision rule, and blocks any early winner call. ## Quick Start Ask the agent to design an A/B test for a specific page change, providing your current conversion rate, monthly traffic, and the smallest improvement worth detecting.

Frequently Asked Questions about suede-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, 95% significance, and 80% power. The Skill provides quick-reference tables: for example, a 3% baseline detecting a 20% lift needs about 31,000 visitors per variant, or use calculators like Evan Miller's or Optimizely's.

How long should I run an A/B test before calling a winner?

Run until three predeclared conditions are met: target sample per variant, minimum duration, and the decision rule. Minimum duration is at least one full week for day-of-week variation, two business cycles for B2B, and through paydays for e-commerce, regardless of early significance.

Why is my A/B test result at 95% confidence still unreliable?

Checking results before reaching the predeclared sample size inflates false positive rates, a problem known as peeking. Early trends reverse routinely due to regression to the mean and audience mix shifts, so significance at partial sample is preliminary, not a winner.

Should I run a multivariate test or sequential A/B tests?

Multivariate tests multiply combinations (2 headlines x 2 images x 2 CTAs = 8 variants) and require very high traffic. If your traffic cannot supply adequate sample per combination, run sequential A/B tests on individual elements instead.

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

Define three tiers: one primary metric tied to the hypothesis that decides the test, secondary metrics that explain why the change worked, and guardrail metrics that must not get worse, such as support tickets or refund rate.

When should I not use this A/B testing skill?

Do not use it for analytics instrumentation (use suede-analytics), post-click conversion diagnosis (use suede-site-alchemy), or writing variant copy (use suede-copy). It also cannot help when traffic is too low to power any realistic test.