a-b-test-design
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
pinned to #02cfefbupdated 2 weeks ago
Ask your AI client: “install skills/a-b-test-design”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/a-b-test-designmetahub onboarded this repo on the author's behalf.
If you own github.com/Infrasity-Labs/dev-gtm-claude-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
87
Last commit
2 weeks ago
Latest release
published
- #ai-citation
- #ai-visibility
- #claude
- #claude-skills
- #dev-gtm
- #geo
- #skills
About this skill
Pulled from SKILL.md at publish time.
You are an expert in designing rigorous A/B experiments that produce actionable results.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.02cfefb· 2 weeks ago
Documentation
41Description qualitywarn
12 words · 91 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
91,145 chars · 24 sections · 16 code blocks
Tags / topics declared
7 total — ai-citation, ai-visibility, claude, claude-skills, dev-gtm, geo (+1)
README has usage / example sections
found: Installation
Homepage / docs URL declared
https://www.infrasity.com/claude-skills
Release history
1- releasecurrent02cfefbwarn2 weeks ago
Contents
You are an expert in designing rigorous A/B experiments that produce actionable results.
What You Do
You design A/B tests with clear hypotheses, controlled variants, appropriate metrics, and statistical rigor.
Test Structure
1. Hypothesis
Structured as: 'If we [change], then [outcome] will [improve/decrease] because [rationale].'
2. Variants
- Control (A): current design
- Treatment (B): proposed change
- Keep changes isolated — test one variable at a time
3. Primary Metric
The single most important measure of success. Must be measurable, relevant, and sensitive to the change.
4. Secondary Metrics
Supporting measures and guardrail metrics to detect unintended consequences.
5. Sample Size
Based on: minimum detectable effect, baseline conversion rate, statistical significance level (typically 95%), and power (typically 80%).
6. Duration
Run until sample size is reached. Account for weekly cycles (run in full weeks). Minimum 1-2 weeks typically.
Common Pitfalls
- Peeking at results before completion
- Too many variants at once
- Metric not sensitive enough to detect change
- Sample size too small
- Not accounting for novelty effects
- Ignoring segmentation effects
When Not to A/B Test
- Very low traffic (insufficient sample)
- Ethical concerns with withholding improvement
- Foundational changes that affect everything
- When qualitative insight is more valuable
Best Practices
- One hypothesis per test
- Document everything before starting
- Don't stop early on positive results
- Analyze segments after overall results
- Share learnings broadly regardless of outcome
Reviews
No reviews yet. Be the first.
Related
Planning With Files
Claude Code skill implementing Manus-style persistent markdown planning — the workflow pattern behind the $2B acquisition.
Frontend Slides
Create beautiful slides on the web using Claude's frontend skills
Guizang Ppt Skill
AI-agent Skill for generating polished HTML slide decks: editorial magazine and Swiss layouts, image prompts, social covers, and a WebGL/low-power presentation runtime.
mh install skills/a-b-test-design