experiment-design SKILL.md skillA
experiment-design from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/experiment-design@git:20261019.be4abccPins git:20261019.be4abcc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/pm/experiment-design/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261019.be4abcc, committed Oct 19, 2026
- First version recorded
- Mar 3, 2026
- Size
- 4,591 bytes
- Repository stars
- 24
- License
- MIT
Design product experiments to test hypotheses. Use when the user says "run an experiment", "A/B test this", "build-measure-learn", "validate this assumption", "test this hypothesis", "we don't know if this will work", "minimum viable test", "lean experiment", or wants to reduce risk before fully building a feature - even if they don't explicitly say "experiment". For sample sizes, power calculations and significance testing, use ab-test-design instead.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Overview Based on **The Lean Startup** by Eric Ries. The core insight: startups (and product teams) don't fail from lack of execution - they fail from executing on the wrong plan. The build-measure-learn loop is how you find the right plan faster. Every feature is a hypothesis. Every release is an experiment. Validated learning - not shipped features - is the unit of progress. ## Workflow ### Step 1: State the hypothesis Format: "We believe [action/feature] will cause [user behavior change], resulting in [metric change], because [assumption]." Example: "We believe adding a progress bar to onboarding will cause more users to complete setup, resulting in a 15% increase in activation rate, because users abandon when they can't see how much is left." The "because" is critical - it forces you to name the assumption you're testing. ### Step 2: Identify the riskiest assumption Most hypotheses have multiple assumptions embedded. Find the one that, if wrong, makes the whole hypothesis collapse. List assumptions - rank by risk - test the riskiest one first. ### Step 3: Design the minimum viable test What's the cheapest, fastest way to test the riskiest assumption? …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/experiment-design@sha256:4140c6c30f0248ccThe line at the top of this page pins the label git:20261019.be4abcc, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_oddlvrkroost4o6t)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Mar 3, 2026 and Oct 19, 2026, about one every 230 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.be4abcc latest | 2026-10-19 | be4abcc | 4,591 B | A | view · diff |
| git:20260303.e2bea1e | 2026-03-03 | e2bea1e | 4,498 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4591 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qa-aman/claude-skills · 24 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oddlvrkroost4o6t GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/experiment-design GET https://markdownregistry.com/api/v1/blob/4140c6c30f0248ccf93e2752d7eede35b010cc3b603d31a1797bbdc7244e14f8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from qa-aman/claude-skills
Every file in qa-aman/claude-skills