hypothesis-generation

4
0
Source

Generate testable hypotheses. Formulate from observations, design experiments, explore competing explanations, develop predictions, propose mechanisms, for scientific inquiry across domains.

Install

mkdir -p .claude/skills/hypothesis-generation && curl -L -o skill.zip "https://mcp.directory/api/skills/download/2243" && unzip -o skill.zip -d .claude/skills/hypothesis-generation && rm skill.zip

Installs to .claude/skills/hypothesis-generation

About this skill

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:

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)
  • Natural experiments or quasi-experimental designs

7. Formulate Testable Predictions

For each hypothesis, generate specific, quantitative predictions:

  • State what should be observed if the hypothesis is correct
  • Specify expected direction and magnitude of effects when possible
  • Identify conditions under which predictions should hold
  • Distinguish predictions between competing hypotheses
  • Note predictions that would falsify the hypothesis

8. Present Structured Output

Generate a professional LaTeX document using the template in assets/hypothesis_report_template.tex. The report should be well-formatted with colored boxes for visual organization and divided into a concise main text with comprehensive appendices.

Document Structure:

Main Text (Maximum 4 pages):

  1. Executive Summary - Brief overview in summary box (0.5-1 page)
  2. Competing Hypotheses - Each hypothesis in its own colored box with brief mechanistic explanation and key evidence (2-2.5 pages for 3-5 hypotheses)
    • IMPORTANT: Use \newpage before each hypothesis box to prevent content overflow
    • Each box should be ≤0.6 pages maximum
  3. Testable Predictions - Key predictions in amber boxes (0.5-1 page)
  4. Critical Comparisons - Priority comparison boxes (0.5-1 page)

Keep main text highly concise - only the most essential information. All details go to appendices.

Page Break Strategy:

  • Always use \newpage before hypothesis boxes to ensure they start on fresh pages
  • This prevents content from overflowing off page boundaries
  • LaTeX boxes (tcolorbox) do not automatically break across pages

Appendices (Comprehensive, Detailed):

  • Appendix A: Comprehensive literature review with extensive citations
  • Appendix B: Detailed experimental designs with full protocols
  • Appendix C: Quality assessment tables and detailed evaluations
  • Appendix D: Supplementary evidence and analogous systems

Colored Box Usage:

Use the custom box environments from hypothesis_generation.sty:

  • hypothesisbox1 through hypothesisbox5 - For each competing hypothesis (blue, green, purple, teal, orange)
  • predictionbox - For testable predictions (amber)
  • comparisonbox - For critical comparisons (steel gray)
  • evidencebox - For supporting evidence highlights (light blue)
  • summarybox - For executive summary (blue)

Each hypothesis box should contain (keep concise for 4-page limit):

  • Mechanistic Explanation: 1-2 brief paragraphs (6-10 sentences max) explaining HOW and WHY
  • Key Supporting Evidence: 2-3 bullet points with citations (most important evidence only)
  • Core Assumptions: 1-2 critical assumptions

All detailed explanations, additional evidence, and comprehensive discussions belong in the appendices.

Critical Overflow Prevention:

  • Insert \newpage before each hypothesis box to start it on a fresh page
  • Keep each complete hypothesis box to ≤0.6 pages (approximately 15-20 lines of content)
  • If content exceeds this, move additional details to Appendix A
  • Never let boxes overflow off page boundaries - this creates unreadable PDFs

Citation Requirements:

Aim for extensive citation to support all claims:

  • Main text: 10-15 key citations for most important evidence only (keep concise for 4-page limit)
  • Appendix A: 40-70+ comprehensive citations covering all relevant literature
  • Total target: 50+ references in bibliography

Main text citations should be selective - cite only the most critical papers. All comprehensive citation and detailed literature discussion belongs in the appendices. Use \citep{author2023} for parenthetical citations.

LaTeX Compilation:

The template requires XeLaTeX or LuaLaTeX for proper rendering:

xelatex hypothesis_report.tex
bibtex hypothesis_report
xelatex hypothesis_report.tex
xelatex hypothesis_report.tex

Required packages: The hypothesis_generation.sty style package must be in the same directory or LaTeX p


Content truncated.

scroll-experience

davila7

Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.

6230

software-architecture

davila7

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

8125

senior-fullstack

davila7

Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.

8122

senior-security

davila7

Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.

6819

game-development

davila7

Game development orchestrator. Routes to platform-specific skills based on project needs.

5414

2d-games

davila7

2D game development principles. Sprites, tilemaps, physics, camera.

4812

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

643969

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

591705

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318398

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

339397

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

451339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.