experiment-design
Skill0 starsChanged 2 months agoMITView on GitHub
Design a marketing test that can actually answer the question, and read the result honestly. Covers sample size, run length, stopping rules and the difference between a real effect and noise. Use before launching a test, or when asked whether a result is real.
32 other projects use a version of this.
Adopted by
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- Walsworth-Group/physkittheir own version, first seen Nov 8, 2026
- flonat/flonat-researchtheir own version, first seen Nov 3, 2026
- automatewithuday/GTM-Skillstheir own version, first seen Nov 2, 2026
- Chykalophia/cro-research-reportingtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use list-quality-scorecard and positive-reply-scoring.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
creatop-gtmSkilllist-quality-scorecard
Check a lead list before it goes into a sequence. Gives a deliverability readout (firm) and a targeting readout (advisory). Surfaces issues, never blocks. Use before enrolling any list.
Also in 3 projects that use this
creatop-gtmSkillpositive-reply-scoring
Classify replies and compute positive reply rate, the metric that predicts revenue. Use to tell whether a campaign is actually working, not just getting replies.
Also in 3 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- microsoft/hve-core★ 1.6ksame name
- growthenginenowoslawski/coldoutboundskills★ 759same name
- lingzhi227/agent-research-skills★ 350same name
- Yeachan-Heo/My-Jogyo★ 241same name
- flonat/flonat-research★ 150same name
- voidful/academic-skills★ 126same name
- itseffi/agentic-os★ 114same name
- pratikshadake/claude-product-management-skills★ 33same name
- Adelie-Squad/solosquad★ 25same name
- TashanGKD/tashan-research-skills★ 19same name
22 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- activationSkill
- capacity-economicsSkill
- channel-fitSkill
- data-trustSkill
- form-frictionSkill
- funnel-diagnosisSkill
- pricing-decisionsSkill
- retention-diagnosisSkill
- unit-economicsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Ask for the minimum effect worth acting on, not the effect you hope for.
- Distinctive: line 35
Long enough to cover the conversion lag: If people convert 8 days after first touch, a 7-day test measures the wrong thing
- Distinctive: line 46
If you must monitor, monitor for harm — a variant losing badly enough to be worth killing — not for wins.
“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Experiment design
Most marketing tests cannot detect the effect they are looking for. They run, produce a number, and the number gets believed.
Before the test: can it possibly answer?
Ask for the minimum effect worth acting on, not the effect you hope for. If a 5% lift would not change any decision, do not power the test for 5%.
Rough sample size for a conversion test, per variant:
n ≈ 16 × p × (1 − p) / (minimum detectable effect)²where p is the current conversion rate as a decimal and the effect is absolute.
Going from 2% to 2.4% is an absolute effect of 0.004, and needs roughly 300,000
per variant. Most teams discover this and quietly test for 50% lifts instead.
Report the number honestly. If the traffic does not exist, say the test cannot be run and suggest a different question: a bigger change, a higher-traffic surface, or a qualitative method.
Run length
- Full weeks only. Weekday and weekend behaviour differ in nearly every consumer category. A test stopped on a Wednesday is a test of Wednesdays
- Minimum two weeks for anything with a purchase cycle
- Long enough to cover the conversion lag. If people convert 8 days after first touch, a 7-day test measures the wrong thing
Stopping rules, set in advance
Peeking is the most common way marketing tests lie. Checking daily and stopping when it looks significant produces false positives at several times the stated rate, because you get many chances to cross the line by chance.
Set the sample size and the end date before launch. Then look at the end.
If you must monitor, monitor for harm — a variant losing badly enough to be worth killing — not for wins.
Reading the result
- Under ~30 conversions per variant, do not call it. Say the test is inconclusive
- A non-significant result is not "no difference." It means the test could not detect one. Report the range the true effect could plausibly sit in
- Check the segments only to generate hypotheses, never to rescue a null. Slicing until something is significant will always eventually succeed
- Confirm the split was actually even and that both variants were served through the same period
What not to test
Small copy changes on low-traffic pages. The effect is too small and the traffic too thin, ever. Change something big enough to matter, or research it qualitatively instead.
Output
For a planned test: required sample per variant, expected run length at current traffic, the pre-registered stopping rule, and a plain statement of whether the test is feasible. For a completed test: the verdict, the plausible effect range, and whether the design permits the conclusion being drawn.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

