pm-abtest

Analyze A/B test results into ship, extend, or stop decisions.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-abtest-wcof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-abtest
Source: https://github.com/Wcof/PMSkill/tree/main/skills/delivery/pm-abtest
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-abtest-wcof

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams make reliable A/B test decisions instead of guessing from raw conversion numbers. It validates whether an experiment was run correctly, checks if the result is statistically and practically meaningful, and prevents bad launches when SRM, weak sample size, or guardrail regressions make the evidence unreliable.

Core Features & Use Cases

  • Experiment validity checks: Verifies sample size, runtime coverage, randomization quality, SRM, and novelty effects before trusting any result.
  • Decision-ready statistical analysis: Calculates conversion rates, lift, p-value, and 95% confidence intervals, then compares the outcome against PMContext success thresholds.
  • Guardrail-aware launch recommendations: Reviews downside metrics such as revenue, retention, or latency and downgrades decisions when the primary metric improves but important safeguards worsen.
  • Use cases: Analyze onboarding experiments, pricing tests, feature rollout experiments, activation funnel changes, or any split test where product managers need a clear ship, extend, or stop recommendation tied back to documented product metrics.

Quick Start

Ask the pm-abtest skill to analyze your A/B test by providing control and variant sample sizes, conversions, runtime, and the relevant PMContext success threshold and guardrail metrics.

Frequently Asked Questions about pm-abtest

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

FAQPage Schema
How do I analyze A/B test results to make a ship or stop decision?

A/B test analysis validates experiment validity, checks SRM and sample size, calculates statistical significance and lift, then outputs a ship, extend, or stop decision based on guardrail regressions.

What is SRM detection and why does it matter for split testing?

SRM detection checks for sample ratio mismatch in split testing to verify randomization quality. If SRM is present, the experiment evidence is unreliable and launch decisions must be downgraded to prevent bad releases.

How do you calculate lift analysis and confidence intervals for conversion experiments?

Lift analysis calculates conversion rate differences between variants, while 95% confidence intervals estimate the precision of that lift. Both are compared against success thresholds to validate practical significance.

When should I downgrade a launch decision due to guardrail metrics?

You should downgrade a launch decision when the primary metric improves but guardrail metrics like revenue, retention, or latency regress, indicating the variant harms important product safeguards despite the conversion gain.

What sample size and runtime data do I need for statistical significance testing?

Statistical significance testing requires control and variant sample sizes, conversions, and runtime coverage to verify adequate exposure and detect novelty effects before trusting the experiment outcome.

Does A/B testing work for pricing and onboarding experiments?

A/B testing applies to pricing, onboarding, activation, and feature rollout experiments by validating conversion changes against documented product metrics and guardrails to ensure reliable launch decisions.