ab-test-analysis

Analyze A/B test results for statistical significance and sample size validation.

8|1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/officebeats/beats-pm-kit --skill ab-test-analysis-officebeats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test-analysis
Source: https://github.com/officebeats/beats-pm-kit/tree/main/.agent/skills/ab-test-analysis
Command: npx skills add https://github.com/officebeats/beats-pm-kit --skill ab-test-analysis-officebeats

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides rigorous statistical analysis of A/B test results, helping you make data-driven decisions about product changes and feature rollouts.

Core Features & Use Cases

  • Statistical Significance: Calculates p-values and confidence intervals to determine if observed differences are statistically significant.
  • Sample Size & Power Validation: Checks if the test collected enough data to reliably detect the expected effect size.
  • Guardrail Metric Monitoring: Evaluates the impact on secondary metrics to prevent unintended negative consequences.
  • Decision Framework: Provides clear recommendations (Ship, Extend, Stop, Investigate) based on the analysis.
  • Use Case: After running an experiment on a new checkout flow, use this Skill to determine if the conversion rate lift is statistically significant and if it negatively impacted other key metrics before deciding to launch it.

Quick Start

Analyze the A/B test results in the attached file 'experiment_results.csv' for the new user onboarding flow.

Frequently Asked Questions about ab-test-analysis

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?

To determine statistical significance in A/B testing, calculate p-values and confidence intervals to verify if observed metric differences are reliable. This analysis evaluates whether the conversion rate lift is genuine or due to random chance before making product decisions.

What's the best way to evaluate guardrail metrics during experiment analysis?

Evaluating guardrail metrics during experiment analysis involves checking secondary metrics for unintended negative consequences. This process ensures a new feature rollout improves the target conversion rate without degrading existing product metrics.

How do I validate sample size and power for an A/B test?

Validating sample size and power for an A/B test confirms whether the experiment collected enough data to reliably detect the expected effect size. This power analysis prevents false positives and ensures accurate hypothesis validation.

When should I ship, extend, or stop an A/B test?

You should ship, extend, or stop an A/B test based on a decision framework evaluating statistical significance and observed lift. Ship validated hypotheses, extend tests lacking sample size, and stop experiments showing negative guardrail metric impacts.

Can I analyze split test data from a CSV file for product decisions?

You can analyze split test data from a CSV file containing experiment results to guide product decisions. The analysis processes the attached data to calculate statistical significance and validate the hypothesis for feature rollouts.