hypothesis-generation
Structured hypothesis formulation: turn observations into testable hypotheses with predictions, propose mechanisms, design experiments. Follows the scientific method. Use scientific-brainstorming for open ideation; hypogenic for automated LLM hypothesis testing on datasets.
Install / Use
npx skills add jaechang-hits/SciAgent-Skills --skill hypothesis-generationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of hypothesis-generation
hypothesis-generation scores 86/100 on our quality scale, 1746th of 2,866 Automation skills we index.
Its SKILL.md is 10 KB long, well organised into 13 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
It has 367 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 37 days ago, so hypothesis-generation is actively maintained.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
hypothesis-generation compared with similar skills
All 4 of these similar skills score higher than hypothesis-generation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| hypothesis-generation (this skill)by jaechang-hits | 86 | 367 | 37d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 90.8k | 19d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 85.7k | today | MCP Server |
| rufloby ruvnet | 100 | 73.9k | today | MCP Server |
| algorithmic-artby anthropics | 100 | 177.9k | 12d ago | SKILL.md |
Frequently asked questions
- How do I install hypothesis-generation?
- Run
npx skills add jaechang-hits/SciAgent-Skills --skill hypothesis-generation. The install tabs above show the steps for each supported agent. - Which AI agents does hypothesis-generation work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is hypothesis-generation safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is hypothesis-generation still maintained?
- The repository was last updated 37 days ago, so hypothesis-generation is actively maintained.
Skill content
View source on GitHubname: hypothesis-generation description: "Structured hypothesis formulation: turn observations into testable hypotheses with predictions, propose mechanisms, design experiments. Follows the scientific method. Use scientific-brainstorming for open ideation; hypogenic for automated LLM hypothesis testing on datasets." license: CC-BY-4.0
Scientific Hypothesis Generation
Overview
Hypothesis generation is a systematic process for developing testable mechanistic explanations from observations. This knowhow covers the full cycle: from understanding a phenomenon through literature synthesis, generating competing hypotheses, evaluating hypothesis quality, designing experimental tests, and formulating testable predictions.
Key Concepts
1. Hypothesis vs Observation vs Prediction
- Observation: A factual statement about what was measured or seen (e.g., "Drug X reduces tumor size in mice")
- Hypothesis: A proposed mechanistic explanation for the observation (e.g., "Drug X inhibits angiogenesis via VEGF pathway blockade, reducing tumor nutrient supply")
- Prediction: A testable consequence of the hypothesis (e.g., "VEGF levels should decrease after Drug X treatment; tumors in VEGF-knockout mice should show no additional effect")
Good hypotheses are mechanistic (explain HOW/WHY), not descriptive (restate WHAT).
2. Hypothesis Quality Criteria
| Criterion | Definition | Example of Strong | Example of Weak | |-----------|-----------|-------------------|-----------------| | Testability | Can be empirically investigated | "Protein X binds to receptor Y" (can test with co-IP) | "Life force drives cellular growth" (untestable) | | Falsifiability | Specific observations would disprove it | "If X is absent, effect disappears" | "X contributes to the effect somehow" | | Parsimony | Simplest explanation fitting the evidence | Single mechanism | Multi-step chain without evidence | | Explanatory Power | Accounts for observed patterns | Explains dose-response and tissue specificity | Explains only one observation | | Scope | Range of phenomena covered | Applies across related systems | Limited to single dataset | | Consistency | Aligns with established knowledge | Consistent with known pathway biology | Contradicts thermodynamics | | Novelty | Offers new insight | Proposes unexplored mechanism | Restates established knowledge |
3. Levels of Mechanistic Explanation
Hypotheses can operate at different scales. Strong hypothesis sets include explanations at multiple levels:
- Molecular: Protein interactions, gene regulation, enzymatic activity
- Cellular: Signaling pathways, cell fate decisions, metabolic changes
- Tissue/Organ: Microenvironment, cell-cell communication, organ function
- Organismal: Systemic responses, physiological adaptation
- Population: Evolutionary pressures, epidemiological patterns
Decision Framework
What is your starting point?
├── Specific observation / data → Follow the full 8-step Workflow below
├── Broad research question → Start with Step 2 (literature search) to narrow scope
├── Existing hypothesis to refine → Start at Step 5 (evaluate quality) and iterate
└── Need creative ideation first → Use scientific-brainstorming skill, then return here
| Starting Situation | Approach | Key Steps | |-------------------|----------|-----------| | Unexpected experimental result | Phenomenon-driven | Steps 1→2→3→4 (focus on competing explanations) | | Literature gap identified | Gap-driven | Steps 2→3→4→5 (focus on novelty criterion) | | Cross-domain analogy noticed | Analogy-driven | Steps 1→4→5→6 (focus on translating mechanism) | | Contradictory findings in literature | Conflict-driven | Steps 2→3→4→7 (focus on discriminating predictions) | | Large dataset patterns | Data-driven | Use hypogenic first, then Steps 5→6→7 here |
Best Practices
-
Always generate competing hypotheses (3–5): A single hypothesis is a confirmation trap. Multiple competing explanations force you to design experiments that discriminate between alternatives, not just confirm your favorite.
-
Start with mechanism, not correlation: "X is associated with Y" is not a hypothesis. "X causes Y via mechanism Z" is. Always include the mechanistic link (HOW the cause produces the effect).
-
Make predictions that differ between hypotheses: The most valuable predictions are those where Hypothesis A predicts outcome X and Hypothesis B predicts outcome Y. This is called a "crucial experiment" — design your tests around these discriminating predictions.
-
Ground every hypothesis in evidence: Cite existing literature for each hypothesis. "It is known that pathway X can regulate process Y [Author, 2023]; therefore, we hypothesize that..." Unsupported hypotheses are speculation, not science.
-
State falsification criteria explicitly: For each hypothesis, write "This hypothesis would be falsified if..." before designing experiments. If you cannot state falsification criteria, the hypothesis is untestable.
-
Consider the null hypothesis: The simplest explanation — that there is no novel mechanism and observed effects are due to known processes, artifact, or chance — should always be included as one of the competing hypotheses.
-
Scale predictions quantitatively when possible: "Expression should increase" is weaker than "Expression should increase 2–5 fold (based on known pathway kinetics)." Quantitative predictions enable power analysis for experimental design.
Common Pitfalls
-
Confirmation bias in hypothesis selection: Generating one "main" hypothesis and 2-3 weak alternatives to make the main one look good. How to avoid: Generate hypotheses independently, then rank them by quality criteria. Have someone else review whether alternatives are genuinely competitive.
-
Untestable "just-so" stories: Hypotheses that sound plausible but cannot be empirically tested with current technology. How to avoid: For each hypothesis, immediately write the experiment that would test it. If you cannot design an experiment, the hypothesis needs revision.
-
Confusing correlation-based claims with mechanistic hypotheses: "Gene X is upregulated in disease Y" is not a hypothesis. How to avoid: Always include HOW and WHY in the hypothesis statement. Use the template: "[Mechanism] leads to [effect] because [rationale]."
-
Ignoring contradictory evidence: Cherry-picking literature that supports your hypothesis while ignoring opposing data. How to avoid: In Step 3 (Synthesize Evidence), explicitly section contradictory findings. Each hypothesis must address how it handles conflicting data.
-
Scope creep in hypothesis evaluation: Trying to make one hypothesis explain everything. How to avoid: A hypothesis does not need to explain all observations — it needs to explain the specific phenomenon under investigation. State scope boundaries explicitly.
-
Designing experiments that can only confirm: If your experiment cannot produce a negative result, it does not test your hypothesis. How to avoid: For each experiment, write down what "failure" looks like. Include negative and positive controls.
-
Neglecting feasibility in experimental design: Proposing experiments requiring technology, samples, or timelines that are unrealistic. How to avoid: Include feasibility assessment (available reagents, equipment, sample access, timeline) alongside each experimental proposal.
Workflow
Structured Hypothesis Generation Process (8 Steps)
-
Understand the phenomenon: Clarify the core observation, define scope and boundaries, note what is known vs uncertain, identify the relevant scientific domain(s)
-
Conduct literature search: Search PubMed (biomedical) and general databases for reviews, primary research, related mechanisms, and analogous systems. Look for gaps, contradictions, and unresolved debates
-
Synthesize existing evidence: Summarize current understanding, identify established mechanisms that may apply, note conflicting evidence, recognize knowledge gaps, find cross-domain analogies
-
Generate 3–5 competing hypotheses: Each must be mechanistic (explain HOW/WHY), distinguishable from others, evidence-grounded, and consider different levels of explanation (molecular → population)
-
Evaluate hypothesis quality: Score each hypothesis against the 7 quality criteria (testability, falsifiability, parsimony, explanatory power, scope, consistency, novelty). Note strengths and weaknesses explicitly
-
Design experimental tests: For each viable hypothesis, propose specific experiments with: measurements, controls, methods, sample sizes, statistical approaches, and potential confounds
-
Formulate testable predictions: State what should be observed if the hypothesis is correct, specify expected direction and magnitude, identify conditions where predictions hold, distinguish predictions between competing hypotheses
-
Present structured output: Organize findings into: executive summary, competing hypotheses with evidence, testable predictions, critical comparisons, and detailed appendices (literature review, experimental protocols, quality assessments)
Further Reading
- Platt, JR (1964) "Strong Inference" — Science 146:347-353. Classic paper on designing experiments to discriminate between competing hypotheses
- Popper, KR (1959) "The Logic of Scientific Discovery" — foundational framework for hypothesis falsification
- Chamberlin, TC (1890) "The Method of Multiple Working Hypotheses" — Science 15:92-96. Original argument for generating competing explanations
- NIH Guide to Hypothesis Development — practical guidance for grant-writing hypothesis sections
- Kell, DB & Oliver, SG (2004) "Here is the evidence, now what is the hypothesis?" — BioEssays 26:99-105. Data-driven hypothesis generation
Related Skills
- scientific-brainstorming — open-ended creative ideation when you need divergent thinking before structured hypothesis formulation
- scientific-critical-thinking — evaluating evidence quality and logical reasoning; complements hypothesis quality assessment
- literature-review — systematic evidence gathering; feeds into Steps 2–3 of this workflow
- statistical-analysis — power analysis and experimental design statistics for Step 6
- scientific-writing — structuring hypothesis-driven manuscripts for publication
Related Skills
Agent-Reach
90.8kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Scrapling
85.7k🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
ruflo
73.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
