experiment

Design and analyze A/B tests to determine treatment effects on defined metrics.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill experiment-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/experiment
Command: npx skills add https://github.com/arbazkhan971/godmode --skill experiment-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design, run, and interpret A/B experiments with statistical rigor so they can validate product changes, avoid false positives from peeking, and protect revenue and performance guardrails.

Core Features & Use Cases

  • Detects existing experimentation SDKs and configs (Statsig, Optimizely, GrowthBook) and inspects assignment logic and exposure logging.
  • Performs sample size and power calculations, SRM checks, deterministic assignment, frequentist and Bayesian decision rules, guardrail monitoring, ramp schedules, and cleanup workflows.
  • Use case: plan and analyze a signup funnel experiment, compute required traffic for a specified MDE, enforce latency and error-rate guardrails, and produce a clear ship/kill verdict.

Quick Start

Run an A/B test to improve signup conversion by 10% and compute required sample size, deterministic assignment, and decision rules with 80% power.

Frequently Asked Questions about experiment

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

FAQPage Schema
How do I calculate required sample size and power for an A/B test?

To calculate A/B test sample size and power, you define a minimum detectable effect (MDE) and apply statistical power analysis. This Skill computes the required traffic for your specified MDE and decision rules to ensure reliable experiment results.

Does this work with existing experimentation SDKs like Statsig, Optimizely, and GrowthBook?

Yes, it works with Statsig, Optimizely, and GrowthBook. The Skill detects existing experimentation SDKs and configurations, inspecting assignment logic and exposure logging to validate your web and mobile platform rollouts.

How do I avoid false positives from peeking during A/B testing?

To avoid false positives from peeking during A/B testing, apply frequentist and Bayesian decision rules with strict guardrail monitoring. This Skill enforces statistical rigor and performs SRM checks to protect your revenue and performance metrics.

What is SRM checking and how does it protect my experiment results?

SRM checking, or Sample Ratio Mismatch checking, validates that traffic assignment matches expected ratios across experiment variants. It acts as a guardrail to detect logging errors or assignment bugs that could invalidate your A/B test treatment effects.

Can this Skill help plan ramp schedules and cleanup workflows for feature flags?

Yes, it supports feature flag ramp schedules and cleanup workflows. The Skill manages the entire experimental lifecycle, from deterministic assignment and guardrail monitoring to producing clear ship or kill verdicts for your product rollouts.

When should I use frequentist versus Bayesian decision rules for my experiments?

Use frequentist or Bayesian decision rules based on your experimental needs for determining treatment effects. This Skill applies both methodologies to analyze your defined metrics, enforcing latency and error-rate guardrails to output clear ship/kill decisions.