Experiment designer

Use when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/experiment-designer-2.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/product-team/skills/experiment-designer#main ~/.claude/skills/experiment-designer-2

For one project only, change the path to .claude/skills/experiment-designer-2.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Experiment designer

Show the full text105 lines
namedescription
experiment-designerUse when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor.

Experiment Designer

Design, prioritize, and evaluate product experiments with clear hypotheses and defensible decisions.

When To Use

Use this skill for:

  • A/B and multivariate experiment planning
  • Hypothesis writing and success criteria definition
  • Sample size and minimum detectable effect planning
  • Experiment prioritization with ICE scoring
  • Reading statistical output for product decisions

Core Workflow

  1. Write hypothesis in If/Then/Because format
  • If we change [intervention]
  • Then [metric] will change by [expected direction/magnitude]
  • Because [behavioral mechanism]
  1. Define metrics before running test
  • Primary metric: single decision metric
  • Guardrail metrics: quality/risk protection
  • Secondary metrics: diagnostics only
  1. Estimate sample size
  • Baseline conversion or baseline mean
  • Minimum detectable effect (MDE)
  • Significance level (alpha) and power

Use:

python3 scripts/sample_size_calculator.py --baseline-rate 0.12 --mde 0.02 --mde-type absolute
  1. Prioritize experiments with ICE
  • Impact: potential upside
  • Confidence: evidence quality
  • Ease: cost/speed/complexity

ICE Score = (Impact * Confidence * Ease) / 10

  1. Launch with stopping rules
  • Decide fixed sample size or fixed duration in advance
  • Avoid repeated peeking without proper method
  • Monitor guardrails continuously
  1. Interpret results
  • Statistical significance is not business significance
  • Compare point estimate + confidence interval to decision threshold
  • Investigate novelty effects and segment heterogeneity

Hypothesis Quality Checklist

  • Contains explicit intervention and audience
  • Specifies measurable metric change
  • States plausible causal reason
  • Includes expected minimum effect
  • Defines failure condition

Common Experiment Pitfalls

  • Underpowered tests leading to false negatives
  • Running too many simultaneous changes without isolation
  • Changing targeting or implementation mid-test
  • Stopping early on random spikes
  • Ignoring sample ratio mismatch and instrumentation drift
  • Declaring success from p-value without effect-size context

Statistical Interpretation Guardrails

  • p-value < alpha indicates evidence against null, not guaranteed truth.
  • Confidence interval crossing zero/no-effect means uncertain directional claim.
  • Wide intervals imply low precision even when significant.
  • Use practical significance thresholds tied to business impact.

See:

  • references/experiment-playbook.md
  • references/statistics-reference.md

Tooling

scripts/sample_size_calculator.py

Computes required sample size (per variant and total) from:

  • baseline rate
  • MDE (absolute or relative)
  • significance level (alpha)
  • statistical power

Example:

python3 scripts/sample_size_calculator.py \
  --baseline-rate 0.10 \
  --mde 0.015 \
  --mde-type absolute \
  --alpha 0.05 \
  --power 0.8
1---
2name: experiment-designer
3description: Use when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor.
4---
5 
6# Experiment Designer
7 
8Design, prioritize, and evaluate product experiments with clear hypotheses and defensible decisions.
9 
10## When To Use
11 
12Use this skill for:
13- A/B and multivariate experiment planning
14- Hypothesis writing and success criteria definition
15- Sample size and minimum detectable effect planning
16- Experiment prioritization with ICE scoring
17- Reading statistical output for product decisions
18 
19## Core Workflow
20 
211. Write hypothesis in If/Then/Because format
22- If we change `[intervention]`
23- Then `[metric]` will change by `[expected direction/magnitude]`
24- Because `[behavioral mechanism]`
25 
262. Define metrics before running test
27- Primary metric: single decision metric
28- Guardrail metrics: quality/risk protection
29- Secondary metrics: diagnostics only
30 
313. Estimate sample size
32- Baseline conversion or baseline mean
33- Minimum detectable effect (MDE)
34- Significance level (alpha) and power
35 
36Use:
37```bash
38python3 scripts/sample_size_calculator.py --baseline-rate 0.12 --mde 0.02 --mde-type absolute
39```
40 
414. Prioritize experiments with ICE
42- Impact: potential upside
43- Confidence: evidence quality
44- Ease: cost/speed/complexity
45 
46ICE Score = (Impact * Confidence * Ease) / 10
47 
485. Launch with stopping rules
49- Decide fixed sample size or fixed duration in advance
50- Avoid repeated peeking without proper method
51- Monitor guardrails continuously
52 
536. Interpret results
54- Statistical significance is not business significance
55- Compare point estimate + confidence interval to decision threshold
56- Investigate novelty effects and segment heterogeneity
57 
58## Hypothesis Quality Checklist
59 
60- [ ] Contains explicit intervention and audience
61- [ ] Specifies measurable metric change
62- [ ] States plausible causal reason
63- [ ] Includes expected minimum effect
64- [ ] Defines failure condition
65 
66## Common Experiment Pitfalls
67 
68- Underpowered tests leading to false negatives
69- Running too many simultaneous changes without isolation
70- Changing targeting or implementation mid-test
71- Stopping early on random spikes
72- Ignoring sample ratio mismatch and instrumentation drift
73- Declaring success from p-value without effect-size context
74 
75## Statistical Interpretation Guardrails
76 
77- p-value < alpha indicates evidence against null, not guaranteed truth.
78- Confidence interval crossing zero/no-effect means uncertain directional claim.
79- Wide intervals imply low precision even when significant.
80- Use practical significance thresholds tied to business impact.
81 
82See:
83- `references/experiment-playbook.md`
84- `references/statistics-reference.md`
85 
86## Tooling
87 
88### `scripts/sample_size_calculator.py`
89 
90Computes required sample size (per variant and total) from:
91- baseline rate
92- MDE (absolute or relative)
93- significance level (alpha)
94- statistical power
95 
96Example:
97```bash
98python3 scripts/sample_size_calculator.py \
99 --baseline-rate 0.10 \
100 --mde 0.015 \
101 --mde-type absolute \
102 --alpha 0.05 \
103 --power 0.8
104```
105 

Discussion

Alternatives

Also in Roadmap & prioritiesSee all 277 in Product →