[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R3496ACMRTMJFQG4Q2J8C5":3,"skill-same:01M6R3496ACMRTMJFQG4Q2J8C5":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M6R3496ACMRTMJFQG4Q2J8C5","hypothesis-generation",null,"Generate testable hypotheses. Formulate from observations, design experiments, explore competing explanations, develop predictions, propose mechanisms, for scientific inquiry across domains.","Mishit18\u002Fclaude-code-templates","Mishit18","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F244127857?v=4","01M6QXBYKWM76HSKYDNWSKKE41","Mishit Sharma","01M6QXBYRJ0CAVM51S1RTEKTZZ",1,"MIT","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"hypothesis","hypothesis generation","generation","write","for","observations","scientific","predictions","domains","across","edit","design","read","develop","explore","Bash","generate","experiments","2026-11-10 10:12:30",false,"---\nname: hypothesis-generation\ndescription: \"Generate testable hypotheses. Formulate from observations, design experiments, explore competing explanations, develop predictions, propose mechanisms, for scientific inquiry across domains.\"\nallowed-tools: [Read, Write, Edit, Bash]\n---\n\n# Scientific Hypothesis Generation\n\n## Overview\n\nHypothesis 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.\n\n## When to Use This Skill\n\nThis skill should be used when:\n- Developing hypotheses from observations or preliminary data\n- Designing experiments to test scientific questions\n- Exploring competing explanations for phenomena\n- Formulating testable predictions for research\n- Conducting literature-based hypothesis generation\n- Planning mechanistic studies across scientific domains\n\n## Visual Enhancement with Scientific Schematics\n\n**⚠️ MANDATORY: Every hypothesis generation report MUST include at least 1-2 AI-generated figures using the scientific-schematics skill.**\n\nThis is not optional. Hypothesis reports without visual elements are incomplete. Before finalizing any document:\n1. Generate at minimum ONE schematic or diagram (e.g., hypothesis framework showing competing explanations)\n2. Prefer 2-3 figures for comprehensive reports (mechanistic pathway, experimental design flowchart, prediction decision tree)\n\n**How to generate figures:**\n- Use the **scientific-schematics** skill to generate AI-powered publication-quality diagrams\n- Simply describe your desired diagram in natural language\n- Nano Banana Pro will automatically generate, review, and refine the schematic\n\n**How to generate schematics:**\n```bash\npython scripts\u002Fgenerate_schematic.py \"your diagram description\" -o figures\u002Foutput.png\n```\n\nThe AI will automatically:\n- Create publication-quality images with proper formatting\n- Review and refine through multiple iterations\n- Ensure accessibility (colorblind-friendly, high contrast)\n- Save outputs in the figures\u002F directory\n\n**When to add schematics:**\n- Hypothesis framework diagrams showing competing explanations\n- Experimental design flowcharts\n- Mechanistic pathway diagrams\n- Prediction decision trees\n- Causal relationship diagrams\n- Theoretical model visualizations\n- Any complex concept that benefits from visualization\n\nFor detailed guidance on creating schematics, refer to the scientific-schematics skill documentation.\n\n---\n\n## Workflow\n\nFollow this systematic process to generate robust scientific hypotheses:\n\n### 1. Understand the Phenomenon\n\nStart by clarifying the observation, question, or phenomenon that requires explanation:\n\n- Identify the core observation or pattern that needs explanation\n- Define the scope and boundaries of the phenomenon\n- Note any constraints or specific contexts\n- Clarify what is already known vs. what is uncertain\n- Identify the relevant scientific domain(s)\n\n### 2. Conduct Comprehensive Literature Search\n\nSearch existing scientific literature to ground hypotheses in current evidence. Use both PubMed (for biomedical topics) and general web search (for broader scientific domains):\n\n**For biomedical topics:**\n- Use WebFetch with PubMed URLs to access relevant literature\n- Search for recent reviews, meta-analyses, and primary research\n- Look for similar phenomena, related mechanisms, or analogous systems\n\n**For all scientific domains:**\n- Use WebSearch to find recent papers, preprints, and reviews\n- Search for established theories, mechanisms, or frameworks\n- Identify gaps in current understanding\n\n**Search strategy:**\n- Begin with broad searches to understand the landscape\n- Narrow to specific mechanisms, pathways, or theories\n- Look for contradictory findings or unresolved debates\n- Consult `references\u002Fliterature_search_strategies.md` for detailed search techniques\n\n### 3. Synthesize Existing Evidence\n\nAnalyze and integrate findings from literature search:\n\n- Summarize current understanding of the phenomenon\n- Identify established mechanisms or theories that may apply\n- Note conflicting evidence or alternative viewpoints\n- Recognize gaps, limitations, or unanswered questions\n- Identify analogies from related systems or domains\n\n### 4. Generate Competing Hypotheses\n\nDevelop 3-5 distinct hypotheses that could explain the phenomenon. Each hypothesis should:\n\n- Provide a mechanistic explanation (not just description)\n- Be distinguishable from other hypotheses\n- Draw on evidence from the literature synthesis\n- Consider different levels of explanation (molecular, cellular, systemic, population, etc.)\n\n**Strategies for generating hypotheses:**\n- Apply known mechanisms from analogous systems\n- Consider multiple causative pathways\n- Explore different scales of explanation\n- Question assumptions in existing explanations\n- Combine mechanisms in novel ways\n\n### 5. Evaluate Hypothesis Quality\n\nAssess each hypothesis against established quality criteria from `references\u002Fhypothesis_quality_criteria.md`:\n\n**Testability:** Can the hypothesis be empirically tested?\n**Falsifiability:** What observations would disprove it?\n**Parsimony:** Is it the simplest explanation that fits the evidence?\n**Explanatory Power:** How much of the phenomenon does it explain?\n**Scope:** What range of observations does it cover?\n**Consistency:** Does it align with established principles?\n**Novelty:** Does it offer new insights beyond existing explanations?\n\nExplicitly note the strengths and weaknesses of each hypothesis.\n\n### 6. Design Experimental Tests\n\nFor each viable hypothesis, propose specific experiments or studies to test it. Consult `references\u002Fexperimental_design_patterns.md` for common approaches:\n\n**Experimental design elements:**\n- What would be measured or observed?\n- What comparisons or controls are needed?\n- What methods or techniques would be used?\n- What sample sizes or statistical approaches are appropriate?\n- What are potential confounds and how to address them?\n\n**Consider multiple approaches:**\n- Laboratory experiments (in vitro, in vivo, computational)\n- Observational studies (cross-sectional, longitudinal, case-control)\n- Clinical trials (if applicable)\n- Natural experiments or quasi-experimental designs\n\n### 7. Formulate Testable Predictions\n\nFor each hypothesis, generate specific, quantitative predictions:\n\n- State what should be observed if the hypothesis is correct\n- Specify expected direction and magnitude of effects when possible\n- Identify conditions under which predictions should hold\n- Distinguish predictions between competing hypotheses\n- Note predictions that would falsify the hypothesis\n\n### 8. Present Structured Output\n\nGenerate a professional LaTeX document using the template in `assets\u002Fhypothesis_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.\n\n**Document Structure:**\n\n**Main Text (Maximum 4 pages):**\n1. **Executive Summary** - Brief overview in summary box (0.5-1 page)\n2. **Competing Hypotheses** - Each hypothesis in its own colored box with brief mechanistic explanation and key evidence (2-2.5 pages for 3-5 hypotheses)\n   - **IMPORTANT:** Use `\\newpage` before each hypothesis box to prevent content overflow\n   - Each box should be ≤0.6 pages maximum\n3. **Testable Predictions** - Key predictions in amber boxes (0.5-1 page)\n4. **Critical Comparisons** - Priority comparison boxes (0.5-1 page)\n\nKeep main text highly concise - only the most essential information. All details go to appendices.\n\n**Page Break Strategy:**\n- Always use `\\newpage` before hypothesis boxes to ensure they start on fresh pages\n- This prevents content from overflowing off page boundaries\n- LaTeX boxes (tcolorbox) do not automatically break across pages\n\n**Appendices (Comprehensive, Detailed):**\n- **Appendix A:** Comprehensive literature review with extensive citations\n- **Appendix B:** Detailed experimental designs with full protocols\n- **Appendix C:** Quality assessment tables and detailed evaluations\n- **Appendix D:** Supplementary evidence and analogous systems\n\n**Colored Box Usage:**\n\nUse the custom box environments from `hypothesis_generation.sty`:\n\n- `hypothesisbox1` through `hypothesisbox5` - For each competing hypothesis (blue, green, purple, teal, orange)\n- `predictionbox` - For testable predictions (amber)\n- `comparisonbox` - For critical comparisons (steel gray)\n- `evidencebox` - For supporting evidence highlights (light blue)\n- `summarybox` - For executive summary (blue)\n\n**Each hypothesis box should contain (keep concise for 4-page limit):**\n- **Mechanistic Explanation:** 1-2 brief paragraphs (6-10 sentences max) explaining HOW and WHY\n- **Key Supporting Evidence:** 2-3 bullet points with citations (most important evidence only)\n- **Core Assumptions:** 1-2 critical assumptions\n\nAll detailed explanations, additional evidence, and comprehensive discussions belong in the appendices.\n\n**Critical Overflow Prevention:**\n- Insert `\\newpage` before each hypothesis box to start it on a fresh page\n- Keep each complete hypothesis box to ≤0.6 pages (approximately 15-20 lines of content)\n- If content exceeds this, move additional details to Appendix A\n- Never let boxes overflow off page boundaries - this creates unreadable PDFs\n\n**Citation Requirements:**\n\nAim for extensive citation to support all claims:\n- **Main text:** 10-15 key citations for most important evidence only (keep concise for 4-page limit)\n- **Appendix A:** 40-70+ comprehensive citations covering all relevant literature\n- **Total target:** 50+ references in bibliography\n\nMain 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.\n\n**LaTeX Compilation:**\n\nThe template requires XeLaTeX or LuaLaTeX for proper rendering:\n\n```bash\nxelatex hypothesis_report.tex\nbibtex hypothesis_report\nxelatex hypothesis_report.tex\nxelatex hypothesis_report.tex\n```\n\n**Required packages:** The `hypothesis_generation.sty` style package must be in the same directory or LaTeX path. It requires: tcolorbox, xcolor, fontspec, fancyhdr, titlesec, enumitem, booktabs, natbib.\n\n**Page Overflow Prevention:**\n\nTo prevent content from overflowing on pages, follow these critical guidelines:\n\n1. **Monitor Box Content Length:** Each hypothesis box should fit comfortably on a single page. If content exceeds ~0.7 pages, it will likely overflow.\n\n2. **Use Strategic Page Breaks:** Insert `\\newpage` before boxes that contain substantial content:\n   ```latex\n   \\newpage\n   \\begin{hypothesisbox1}[Hypothesis 1: Title]\n   % Long content here\n   \\end{hypothesisbox1}\n   ```\n\n3. **Keep Main Text Boxes Concise:** For the 4-page main text limit:\n   - Each hypothesis box: Maximum 0.5-0.6 pages\n   - Mechanistic explanation: 1-2 brief paragraphs only (6-10 sentences max)\n   - Key evidence: 2-3 bullet points only\n   - Core assumptions: 1-2 items only\n   - If content is longer, move details to appendices\n\n4. **Break Long Content:** If a hypothesis requires extensive explanation, split across main text and appendix:\n   - Main text box: Brief mechanistic overview + 2-3 key evidence points\n   - Appendix A: Detailed mechanism explanation, comprehensive evidence, extended discussion\n\n5. **Test Page Boundaries:** Before each new box, consider if remaining page space is sufficient. If less than 0.6 pages remain, use `\\newpage` to start the box on a fresh page.\n\n6. **Appendix Page Management:** In appendices, use `\\newpage` between major sections to avoid overflow in detailed content areas.\n\n**Quick Reference:** See `assets\u002FFORMATTING_GUIDE.md` for detailed examples of all box types, color schemes, and common formatting patterns.\n\n## Quality Standards\n\nEnsure all generated hypotheses meet these standards:\n\n- **Evidence-based:** Grounded in existing literature with citations\n- **Testable:** Include specific, measurable predictions\n- **Mechanistic:** Explain how\u002Fwhy, not just what\n- **Comprehensive:** Consider alternative explanations\n- **Rigorous:** Include experimental designs to test predictions\n\n## Resources\n\n### references\u002F\n\n- `hypothesis_quality_criteria.md` - Framework for evaluating hypothesis quality (testability, falsifiability, parsimony, explanatory power, scope, consistency)\n- `experimental_design_patterns.md` - Common experimental approaches across domains (RCTs, observational studies, lab experiments, computational models)\n- `literature_search_strategies.md` - Effective search techniques for PubMed and general scientific sources\n\n### assets\u002F\n\n- `hypothesis_generation.sty` - LaTeX style package providing colored boxes, professional formatting, and custom environments for hypothesis reports\n- `hypothesis_report_template.tex` - Complete LaTeX template with main text structure and comprehensive appendix sections\n- `FORMATTING_GUIDE.md` - Quick reference guide with examples of all box types, color schemes, citation practices, and troubleshooting tips\n\n","# Scientific Hypothesis Generation\n\n## Overview\n\nHypothesis 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.\n\n## When to Use This Skill\n\nThis skill should be used when:\n- Developing hypotheses from observations or preliminary data\n- Designing experiments to test scientific questions\n- Exploring competing explanations for phenomena\n- Formulating testable predictions for research\n- Conducting literature-based hypothesis generation\n- Planning mechanistic studies across scientific domains\n\n## Visual Enhancement with Scientific Schematics\n\n**⚠️ MANDATORY: Every hypothesis generation report MUST include at least 1-2 AI-generated figures using the scientific-schematics skill.**\n\nThis is not optional. Hypothesis reports without visual elements are incomplete. Before finalizing any document:\n1. Generate at minimum ONE schematic or diagram (e.g., hypothesis framework showing competing explanations)\n2. Prefer 2-3 figures for comprehensive reports (mechanistic pathway, experimental design flowchart, prediction decision tree)\n\n**How to generate figures:**\n- Use the **scientific-schematics** skill to generate AI-powered publication-quality diagrams\n- Simply describe your desired diagram in natural language\n- Nano Banana Pro will automatically generate, review, and refine the schematic\n\n**How to generate schematics:**\n```bash\npython scripts\u002Fgenerate_schematic.py \"your diagram description\" -o figures\u002Foutput.png\n```\n\nThe AI will automatically:\n- Create publication-quality images with proper formatting\n- Review and refine through multiple iterations\n- Ensure accessibility (colorblind-friendly, high contrast)\n- Save outputs in the figures\u002F directory\n\n**When to add schematics:**\n- Hypothesis framework diagrams showing competing explanations\n- Experimental design flowcharts\n- Mechanistic pathway diagrams\n- Prediction decision trees\n- Causal relationship diagrams\n- Theoretical model visualizations\n- Any complex concept that benefits from visualization\n\nFor detailed guidance on creating schematics, refer to the scientific-schematics skill documentation.\n\n---\n\n## Workflow\n\nFollow this systematic process to generate robust scientific hypotheses:\n\n### 1. Understand the Phenomenon\n\nStart by clarifying the observation, question, or phenomenon that requires explanation:\n\n- Identify the core observation or pattern that needs explanation\n- Define the scope and boundaries of the phenomenon\n- Note any constraints or specific contexts\n- Clarify what is already known vs. what is uncertain\n- Identify the relevant scientific domain(s)\n\n### 2. Conduct Comprehensive Literature Search\n\nSearch existing scientific literature to ground hypotheses in current evidence. Use both PubMed (for biomedical topics) and general web search (for broader scientific domains):\n\n**For biomedical topics:**\n- Use WebFetch with PubMed URLs to access relevant literature\n- Search for recent reviews, meta-analyses, and primary research\n- Look for similar phenomena, related mechanisms, or analogous systems\n\n**For all scientific domains:**\n- Use WebSearch to find recent papers, preprints, and reviews\n- Search for established theories, mechanisms, or frameworks\n- Identify gaps in current understanding\n\n**Search strategy:**\n- Begin with broad searches to understand the landscape\n- Narrow to specific mechanisms, pathways, or theories\n- Look for contradictory findings or unresolved debates\n- Consult `references\u002Fliterature_search_strategies.md` for detailed search techniques\n\n### 3. Synthesize Existing Evidence\n\nAnalyze and integrate findings from literature search:\n\n- Summarize current understanding of the phenomenon\n- Identify established mechanisms or theories that may apply\n- Note conflicting evidence or alternative viewpoints\n- Recognize gaps, limitations, or unanswered questions\n- Identify analogies from related systems or domains\n\n### 4. Generate Competing Hypotheses\n\nDevelop 3-5 distinct hypotheses that could explain the phenomenon. Each hypothesis should:\n\n- Provide a mechanistic explanation (not just description)\n- Be distinguishable from other hypotheses\n- Draw on evidence from the literature synthesis\n- Consider different levels of explanation (molecular, cellular, systemic, population, etc.)\n\n**Strategies for generating hypotheses:**\n- Apply known mechanisms from analogous systems\n- Consider multiple causative pathways\n- Explore different scales of explanation\n- Question assumptions in existing explanations\n- Combine mechanisms in novel ways\n\n### 5. Evaluate Hypothesis Quality\n\nAssess each hypothesis against established quality criteria from `references\u002Fhypothesis_quality_criteria.md`:\n\n**Testability:** Can the hypothesis be empirically tested?\n**Falsifiability:** What observations would disprove it?\n**Parsimony:** Is it the simplest explanation that fits the evidence?\n**Explanatory Power:** How much of the phenomenon does it explain?\n**Scope:** What range of observations does it cover?\n**Consistency:** Does it align with established principles?\n**Novelty:** Does it offer new insights beyond existing explanations?\n\nExplicitly note the strengths and weaknesses of each hypothesis.\n\n### 6. Design Experimental Tests\n\nFor each viable hypothesis, propose specific experiments or studies to test it. Consult `references\u002Fexperimental_design_patterns.md` for common approaches:\n\n**Experimental design elements:**\n- What would be measured or observed?\n- What comparisons or controls are needed?\n- What methods or techniques would be used?\n- What sample sizes or statistical approaches are appropriate?\n- What are potential confounds and how to address them?\n\n**Consider multiple approaches:**\n- Laboratory experiments (in vitro, in vivo, computational)\n- Observational studies (cross-sectional, longitudinal, case-control)\n- Clinical trials (if applicable)\n- Natural experiments or quasi-experimental designs\n\n### 7. Formulate Testable Predictions\n\nFor each hypothesis, generate specific, quantitative predictions:\n\n- State what should be observed if the hypothesis is correct\n- Specify expected direction and magnitude of effects when possible\n- Identify conditions under which predictions should hold\n- Distinguish predictions between competing hypotheses\n- Note predictions that would falsify the hypothesis\n\n### 8. Present Structured Output\n\nGenerate a professional LaTeX document using the template in `assets\u002Fhypothesis_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.\n\n**Document Structure:**\n\n**Main Text (Maximum 4 pages):**\n1. **Executive Summary** - Brief overview in summary box (0.5-1 page)\n2. **Competing Hypotheses** - Each hypothesis in its own colored box with brief mechanistic explanation and key evidence (2-2.5 pages for 3-5 hypotheses)\n   - **IMPORTANT:** Use `\\newpage` before each hypothesis box to prevent content overflow\n   - Each box should be ≤0.6 pages maximum\n3. **Testable Predictions** - Key predictions in amber boxes (0.5-1 page)\n4. **Critical Comparisons** - Priority comparison boxes (0.5-1 page)\n\nKeep main text highly concise - only the most essential information. All details go to appendices.\n\n**Page Break Strategy:**\n- Always use `\\newpage` before hypothesis boxes to ensure they start on fresh pages\n- This prevents content from overflowing off page boundaries\n- LaTeX boxes (tcolorbox) do not automatically break across pages\n\n**Appendices (Comprehensive, Detailed):**\n- **Appendix A:** Comprehensive literature review with extensive citations\n- **Appendix B:** Detailed experimental designs with full protocols\n- **Appendix C:** Quality assessment tables and detailed evaluations\n- **Appendix D:** Supplementary evidence and analogous systems\n\n**Colored Box Usage:**\n\nUse the custom box environments from `hypothesis_generation.sty`:\n\n- `hypothesisbox1` through `hypothesisbox5` - For each competing hypothesis (blue, green, purple, teal, orange)\n- `predictionbox` - For testable predictions (amber)\n- `comparisonbox` - For critical comparisons (steel gray)\n- `evidencebox` - For supporting evidence highlights (light blue)\n- `summarybox` - For executive summary (blue)\n\n**Each hypothesis box should contain (keep concise for 4-page limit):**\n- **Mechanistic Explanation:** 1-2 brief paragraphs (6-10 sentences max) explaining HOW and WHY\n- **Key Supporting Evidence:** 2-3 bullet points with citations (most important evidence only)\n- **Core Assumptions:** 1-2 critical assumptions\n\nAll detailed explanations, additional evidence, and comprehensive discussions belong in the appendices.\n\n**Critical Overflow Prevention:**\n- Insert `\\newpage` before each hypothesis box to start it on a fresh page\n- Keep each complete hypothesis box to ≤0.6 pages (approximately 15-20 lines of content)\n- If content exceeds this, move additional details to Appendix A\n- Never let boxes overflow off page boundaries - this creates unreadable PDFs\n\n**Citation Requirements:**\n\nAim for extensive citation to support all claims:\n- **Main text:** 10-15 key citations for most important evidence only (keep concise for 4-page limit)\n- **Appendix A:** 40-70+ comprehensive citations covering all relevant literature\n- **Total target:** 50+ references in bibliography\n\nMain 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.\n\n**LaTeX Compilation:**\n\nThe template requires XeLaTeX or LuaLaTeX for proper rendering:\n\n```bash\nxelatex hypothesis_report.tex\nbibtex hypothesis_report\nxelatex hypothesis_report.tex\nxelatex hypothesis_report.tex\n```\n\n**Required packages:** The `hypothesis_generation.sty` style package must be in the same directory or LaTeX path. It requires: tcolorbox, xcolor, fontspec, fancyhdr, titlesec, enumitem, booktabs, natbib.\n\n**Page Overflow Prevention:**\n\nTo prevent content from overflowing on pages, follow these critical guidelines:\n\n1. **Monitor Box Content Length:** Each hypothesis box should fit comfortably on a single page. If content exceeds ~0.7 pages, it will likely overflow.\n\n2. **Use Strategic Page Breaks:** Insert `\\newpage` before boxes that contain substantial content:\n   ```latex\n   \\newpage\n   \\begin{hypothesisbox1}[Hypothesis 1: Title]\n   % Long content here\n   \\end{hypothesisbox1}\n   ```\n\n3. **Keep Main Text Boxes Concise:** For the 4-page main text limit:\n   - Each hypothesis box: Maximum 0.5-0.6 pages\n   - Mechanistic explanation: 1-2 brief paragraphs only (6-10 sentences max)\n   - Key evidence: 2-3 bullet points only\n   - Core assumptions: 1-2 items only\n   - If content is longer, move details to appendices\n\n4. **Break Long Content:** If a hypothesis requires extensive explanation, split across main text and appendix:\n   - Main text box: Brief mechanistic overview + 2-3 key evidence points\n   - Appendix A: Detailed mechanism explanation, comprehensive evidence, extended discussion\n\n5. **Test Page Boundaries:** Before each new box, consider if remaining page space is sufficient. If less than 0.6 pages remain, use `\\newpage` to start the box on a fresh page.\n\n6. **Appendix Page Management:** In appendices, use `\\newpage` between major sections to avoid overflow in detailed content areas.\n\n**Quick Reference:** See `assets\u002FFORMATTING_GUIDE.md` for detailed examples of all box types, color schemes, and common formatting patterns.\n\n## Quality Standards\n\nEnsure all generated hypotheses meet these standards:\n\n- **Evidence-based:** Grounded in existing literature with citations\n- **Testable:** Include specific, measurable predictions\n- **Mechanistic:** Explain how\u002Fwhy, not just what\n- **Comprehensive:** Consider alternative explanations\n- **Rigorous:** Include experimental designs to test predictions\n\n## Resources\n\n### references\u002F\n\n- `hypothesis_quality_criteria.md` - Framework for evaluating hypothesis quality (testability, falsifiability, parsimony, explanatory power, scope, consistency)\n- `experimental_design_patterns.md` - Common experimental approaches across domains (RCTs, observational studies, lab experiments, computational models)\n- `literature_search_strategies.md` - Effective search techniques for PubMed and general scientific sources\n\n### assets\u002F\n\n- `hypothesis_generation.sty` - LaTeX style package providing colored boxes, professional formatting, and custom environments for hypothesis reports\n- `hypothesis_report_template.tex` - Complete LaTeX template with main text structure and comprehensive appendix sections\n- `FORMATTING_GUIDE.md` - Quick reference guide with examples of all box types, color schemes, citation practices, and troubleshooting tips\n\n",{"name":5,"description":7,"allowed-tools":52},[53,54,55,44],"Read","Write","Edit","main","015422534a7457348a313b6381f0255d3364eb8c","cli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation",0,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FMishit18","2026-11-13 18:15:57",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add Mishit18\u002Fclaude-code-templates --skill hypothesis-generation",{"tool":69,"command":70},"bunx","bunx skills add Mishit18\u002Fclaude-code-templates --skill hypothesis-generation",{"tool":72,"command":73},"pnpm","pnpm dlx skills add Mishit18\u002Fclaude-code-templates --skill hypothesis-generation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002FSKILL.md",true,[77,83,87,91,97,101],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"assets\u002FFORMATTING_GUIDE.md","ASSET","资产文件",19305,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Fassets\u002FFORMATTING_GUIDE.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"assets\u002Fhypothesis_generation.sty",7626,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Fassets\u002Fhypothesis_generation.sty",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Fhypothesis_report_template.tex",20149,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Fassets\u002Fhypothesis_report_template.tex",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fexperimental_design_patterns.md","REFERENCE","参考文档",14209,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Freferences\u002Fexperimental_design_patterns.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fhypothesis_quality_criteria.md",8052,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Freferences\u002Fhypothesis_quality_criteria.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fliterature_search_strategies.md",16657,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Freferences\u002Fliterature_search_strategies.md",[106,137,163,190,217,240],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":117,"publishedAt":47},"01M6R4ARN4W2VZRDERDTMN1KP0","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,33,136],"web artifacts builder","web","artifacts","artifacts builder","builder","frontend","css","components","react","routing","state management","state","file","Tailwind","use","single-file","ui components","multi","single",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":148,"publishedAt":47},"01M6R45GXREM5DP8T08MAC788H","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[144,147],{"categoryNo":145,"categoryName":146,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},[149,150,151,123,152,153,119,154,155,156,157,158,159,160,161,162,33],"testing","webapp testing","webapp","screenshots","playwright","debugging","toolkit","browser","ui","logs","applications","behavior","local","with",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":47},"01M6R2GYJ470X8EB7R58V0B68K","think-tank","Run a Virtual Think Tank — a structured multi-persona debate — before planning or making architectural\u002Fdesign\u002Fstrategic decisions. Use this skill whenever the user is about to plan a system, make a technology choice, evaluate trade-offs, decide on an approach, or faces any decision where multiple perspectives would sharpen the outcome. Also trigger when the user says \"think tank\", \"debate this\", \"perspectives on\", \"trade-offs\", \"should I use X or Y\", \"help me decide\", \"before we plan\", or asks for pros\u002Fcons of competing approaches. This skill should run BEFORE any implementation planning begins — it produces a structured analysis that feeds into better plans.","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fthink-tank\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fthink-tank\u002FSKILL.md",[],[171,172,40,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189],"think tank","think","run","feeds","analysis","persona","plan","sharpen","virtual","decision","choice","decide","perspectives","outcome","me","debate","make","trade-offs","when",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":194,"sourceHtmlUrl":195,"categories":196,"keywords":200,"publishedAt":47},"01M6R2FSR55AVRFA9YZ8SC2GZG","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FSKILL.md",[197],{"categoryNo":198,"categoryName":199,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[201,202,203,204,205,206,207,208,209,210,211,212,213,214,162,33,215,189,216],"skill creator","creator","workflows","create","update","capabilities","knowledge","tool","integrations","specialized","guide","new skill","existing skill","users","Existing","new",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":47},"01M6R2FK42ZZ4HJTJVVK9WJBBP","ship-learn-next","Transform learning content (like YouTube transcripts, articles, tutorials) into actionable implementation plans using the Ship-Learn-Next framework. Use when user wants to turn advice, lessons, or educational content into concrete action steps, reps, or a learning quest.","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fship-learn-next\u002FSKILL.md",[],[224,225,226,227,228,229,41,32,132,230,231,232,233,234,235,236,237,238,239,189],"learn","ship learn next","ship","next","framework","learning","advice","implementation","youtube","plans","quest","transform","actionable","action","lessons","youtube transcripts",{"skillNo":241,"name":242,"nameZh":6,"description":243,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":244,"sourceHtmlUrl":245,"categories":246,"keywords":253,"publishedAt":47},"01M6R2088G1RHDA5MDX16HASRB","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fslack-gif-creator\u002FSKILL.md",[247,250],{"categoryNo":248,"categoryName":249,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":251,"categoryName":252,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[254,255,256,202,257,258,259,260,207,132,185,214,187,261,262,33,263,189],"slack gif creator","slack","gif","validation","Tools","constraints","Animation","Utilities","concepts","request"]