ab-test-analysis

Analyzes A/B test results with statistical significance, sample size checks, and ship-or-stop recommendations.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill ab-test-analysis-choi-keith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test-analysis
Source: https://github.com/Choi-Keith/skill-arsenal-ultra/tree/main/plugins/pm-skills/pm-data-analytics/skills/ab-test-analysis
Command: npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill ab-test-analysis-choi-keith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often misread experiment data—calling winners too early, ignoring underpowered tests, or missing guardrail regressions. This Skill applies rigorous statistical methods to A/B test results and converts the findings into a clear launch, extend, or stop decision. ## Core Features & Use Cases - Statistical Significance Testing: Computes conversion rates, relative lift, p-values (z-test or chi-square), and 95% confidence intervals for control vs. variant groups. - Test Validity Checks: Verifies sample size adequacy (power analysis), test duration across business cycles, randomization integrity (SRM detection), and novelty effects. - Guardrail Metric Review: Flags cases where the primary metric wins but revenue, engagement, or performance guardrails degrade. - Decision Framework: Maps result patterns to concrete recommendations—ship, investigate, extend, or stop—with a structured markdown summary. - Use Case: You ran a two-week checkout button experiment with 50,000 users per arm. Provide the conversion counts, and the Skill validates power, computes significance, checks guardrails, and tells you whether to roll out the variant. ## Quick Start Analyze this A/B test result: control had 12,000 visitors with 480 conversions, variant had 12,000 visitors with 540 conversions, and tell me whether to ship it.

Frequently Asked Questions about ab-test-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I know if my A/B test result is statistically significant?

A result is statistically significant when the p-value from a two-tailed z-test or chi-square test is below 0.05, meaning the observed difference is unlikely due to chance. Also check the 95% confidence interval of the difference and confirm the lift is practically meaningful for the business.

How to calculate the sample size needed for an A/B test?

Use the formula n = (Z²α/2 × 2 × p × (1-p)) / MDE², where p is the baseline conversion rate and MDE is the minimum detectable effect. If the achieved sample gives less than 80% statistical power, the test is underpowered and results should be treated with caution.

What should I do when an A/B test is not significant but trending positive?

Extend the test to collect more data rather than shipping or abandoning it. A non-significant positive trend usually means the sample size is too small to detect the true effect, so more traffic or a larger expected effect is needed.

Can I trust an A/B test win if a guardrail metric got worse?

Not automatically. When the primary metric improves but guardrails like revenue, engagement, or page load time degrade, investigate the trade-off before launching. A primary-metric win with guardrail regression may not be a true victory.

Why does my A/B test show a sample ratio mismatch?

A sample ratio mismatch (SRM) indicates the actual traffic split deviates significantly from the intended allocation, signaling broken randomization or instrumentation bugs. Results from a test with SRM should not be trusted until the root cause is fixed.