hypothesis-design
Skill17 starsChanged 3 months agoMITView on GitHub
Turns theory into operationalized, falsifiable hypotheses — statement, direction, estimand, smallest effect of substantive interest, X/Y operationalization, falsification pattern, and what a null would mean — with exactly one marked primary. Use before any data collection, analysis, or preregistration, or whenever the user drafts or revises hypotheses.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- itseffi/agentic-ostheir own version, first seen Jan 23, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- itseffi/agentic-os★ 114same name
- Adelie-Squad/solosquad★ 25same name
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 repository38 other files it gives its agents.
- abstract-shotgunSkill
- analyzeSkill
- archiveSkill
- carefulSkill
- coauthor-reviewSkill
- codebookSkill
- cover-letterSkill
- data-acquireSkill
- data-cleanSkill
- design-researchSkill
- draft-sectionSkill
- freezeSkill
- guardSkill
- idea-shotgunSkill
- identification-reviewSkill
- journal-fitSkill
- learnSkill
- lit-mapSkill
- llm-checklistSkill
- mstack-initSkill
- mstack-upgradeSkill
- paper-statusSkill
- pdf-ingestSkill
- power-analysisSkill
- preregisterSkill
- r-and-rSkill
- referee-mockSkill
- research-questionSkill
- results-auditSkill
- retroSkill
- robustnessSkill
- scope-challengeSkill
- submission-packSkill
- survey-buildSkill
- theory-buildSkill
- title-shotgunSkill
- unfreezeSkill
- vizSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
After /mstack:theory-build.
- Distinctive: line 45
Hypotheses bigger than the data: If the data cannot show the falsifying pattern, get different data or rewrite the hypothesis.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/mstack:hypothesis-design
Stage: map · Voice: methodologist
After /mstack:theory-build; before fielding, analysis, or /mstack:preregister (which quotes these hypotheses verbatim). The bar is the one the preregistration will be held to: two researchers given the hypothesis and the data should test the same thing (see ${CLAUDE_PLUGIN_ROOT}/references/preregistration-guide.md, section "What must be specific").
Procedure
- Load
.mstack/theory.md(mechanism, rivals, estimand) and.mstack/lit-map.md(comparable effect sizes). Specify eight fields per hypothesis (H1, H2, …):
Field Example Statement "Higher exposure to import competition increases vote share for protectionist parties." Direction Positive (β > 0). Estimand "The ATT of a one-SD increase in exposure on protectionist vote share (percentage points), among NUTS-2 regions in 12 EU states, 2000–2019" (Lundberg, Johnson & Stewart 2021). Magnitude expectation "A 1-SD increase in exposure raises vote share by 1–3 percentage points; comparable estimates in Colantone & Stanig (2018) are …" Smallest effect of substantive interest "1 percentage point; smaller effects would not change the policy or theoretical claim." Operationalization of X "ADH-style instrument as in Autor et al. 2013, country-region-year level." Operationalization of Y "Percent of constituency vote for parties CMP classifies as protectionist." Falsification pattern and null reading "A 95% CI excluding zero supports H1; a CI entirely within (−1, 1) is evidence against a substantively meaningful effect; a CI straddling both is inconclusive. β < 0 falsifies the mechanism direction." - Falsifiability check. Could a result actually falsify it, or is the prediction "some relationship"? Is the falsifying pattern observable with the planned data at the planned N (check against
.mstack/power-analysis.mdonce it exists)? If not, the hypothesis is untestable in this design. - Exactly one primary. The headline rests on it; secondaries explore mechanism, heterogeneity, or scope. Every secondary carries the same eight fields.
- Moderation and mechanism. A theorized moderator is its own hypothesis stating the marginal effect of X at each level of the moderator, not the interaction coefficient ("H2: the effect of X on Y is at least twice as large where S is high as where S is low"); a theorized mediator is a hypothesis about the path, with the caveat that mediation analysis needs its own identifying assumptions. Heterogeneity not specified here is exploratory in the prereg. Take the rows of the rival-mechanisms table in
theory.mdand write, for each, the hypothesis that would distinguish your mechanism from that rival. - Save to
.mstack/hypotheses.md; the prereg pulls from it.
Outputs
.mstack/hypotheses.md— every hypothesis with all eight fields, the primary marked, and the rival-discriminating hypotheses grouped at the end.- Summary block: primary hypothesis, its estimand, its SESOI, and its falsification pattern.
Anti-patterns
- One-sided ambiguity. "X is related to Y" is not a hypothesis.
- No estimand. "The coefficient on X" is not a quantity about the world.
- Hypotheses bigger than the data. If the data cannot show the falsifying pattern, get different data or rewrite the hypothesis.
- Five primaries. Exactly one.
- A null with no interpretation. Decide now what a null result will be taken to mean.
Next
/mstack:identification-review, then /mstack:preregister.
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.

