- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill hypothesis-generation -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill hypothesis-generation -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill hypothesis-generation -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill hypothesis-generation -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/tree/HEAD/skills/04-K-Dense-AI-claude-scientific-writer/hypothesis-generationDel publicador
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:
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:
references/literature_search_strategies.md for detailed search techniquesAnalyze 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: 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.
For each viable hypothesis, propose specific experiments or studies to test it. Consult references/experimental_design_patterns.md for common approaches:
Experimental design elements:
Consider multiple approaches:
For each hypothesis, generate specific, quantitative predictions:
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):
ewpage before each hypothesis box to prevent content overflowKeep main text highly concise - only the most essential information. All details go to appendices.
Page Break Strategy:
ewpage before hypothesis boxes to ensure they start on fresh pagesAppendices (Comprehensive, Detailed):
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):
All detailed explanations, additional evidence, and comprehensive discussions belong in the appendices.
Critical Overflow Prevention:
ewpage before each hypothesis box to start it on a fresh pageCitation Requirements:
Aim for extensive citation to support all claims:
Main text citations should be selective - cite only the most critical papers. All comprehensive citation and detailed literature discussion belongs in the appendices. Use `
Generate testable hypotheses. Formulate from observations, design experiments, explore competing explanations, develop predictions, propose mechanisms, for scientific inquiry across domains.
---name: hypothesis-generationdescription: Generate testable hypotheses. Formulate from observations, design experiments, explore competing explanations…---# skills/04-K-Dense-AI-claude-scientific-writer/hypothesis-generation/SKILL.mdPreguntas frecuentes
Descarga skills/04-K-Dense-AI-claude-scientific-writer/hypothesis-generation/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.