hypothesis-generation
This Claude Code skill generates testable scientific hypotheses from observations and experimental data by systematically formulating evidence-based explanations, exploring competing mechanisms, and designing experiments to validate them. Use it when analyzing preliminary findings, planning mechanistic studies, or structuring research inquiries that require predictions and experimental designs following established scientific method frameworks.
git clone --depth 1 https://github.com/K-Dense-AI/scientific-agent-skills /tmp/hypothesis-generation && cp -r /tmp/hypothesis-generation/skills/hypothesis-generation ~/.claude/skills/hypothesis-generationSKILL.md
# Scientific Hypothesis Generation ## Overview Hypothesis generation is a systematic process for developing testable explanations. Formulate evidence-based hypotheses from observations, design experiments, explore competing explanations, and develop predictions. Apply this skill for scientific inquiry across domains. ## When to Use This Skill This skill should be used when: - Developing hypotheses from observations or preliminary data - Designing experiments to test scientific questions - Exploring competing explanations for phenomena - Formulating testable predictions for research - Conducting literature-based hypothesis generation - Planning mechanistic studies across scientific domains ## Visual Enhancement with Scientific Schematics **⚠️ MANDATORY: Every hypothesis generation report MUST include at least 1-2 AI-generated figures using the scientific-schematics skill.** This is not optional. Hypothesis reports without visual elements are incomplete. Before finalizing any document: 1. Generate at minimum ONE schematic or diagram (e.g., hypothesis framework showing competing explanations) 2. Prefer 2-3 figures for comprehensive reports (mechanistic pathway, experimental design flowchart, prediction decision tree) **How to generate figures:** - Use the **scientific-schematics** skill to generate AI-powered publication-quality diagrams - Simply describe your desired diagram in natural language - Nano Banana Pro will automatically generate, review, and refine the schematic **How to generate schematics:** ```bash python scripts/generate_schematic.py "your diagram description" -o figures/output.png ``` The AI will automatically: - Create publication-quality images with proper formatting - Review and refine through multiple iterations - Ensure accessibility (colorblind-friendly, high contrast) - Save outputs in the figures/ directory **When to add schematics:** - Hypothesis framework diagrams showing competing explanations - Experimental design flowcharts - Mechanistic pathway diagrams - Prediction decision trees - Causal relationship diagrams - Theoretical model visualizations - Any complex concept that benefits from visualization For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation. --- ## Workflow Follow this systematic process to generate robust scientific hypotheses: ### 1. Understand the Phenomenon Start by clarifying the observation, question, or phenomenon that requires explanation: - Identify the core observation or pattern that needs explanation - Define the scope and boundaries of the phenomenon - Note any constraints or specific contexts - Clarify what is already known vs. what is uncertain - Identify the relevant scientific domain(s) ### 2. Conduct Comprehensive Literature Search Search existing scientific literature to ground hypotheses in current evidence. Use both PubMed (for biomedical topics) and general web search (for broader scientific domains): **For biomedical topics:** - Use WebFetch with PubMed URLs to access relevant literature - Search for recent reviews, meta-analyses, and primary research - Look for similar phenomena, related mechanisms, or analogous systems **For all scientific domains:** - Use WebSearch to find recent papers, preprints, and reviews - Search for established theories, mechanisms, or frameworks - Identify gaps in current understanding **Search strategy:** - Begin with broad searches to understand the landscape - Narrow to specific mechanisms, pathways, or theories - Look for contradictory findings or unresolved debates - Consult `references/literature_search_strategies.md` for detailed search techniques ### 3. Synthesize Existing Evidence Analyze and integrate findings from literature search: - Summarize current understanding of the phenomenon - Identify established mechanisms or theories that may apply - Note conflicting evidence or alternative viewpoints - Recognize gaps, limitations, or unanswered questions - Identify analogies from related systems or domains ### 4. Generate Competing Hypotheses Develop 3-5 distinct hypotheses that could explain the phenomenon. Each hypothesis should: - Provide a mechanistic explanation (not just description) - Be distinguishable from other hypotheses - Draw on evidence from the literature synthesis - Consider different levels of explanation (molecular, cellular, systemic, population, etc.) **Strategies for generating hypotheses:** - Apply known mechanisms from analogous systems - Consider multiple causative pathways - Explore different scales of explanation - Question assumptions in existing explanations - Combine mechanisms in novel ways ### 5. Evaluate Hypothesis Quality Assess each hypothesis against established quality criteria from `references/hypothesis_quality_criteria.md`: **Testability:** Can the hypothesis be empirically tested? **Falsifiability:** What observations would disprove it? **Parsimony:** Is it the simplest explanation that fits the evidence? **Explanatory Power:** How much of the phenomenon does it explain? **Scope:** What range of observations does it cover? **Consistency:** Does it align with established principles? **Novelty:** Does it offer new insights beyond existing explanations? Explicitly note the strengths and weaknesses of each hypothesis. ### 6. Design Experimental Tests For each viable hypothesis, propose specific experiments or studies to test it. Consult `references/experimental_design_patterns.md` for common approaches: **Experimental design elements:** - What would be measured or observed? - What comparisons or controls are needed? - What methods or techniques would be used? - What sample sizes or statistical approaches are appropriate? - What are potential confounds and how to address them? **Consider multiple approaches:** - Laboratory experiments (in vitro, in vivo, computational) - Observational studies (cross-sectional, longitudinal, case-control) - Clinical trials (if applicable) -
How to use the Adaptyv Bio Foundry API and Python SDK for protein experiment design, submission, and results retrieval. Use this skill whenever the user mentions Adaptyv, Foundry API, protein binding assays, protein screening experiments, BLI/SPR assays, thermostability assays, or wants to submit protein sequences for experimental characterization. Also trigger when code imports `adaptyv`, `adaptyv_sdk`, or `FoundryClient`, or references `foundry-api-public.adaptyvbio.com`.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Infer gene regulatory networks (GRNs) from gene expression data using scalable algorithms (GRNBoost2, GENIE3). Use when analyzing transcriptomics data (bulk RNA-seq, single-cell RNA-seq) to identify transcription factor-target gene relationships and regulatory interactions. Supports distributed computation for large-scale datasets.
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
Observe the user's screen via screenpipe, detect repeated research workflows, match them against existing scientific-agent-skills, and draft new skills (or composition recipes that chain existing ones) for the patterns not yet covered. Use when the user asks to analyze their recent work and propose skills based on what they actually do. Requires the screenpipe daemon (https://github.com/screenpipe/screenpipe) running locally on port 3030 — the skill has no other data source and will refuse to run if screenpipe is unreachable. All detection runs locally; only redacted cluster summaries reach the LLM.
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server. Returns 25+ fields per paper including methods, results, sample sizes, quality scores, and conclusions. Use for literature reviews, evidence synthesis, and finding experimental details not available in abstracts alone.