hypothesis-formulation
Structured scientific hypothesis generation from observations. Use when formulating testable hypotheses, competing explanations, or experimental predictions.
pinned to #ea77ec1updated 2 weeks ago
Ask your AI client: “install skills/hypothesis-formulation”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/hypothesis-formulationmetahub onboarded this repo on the author's behalf.
If you own github.com/aiming-lab/AutoResearchClaw 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
13,760
Last commit
2 weeks ago
Latest release
published
- #autonomous-research
- #citation-verification
- #llm-agents
- #metaclaw
- #multi-agent-debate
- #openclaw
- #paper-generation
- #scientific-discovery
- #self-evolving
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.ea77ec1· 2 weeks ago
Kind-specific
31Skill: SKILL.md present
found at .claude/skills/hypothesis-formulation/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
282 words · 2,027 chars · 6 sections
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrentea77ec1warn2 weeks ago
Contents
Hypothesis Formulation Best Practice
Structured Hypothesis Development
- Start with a clear observation or pattern that requires explanation
- Review existing literature for known mechanisms and prior explanations
- Identify what is already established vs. what remains uncertain
- Formulate the hypothesis as a specific, testable statement
- Ensure the hypothesis is falsifiable — define what outcome would refute it
Hypothesis Format
- Null hypothesis (H0): There is no effect or no difference
- Alternative hypothesis (H1): There is a specific, directional effect
- State both explicitly; design experiments to reject H0
- Use "If... then... because..." structure for mechanistic hypotheses:
- If [independent variable is manipulated], then [predicted outcome], because [proposed mechanism]
Generating Competing Hypotheses
- Propose at least 2-3 plausible explanations for the same observation
- For each, identify unique predictions that distinguish it from alternatives
- Rank hypotheses by parsimony, consistency with prior evidence, and testability
- Design experiments that can discriminate between competing hypotheses
- Consider confounding variables that could produce the same observation
Testable Predictions
- Derive specific, measurable predictions from each hypothesis
- Define expected effect direction AND approximate magnitude
- Specify what experimental conditions would confirm vs. refute the prediction
- Identify potential confounds and plan controls to address them
- Ensure predictions are achievable with available methods and resources
Aligning with Experimental Design
- Map each hypothesis to a concrete experimental condition or comparison
- Ensure sample size is adequate to detect the predicted effect (power analysis)
- Pre-register hypotheses and analysis plans when possible
- Distinguish confirmatory (hypothesis-testing) from exploratory analyses
- Plan for both positive and null results — what will you conclude in each case?
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.
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
mh install skills/hypothesis-formulation