ab-test-analysis

Analyze A/B test results for statistical significance and actionable recommendations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/KoryakinYurij/Self-Sustain-System --skill ab-test-analysis-koryakinyurij
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-test-analysis
Source: https://github.com/KoryakinYurij/Self-Sustain-System/tree/main/Skill%20Creation/research/pm-skills/pm-data-analytics/skills/ab-test-analysis
Command: npx skills add https://github.com/KoryakinYurij/Self-Sustain-System --skill ab-test-analysis-koryakinyurij

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product managers and data analysts make data-driven decisions by rigorously evaluating A/B test results, determining statistical significance, and providing clear recommendations.

Core Features & Use Cases

  • Statistical Significance Calculation: Determines if observed differences between variants are statistically significant.
  • Sample Size & Duration Validation: Checks if the test was adequately powered and ran for a sufficient period.
  • Guardrail Metric Monitoring: Assesses the impact on secondary metrics to prevent unintended negative consequences.
  • Recommendation Engine: Provides actionable advice (Ship, Extend, Stop, Investigate) based on the analysis.
  • Use Case: You've just completed an A/B test on a new feature and need to know if the observed lift in conversion rate is real and if any negative impacts on user engagement occurred, so you can decide whether to launch the feature.

Quick Start

Analyze the A/B test results for the user onboarding flow experiment using the provided data files.

Frequently Asked Questions about ab-test-analysis

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

FAQPage Schema
How do I analyze A/B test results to determine statistical significance?

To analyze A/B test results for statistical significance, the Skill calculates p-values, conversion rates, lift, and confidence intervals to determine if observed differences between variants are real or due to chance.

When do I need to validate sample size and duration for split testing?

You need to validate sample size and duration during split testing to ensure the experiment was adequately powered and ran long enough to detect true conversion rate differences, preventing premature rollouts.

How do I check if my A/B test caused negative impacts on secondary metrics?

You can check for negative impacts by monitoring guardrail metrics, which the Skill assesses alongside primary experiment outcomes to prevent unintended consequences on user engagement during a product feature rollout.

What is the best way to decide whether to ship, extend, or stop an experiment?

The best way to decide whether to ship, extend, or stop an experiment is by using a recommendation engine that evaluates statistical significance and guardrail metrics to provide actionable advice.

Can I use this Skill to interpret conversion rate lift for a product feature rollout?

Yes, you can use this Skill to interpret conversion rate lift for a product feature rollout by validating test setup, analyzing split test data, and confirming if the observed lift is statistically significant.

Why does my A/B test data show a conversion lift but I am unsure if I should launch?

Your A/B test data might show a conversion lift requiring further validation because the experiment lacks adequate sample size, sufficient duration, or shows negative impacts on guardrail metrics that prevent a safe launch.