brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Structured hypothesis formulation from observations. Use when you have experimental observations or data and need to formulate testable hypotheses with predictions, propose mechanisms, and design experiments to test them. Follows scientific method framework. For open-ended
$ npx -y skills add xintaofei/codeg --skill hypothesis-generation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/hypothesis-generationContext preview
The summary Claude sees to decide when to auto-load this skill.
Structured hypothesis formulation from observations. Use when you have experimental observations or data and need to formulate testable hypotheses with predictions, propose mechanisms, and design experiments to test them. Follows scientific method framework. For open-ended
name: hypothesis-generation
description: Structured hypothesis formulation from observations. Use when you have experimental observations or data and need to formulate testable hypotheses with predictions, propose mechanisms, and design experiments to test them. Follows scientific method framework. For open-ended ideation use scientific-brainstorming; for automated LLM-driven hypothesis testing on datasets use hypogenic.
allowed-tools: Read Write Edit Bash
license: MIT license
required_environment_variables: [{"name": "OPENROUTER_API_KEY", "prompt": "OpenRouter API key for the skill's LLM-powered steps.", "required_for": "optional features"}]
metadata: {"version": "1.1", "skill-author": "K-Dense Inc.", "openclaw": {"primaryEnv": "OPENROUTER_API_KEY", "envVars": [{"name": "OPENROUTER_API_KEY", "required": false, "description": "OpenRouter API key for the skill's LLM-powered steps."}]}}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.
This skill should be used when:
**⚠️ 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:**
**How to generate schematics:**
python scripts/generate_schematic.py "your diagram description" -o figures/output.png
The AI will automatically:
**When to add schematics:**
For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation.
---
Follow this systematic process to generate robust scientific hypotheses:
Start by clarifying the observation, question, or phenomenon that requires explanation:
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:**
**For all scientific domains:**
**Search strategy:**
Analyze and integrate findings from literature search:
Develop 3-5 distinct hypotheses that could explain the phenomenon. Each hypothesis should:
**Strategies for generating hypotheses:**
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:** Wh
English | 简体中文 | 繁體中文 | 日本語 | 한국어 | Español | Deutsch | Français | Português | العربية Codeg (Code Generation) is a multi-agent coding workspace: run every AI coding agent in one place — and let them work together.
Repo: xintaofei/codeg
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements