tooluniverse-disease-research

mims-harvard/tooluniverse · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-disease-research
0 commentsdiscussion
summary

Generate a comprehensive disease research report with full source citations. The report is created as a markdown file and progressively updated during research.

skill.md

ToolUniverse 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:

  1. Create report file first - Initialize {disease_name}_research_report.md
  2. Research each dimension - Use all relevant tools
  3. Update report progressively - Write findings after each dimension
  4. Include citations - Every fact must reference its source tool

Disease Mechanism Reasoning

When synthesizing disease etiology, trace the full pathogenic cascade:

  1. Genetic basis - Which variants (rare or common) confer risk, and in which genes?
  2. Molecular mechanism - How do those variants alter protein function, expression, or regulation?
  3. Cellular effect - What downstream cellular processes are disrupted (signaling, metabolism, stress response)?
  4. 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.


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:

  1. What causes this disease? Summarize the genetic architecture (monogenic vs polygenic, key loci, penetrance)
  2. What are the therapeutic options? Ranked by evidence level and approval status
  3. What biomarkers exist? For diagnosis, prognosis, and treatment selection
  4. What's the unmet need? What aspects lack effective treatment or understanding?
  5. 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

how to use tooluniverse-disease-research

How to use tooluniverse-disease-research on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add tooluniverse-disease-research
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-disease-research

The skills CLI fetches tooluniverse-disease-research from GitHub repository mims-harvard/tooluniverse and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/tooluniverse-disease-research

Reload or restart Cursor to activate tooluniverse-disease-research. Access the skill through slash commands (e.g., /tooluniverse-disease-research) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.537 reviews
  • Olivia Rao· Dec 28, 2024

    Registry listing for tooluniverse-disease-research matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Nikhil Li· Dec 16, 2024

    Keeps context tight: tooluniverse-disease-research is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Amina Li· Dec 16, 2024

    Useful defaults in tooluniverse-disease-research — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Shikha Mishra· Dec 8, 2024

    I recommend tooluniverse-disease-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kaira Malhotra· Nov 23, 2024

    tooluniverse-disease-research reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • William Kim· Nov 19, 2024

    Solid pick for teams standardizing on skills: tooluniverse-disease-research is focused, and the summary matches what you get after install.

  • Nikhil Thomas· Nov 7, 2024

    tooluniverse-disease-research is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Sakura Chen· Nov 7, 2024

    tooluniverse-disease-research has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Li Agarwal· Oct 26, 2024

    Useful defaults in tooluniverse-disease-research — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ren Brown· Oct 26, 2024

    Keeps context tight: tooluniverse-disease-research is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 37

1 / 4