[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFF7WA662AHQMWFG48G9WK":3,"skill-same:01M6AFF7WA662AHQMWFG48G9WK":111},{"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":31,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6AFF7WA662AHQMWFG48G9WK","hypothesis-generation",null,"Generate testable hypotheses. Formulate from observations, design experiments, explore competing explanations, develop predictions, propose mechanisms, for scientific inquiry across domains.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"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","# 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",{"name":5,"description":7,"allowed-tools":55},[56,57,58,47],"Read","Write","Edit","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add davila7\u002Fclaude-code-templates --skill hypothesis-generation",{"tool":75,"command":76},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill hypothesis-generation",{"tool":78,"command":79},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill hypothesis-generation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002FSKILL.md",true,[83,89,93,97,103,107],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"assets\u002FFORMATTING_GUIDE.md","ASSET","资产文件",19304,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Fassets\u002FFORMATTING_GUIDE.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"assets\u002Fhypothesis_generation.sty",7625,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Fassets\u002Fhypothesis_generation.sty",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"assets\u002Fhypothesis_report_template.tex",20148,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Fassets\u002Fhypothesis_report_template.tex",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fexperimental_design_patterns.md","REFERENCE","参考文档",14208,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Freferences\u002Fexperimental_design_patterns.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fhypothesis_quality_criteria.md",8051,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Freferences\u002Fhypothesis_quality_criteria.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fliterature_search_strategies.md",16656,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fhypothesis-generation\u002Freferences\u002Fliterature_search_strategies.md",[112,139,166,197,232,256],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":50},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[118],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,123,124,36,125,126,127,128,129,130,131,132,133,134,135,136,137,138],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":50},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[145],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[147,148,149,150,151,152,153,154,155,156,157,128,158,159,160,161,162,163,164,165],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":179,"publishedAt":50},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[172,175,176],{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":177,"categoryName":178,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",[180,181,182,183,184,185,186,36,187,188,189,190,191,192,193,127,194,195,128,196],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":201,"licenseFileUrl":202,"sourceHtmlUrl":203,"categories":204,"keywords":208,"publishedAt":50},"01M6AFY6F7CC2BBZP1QD6VTNVC","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\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[205],{"categoryNo":206,"categoryName":207,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,36,231],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":201,"licenseFileUrl":236,"sourceHtmlUrl":237,"categories":238,"keywords":243,"publishedAt":50},"01M6AFWF33SFV9Z3SF4PEEE4BF","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\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[239,242],{"categoryNo":240,"categoryName":241,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":206,"categoryName":207,"taxonomyType":21,"taxonomyTypeDesc":22},[244,245,246,247,248,210,249,219,220,250,251,252,253,36,254,130,255],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":257,"name":258,"nameZh":6,"description":259,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":201,"licenseFileUrl":260,"sourceHtmlUrl":261,"categories":262,"keywords":270,"publishedAt":50},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[263,266,267],{"categoryNo":264,"categoryName":265,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":268,"categoryName":269,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者",[271,272,273,274,275,276,277,278,212,279,222,158,280,281,282,283,284,192,285,128,286,287,288,289,290,136,291],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]