ab-testing

Design, monitor, and analyze A/B tests across web, email, and in-app interfaces.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/Ryko1141/Hedge-Edge-agentic --skill ab-testing-ryko1141
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ab-testing
Source: https://github.com/Ryko1141/Hedge-Edge-agentic/tree/main/Analytics%20Agent/.agents/skills/ab-testing
Command: npx skills add https://github.com/Ryko1141/Hedge-Edge-agentic --skill ab-testing-ryko1141

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill replaces guesswork with data-driven decision-making by enabling the design, execution, and analysis of controlled experiments to optimize business metrics.

Core Features & Use Cases

  • Experiment Design: Formulate hypotheses, define primary and guardrail metrics, and calculate sample sizes.
  • Implementation Guidance: Provides instructions for A/B testing on landing pages, emails, and in-app features.
  • Monitoring & Analysis: Offers step-by-step processes for tracking experiments, performing statistical tests, and interpreting results.
  • Use Case: Optimize the landing page conversion rate by testing different headlines and calls-to-action to increase sign-ups.

Quick Start

Design an A/B test for the landing page headline with a hypothesis that changing it will increase signup rate.

Frequently Asked Questions about ab-testing

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

FAQPage Schema
How do I calculate sample size for an A/B test to optimize conversion rates?

Calculate A/B test sample size by formulating a hypothesis and defining primary and guardrail metrics to ensure statistical rigor. This process prevents common pitfalls like peeking and p-hacking while optimizing business funnels.

What is the best way to design controlled experiments for product features?

Design controlled experiments by defining metrics, calculating sample sizes, and establishing randomization protocols. This ensures statistical rigor when testing product features across web, email, and in-app interfaces to drive growth.

Can I use A/B testing for both email campaigns and in-app interfaces?

Yes, A/B testing supports implementation across web, email, and in-app interfaces. It provides step-by-step monitoring and statistical analysis to interpret results for various digital marketing and product experiments.

How do I stop p-hacking and peeking when monitoring statistical tests?

Prevent p-hacking and peeking during statistical tests by following rigorous monitoring protocols and predefined sample sizes. This ensures valid conversion rate optimization results and prevents interpreting early data incorrectly.

Why does my A/B test result show misleading statistical significance?

Misleading A/B test statistical significance often results from peeking at early data or p-hacking without proper sample size calculation. Ensuring randomization and following strict monitoring protocols prevents these common experimentation pitfalls.

Do I need to define guardrail metrics before running growth marketing experiments?

Yes, defining guardrail metrics during experiment design is essential before running growth marketing tests. Establishing these alongside primary metrics and hypotheses ensures statistical rigor and protects business funnels from negative impacts.