
ToolUniverse Disease Research
FreeGenerate detailed disease research reports effortlessly.
Free · Opens the source repo
What ToolUniverse Disease Research does
ToolUniverse Disease Research is a Python-based skill designed to assist researchers and healthcare professionals in generating comprehensive disease research reports. By leveraging a variety of established databases and tools, this skill provides a structured approach to compiling information about diseases, including their genetic basis, treatment options, clinical trials, and epidemiological data. The reports are formatted in Markdown, allowing for easy readability and further editing.
The core functionality revolves around a report-first approach, where users can create a new report file for a specific disease and progressively update it with findings from various research dimensions. Each dimension focuses on a different aspect of the disease, such as clinical presentation, genetic and molecular basis, treatment landscape, and more. This structured methodology ensures that all relevant information is captured systematically and cited appropriately, enhancing the reliability of the research.
This skill is particularly useful for medical researchers, geneticists, and healthcare professionals who require detailed insights into specific diseases, including rare and orphan diseases. By utilizing tools like OMIM, OpenTargets, and PubMed, the skill ensures that users have access to the latest and most accurate data available. Furthermore, the emphasis on proper citation practices helps maintain academic integrity and supports users in their research endeavors.
In summary, ToolUniverse Disease Research streamlines the process of disease research by providing a comprehensive framework for report generation, making it an essential tool for anyone involved in medical research or clinical practice.
When to use it
Use this skill when you need to create a detailed report on a specific disease or when someone asks for comprehensive disease intelligence.
When not to use it
This skill may not be suitable for quick, informal inquiries about diseases, as it focuses on generating structured reports rather than providing concise answers.
What you can build with it
Creating a Research Report on Diabetes
When tasked with compiling a report on diabetes, the skill can generate a structured document detailing its genetic factors, treatment options, and clinical trials.
Profiling a Rare Disease
For researchers studying a rare disease, this skill provides a comprehensive overview, including epidemiological data and genetic insights.
Updating Existing Research
If you need to refresh an existing disease report with the latest findings, this skill allows for incremental updates while maintaining citations.
How to install ToolUniverse Disease Research
View source1. Install with the skills CLI
npx skills add mims-harvard/tooluniverse/tooluniverse-disease-research --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by mims-harvardToolUniverse Disease Research
Generate a comprehensive disease research report with full source citations. The report is created as a markdown file and progressively updated during research.
IMPORTANT: Always use English disease names and search terms in tool calls. Respond in the user's language.
LOOK UP, DON'T GUESS
When asked about a disease, query Orphanet/OMIM/DisGeNET FIRST. Don't rely on memory for prevalence, genetics, or treatment — these change over time. When you're not sure about a fact, your first instinct should be to SEARCH for it using tools, not to reason harder from memory.
When to Use
- User asks about any disease, syndrome, or medical condition
- Needs comprehensive disease intelligence or a detailed research report
- Asks "what do we know about [disease]?"
Core Workflow: Report-First Approach
DO NOT show the search process to the user. Instead:
- Create report file first - Initialize
{disease_name}_research_report.md - Research each dimension - Use all relevant tools
- Update report progressively - Write findings after each dimension
- Include citations - Every fact must reference its source tool
Disease Mechanism Reasoning
When synthesizing disease etiology, trace the full pathogenic cascade:
- Genetic basis - Which variants (rare or common) confer risk, and in which genes?
- Molecular mechanism - How do those variants alter protein function, expression, or regulation?
- Cellular effect - What downstream cellular processes are disrupted (signaling, metabolism, stress response)?
- Tissue/organ manifestation - How does cellular dysfunction present as organ-level pathology?
This chain structures the Genetic & Molecular Basis (Section 3) and Biological Pathways (Section 5) sections.
10 Research Dimensions
| Dim | Section | Key Tools |
|---|---|---|
| 1 | Identity & Classification | OSL_get_efo_id_by_disease_name, ols_search_efo_terms, ols_get_efo_term, umls_search_concepts, icd_search_codes, snomed_search_concepts |
| 2 | Clinical Presentation | OpenTargets phenotypes, HPO lookup, MedlinePlus |
| 3 | Genetic & Molecular Basis | OpenTargets targets, ClinVar variants, GWAS associations, gnomAD |
| 4 | Treatment Landscape | OpenTargets drugs, clinical trials, GtoPdb |
| 5 | Biological Pathways | Reactome pathways, humanbase_ppi_analysis, GTEx expression, HPA |
| 6 | Epidemiology & Literature | PubMed, OpenAlex, Europe PMC, Semantic Scholar |
| 7 | Similar Diseases | OpenTargets similar entities |
| 8 | Cancer-Specific (if applicable) | CIViC genes/variants/therapies |
| 9 | Pharmacology | GtoPdb targets/interactions/ligands |
| 10 | Drug Safety | OpenTargets warnings, clinical trial AEs, FAERS |
See: tool_usage_details.md for complete tool calls per section.
Normalizing free text to ontology IDs (Dimension 1)
When the input is messy free text (a sample attribute, a synonym, a tissue/organism label) rather than a clean disease name, use ZOOMA_annotate_text to map it to standardized ontology terms (EFO/MONDO/UBERON/etc.) before lookup. It returns each match as an ontology IRI with a confidence rating (HIGH/GOOD/MEDIUM/LOW), so you can keep only high-confidence hits and feed the resolved ID into OLS / OpenTargets.
tu.run_tool("ZOOMA_annotate_text", {
"property_value": "asthma", # free text to resolve
"property_type": "disease", # optional context hint
"min_confidence": "HIGH", # drop fuzzy matches
"max_results": 3,
})
# -> [{"semantic_tags": ["http://purl.obolibrary.org/obo/MONDO_0004979"],
# "curies": ["MONDO:0004979"], "confidence": "HIGH", "source": "zooma", ...}]
# Restrict to one ontology source (e.g. EFO) when you need a specific namespace:
tu.run_tool("ZOOMA_annotate_text", {"property_value": "diabetes", "ontologies": "efo"})
# Inspect which curated datasources back ZOOMA annotations (for provenance):
tu.run_tool("ZOOMA_list_datasources", {})
# -> [{"name": "eva-clinvar", "type": "DATABASE", "uri": "https://www.ebi.ac.uk/eva"}, ...]
Each match also carries a ready-to-use curies field (e.g. MONDO:0004979) so you can feed the resolved ID straight into OLS / OpenTargets without parsing the IRI. ZOOMA is the live replacement for the retired OxO cross-reference service; pair it with ols_get_efo_term to expand the resolved IRI into labels, synonyms, and hierarchy.
Report Template
Create this file structure at the start:
# Disease Research Report: {Disease Name}
**Report Generated**: {date}
**Disease Identifiers**: (to be filled)
---
## Executive Summary
(Brief 3-5 sentence overview - fill after all research complete)
---
## 1. Disease Identity & Classification
### Ontology Identifiers
| System | ID | Source |
### Synonyms & Alternative Names
### Disease Hierarchy
---
## 2. Clinical Presentation
### Phenotypes (HPO)
| HPO ID | Phenotype | Description | Source |
### Symptoms & Signs
### Diagnostic Criteria
---
## 3. Genetic & Molecular Basis
### Associated Genes
| Gene | Score | Ensembl ID | Evidence | Source |
### GWAS Associations
| SNP | P-value | Odds Ratio | Study | Source |
### Pathogenic Variants (ClinVar)
---
## 4. Treatment Landscape
### Approved Drugs
| Drug | ChEMBL ID | Mechanism | Phase | Target | Source |
### Clinical Trials
| NCT ID | Title | Phase | Status | Source |
---
## 5. Biological Pathways & Mechanisms
## 6. Epidemiology & Risk Factors
## 7. Literature & Research Activity
## 8. Similar Diseases & Comorbidities
## 9. Cancer-Specific Information (if applicable)
## 10. Drug Safety & Adverse Events
---
## References
### Tools Used
| # | Tool | Parameters | Section | Items Retrieved |
Citation Format
Every piece of data MUST include its source:
In tables: Add a Source column with tool name
In lists: - Finding [Source: tool_name]
In prose: (Source: tool_name, query: "...")
References section: Complete tool usage log with parameters
Progressive Update Pattern
# After each dimension's research:
# 1. Read current report
# 2. Replace placeholder with formatted content
# 3. Write back immediately
# 4. Continue to next dimension
Evidence Grading & Interpretation
Every finding in the report should be graded:
| Grade | Criteria | Example |
|---|---|---|
| T1 (Strong) | Replicated genetic evidence (GWAS, rare variants), FDA-approved therapy | BRCA1 → breast cancer; trastuzumab for HER2+ |
| T2 (Moderate) | Single genetic study, phase II+ trial data, strong biological evidence | FOXO3 → longevity (centenarian studies) |
| T3 (Association) | Observational data, gene expression changes, pathway membership | IL-6 elevated in Alzheimer's CSF |
| T4 (Computational) | Network proximity, text mining, predicted associations | DisGeNET text-mined gene-disease link |
Synthesis Questions (answer in Executive Summary)
After collecting data from all 10 dimensions, the report MUST answer:
- What causes this disease? Summarize the genetic architecture (monogenic vs polygenic, key loci, penetrance)
- What are the therapeutic options? Ranked by evidence level and approval status
- What biomarkers exist? For diagnosis, prognosis, and treatment selection
- What's the unmet need? What aspects lack effective treatment or understanding?
- What are the active research frontiers? Based on clinical trials and recent publications
Interpreting Cross-Database Concordance
When multiple databases provide different data for the same disease:
- OpenTargets + DisGeNET + OMIM agree on a gene: T1 evidence — high confidence
- Only OpenTargets reports an association: Check the datasource scores — genetic_association > literature > animal_model
- DisGeNET score > 0.5 but not in OpenTargets: May be text-mined; verify with PubMed
- Gene in GWAS but not OMIM: Likely a complex disease susceptibility locus, not Mendelian
Handling Conflicting Data
| Conflict | Resolution |
|---|---|
| Different prevalence estimates across sources | Report range; note the most recent/largest study |
| Drug approved in one country but not another | Note regulatory status per region |
| Gene-disease association in one DB but absent in another | Grade by evidence type; text-mining alone is T4 |
| Clinical trial results contradict label indications | The trial result is newer evidence; note both |
Final Report Quality Checklist
- All 10 sections have content (or marked "No data available")
- Every data point has a source citation
- Executive summary reflects key findings
- References section lists all tools used
- Tables properly formatted
- No placeholder text remains
Expected Output Scale
For a well-studied disease (e.g., Alzheimer's), the final report should include:
- 5+ ontology IDs, 10+ synonyms, disease hierarchy
- 20+ phenotypes with HPO IDs
- 50+ genes, 30+ GWAS associations, 100+ ClinVar variants
- 20+ drugs, 50+ clinical trials
- 10+ pathways, PPI network, expression data
- 100+ publications
- 15+ similar diseases
- Drug warnings and adverse events
Total: 500+ individual data points, each with source citation.
Cross-Skill References
For rare disease differential diagnosis, run: python3 skills/tooluniverse-rare-disease-diagnosis/scripts/clinical_patterns.py --type differential --symptoms 'symptom1,symptom2'
Reference Files
- REPORT_TEMPLATE.md - Full report markdown template and citation format guide
- RESEARCH_PROTOCOL.md - Step-by-step code procedures, progressive update pattern, quality checklist
- tool_usage_details.md - Complete tool calls for each research dimension
- TOOLS_REFERENCE.md - Complete tool documentation
- EXAMPLES.md - Sample disease research reports
Frequently asked questions about ToolUniverse Disease Research
Similar skills
Scientific Problem Selection
Streamline your research problem selection process.
Nextflow Development
Run nf-core bioinformatics pipelines with ease.
Nature Reviewer Assessment
Simulate peer review for scientific manuscripts.
Research Writing Pipeline
Streamline your scientific writing with structured proposal-first methodologies.
Nature Literature Downloader
Efficiently download academic literature from various sources.
Auto Research
Streamline your NeMo-RL experiments with automated workflows.
