ab-test-analyzer

Analyze A/B test results and recommend ship, extend, or kill decisions.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/ekatasingh1107/b2b-gtm-skills --skill ab-test-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test-analyzer
Source: https://github.com/ekatasingh1107/b2b-gtm-skills/tree/main/skills/capabilities/ab-test-analyzer
Command: npx skills add https://github.com/ekatasingh1107/b2b-gtm-skills --skill ab-test-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes guesswork from A/B testing by performing rigorous statistical analysis on variant results and producing a clear recommendation to ship, extend, or kill a test based on significance, power, and validity checks.

Core Features & Use Cases

  • Comprehensive statistics: Calculates per-variant conversion rates, confidence intervals, pooled z-scores, p-values, absolute and relative lift, and statistical power.
  • Validity and safety checks: Detects sample ratio mismatch, enforces minimum sample thresholds, flags novelty effects, and applies multiple comparison corrections when needed.
  • Decision & impact analysis: Estimates required sample sizes and days remaining given traffic, computes revenue impact when revenue per conversion is provided, and issues actionable SHIP/EXTEND/KILL guidance with next steps.
  • Use case: Decide whether to implement a new CTA, continue an underpowered experiment, or stop a losing variant while estimating business impact.

Quick Start

Analyze this A/B test and recommend SHIP, EXTEND, or KILL: Control 2500 visitors, 100 conversions; Variant B 2500 visitors, 150 conversions; use 95% confidence.

Frequently Asked Questions about ab-test-analyzer

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

FAQPage Schema
How do I determine if my A/B test results are statistically significant?

A/B test significance is determined by computing p-values, z-scores, and confidence intervals from per-variant visitors and conversions. This analysis compares a control against variants to validate if observed conversion rate differences are statistically robust.

When should I stop, extend, or ship my conversion rate experiment?

Ship, extend, or kill an A/B test based on statistical power, significance, and sample size thresholds. Evaluating these metrics ensures the experiment has sufficient traffic to detect true lift and prevents premature decisions on underpowered variants.

How do I calculate the required sample size for an A/B test?

Calculate required A/B test sample size by inputting daily traffic, confidence level, and test duration. This estimates remaining visitors needed per variant to achieve adequate statistical power and ensures the conversion experiment runs long enough to detect true lift.

Can I estimate revenue impact from my A/B test conversion data?

Estimate revenue impact from A/B test conversion data by providing revenue per conversion alongside per-variant visitors and conversions. This calculates absolute and relative conversion lift to project the financial outcome of shipping a winning variant.

What validity checks are needed to detect sample ratio mismatch in A/B testing?

A/B testing validity checks for sample ratio mismatch compare actual visitor distribution across variants against expected traffic splits. Detecting this mismatch, enforcing minimum sample thresholds, and flagging novelty effects ensures statistical significance calculations remain unbiased.

Do I need multiple comparison corrections for A/B tests with multiple variants?

Multiple comparison corrections are needed for A/B tests with multiple variants to prevent false positives. Applying these corrections adjusts p-values and confidence intervals when comparing one control against several variants, maintaining statistical significance integrity.