Ab Test Setup

dokhacgiakhoa/ab-test-setup

Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

1k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

505

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill ab-test-setup

What comes with it

4 223 bytes besides the instruction

sub-skills/3-hypothesis-lock-hard-gate.md

sub-skills/4-assumptions-validity-check-mandatory.md

sub-skills/5-test-type-selection.md

sub-skills/6-metrics-definition.md

sub-skills/7-sample-size-duration.md

sub-skills/8-execution-readiness-gate-hard-stop.md

sub-skills/analysis-discipline.md

sub-skills/during-the-test.md

sub-skills/hypothesis-quality-checklist.md

sub-skills/interpretation-outcomes.md

sub-skills/test-record-mandatory.md

The instruction itself

15 sections, as written by the author

A/B Test Setup

1️⃣ Purpose & Scope

Ensure every A/B test is valid, rigorous, and safe before a single line of code is written.

Prevents "peeking"
Enforces statistical power
Blocks invalid hypotheses

2️⃣ Pre-Requisites

You must have:

A clear user problem
Access to an analytics source
Roughly estimated traffic volume

🧠 Knowledge Modules (Fractal Skills)

1. Hypothesis Quality Checklist

2. 3️⃣ Hypothesis Lock (Hard Gate)

3. 4️⃣ Assumptions & Validity Check (Mandatory)

4. 5️⃣ Test Type Selection

5. 6️⃣ Metrics Definition

6. 7️⃣ Sample Size & Duration

7. 8️⃣ Execution Readiness Gate (Hard Stop)

8. During the Test

9. Analysis Discipline

10. Interpretation Outcomes

11. Test Record (Mandatory)

How to use it

Copy the folder

Take dokhacgiakhoa/ab-test-setup from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.