tooluniverse-infectious-disease

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-infectious-disease
0 commentsdiscussion
summary

When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.

skill.md

COMPUTE, DON'T DESCRIBE

When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it.

Infectious Disease Outbreak Intelligence

Rapid response system for emerging pathogens using taxonomy analysis, target identification, structure prediction, and computational drug repurposing.

KEY PRINCIPLES:

  1. Speed is critical - Optimize for rapid actionable intelligence
  2. Target essential proteins - Focus on conserved, essential viral/bacterial proteins
  3. Leverage existing drugs - Prioritize FDA-approved compounds for repurposing
  4. Structure-guided - Use NvidiaNIM for rapid structure prediction and docking
  5. Evidence-graded - Grade repurposing candidates by evidence strength
  6. Actionable output - Prioritized drug candidates with rationale
  7. English-first queries - Always use English terms in tool calls; respond in user's language

REASONING STRATEGY — Start Here: Start with pathogen identification: What type of organism? (virus, bacteria, fungus, parasite). Then ask:

  • What are the essential proteins? (required for replication or viability — cannot be mutated away)
  • Which are surface-exposed? (accessible to drugs and antibodies)
  • Which are conserved across strains? (targeting conserved regions prevents resistance escape) These three questions define your drug targets and vaccine candidates. Organisms in the same genus share targets — look up drug precedent for related pathogens before predicting from scratch.

LOOK UP DON'T GUESS: Never assume a pathogen's taxonomy, genome size, or protein function. Always call BVBRC_search_taxonomy or UniProt_search first. Even well-known pathogens have strains with different drug susceptibility profiles — look up the specific strain when known.


When to Use

Apply when user asks:

  • "New pathogen detected - what drugs might work?"
  • "Emerging virus [X] - therapeutic options?"
  • "Drug repurposing candidates for [pathogen]"
  • "What do we know about [novel coronavirus/bacteria]?"
  • "Essential targets in [pathogen] for drug development"
  • "Can we repurpose [drug] against [pathogen]?"

Critical Workflow Requirements

1. Report-First Approach (MANDATORY)

  1. Create [PATHOGEN]_outbreak_intelligence.md FIRST with section headers
  2. Progressively update as data is gathered
  3. Output separate files: [PATHOGEN]_drug_candidates.csv, [PATHOGEN]_target_proteins.csv

2. Citation Requirements (MANDATORY)

Every finding must have inline source attribution:

### Target: RNA-dependent RNA polymerase (RdRp)
- **UniProt**: P0DTD1 (NSP12)
- **Essentiality**: Required for replication
*Source: UniProt via `UniProt_search`, literature review*

Phase 0: Tool Verification

Known Parameter Corrections

Tool WRONG Parameter CORRECT Parameter
NCBIDatasets_get_taxonomy name tax_id (integer) or use BVBRC_search_taxonomy for keyword search
UniProt_search name query
ChEMBL_search_targets query, target pref_name__contains (substring match)
get_diffdock_info protein_file protein (content)
drugbank_full_search (may fail) Use drugbank_vocab_search as primary DrugBank lookup

PubMed tip: Use sort="relevance" (default) not sort="pub_date" — date-sorted queries can return empty for narrow topics. Tool name: PubMed_search_articles. FDA labels: Use FDA_get_drug_label_info_by_field_value with targeted return_fields to avoid oversized responses from OpenFDA_search_drug_labels.


Workflow Overview

Phase 1: Pathogen Identification
├── Taxonomic classification (NCBI Taxonomy)
├── Closest relatives (for knowledge transfer)
├── Genome/proteome availability
└── OUTPUT: Pathogen profile
    |
Phase 2: Target Identification
├── Essential genes/proteins (UniProt)
├── Conservation across strains
├── Druggability assessment (ChEMBL)
└── OUTPUT: Prioritized target list (scored by essentiality/conservation/druggability/precedent)
    |
Phase 3: Structure Prediction (NvidiaNIM)
├── AlphaFold2/ESMFold for targets
├── Binding site identification
├── Quality assessment (pLDDT)
└── OUTPUT: Target structures (docking-ready if pLDDT > 70)
    |
Phase 4: Drug Repurposing Screen
├── Approved drugs for related pathogens (ChEMBL)
├── Broad-spectrum antivirals/antibiotics
├── Docking screen (get_diffdock_info)
└── OUTPUT: Ranked candidate drugs
    |
Phase 4.5: Pathway Analysis
├── KEGG: Pathogen metabolism pathways
├── Essential metabolic targets
├── Host-pathogen interaction pathways
└── OUTPUT: Pathway-based drug targets
    |
Phase 5: Literature Intelligence
├── PubMed: Published outbreak reports
├── BioRxiv/MedRxiv: Recent preprints (CRITICAL for outbreaks)
├── ArXiv: Computational/ML preprints
├── OpenAlex: Citation tracking
├── ClinicalTrials.gov: Active trials
└── OUTPUT: Evidence synthesis
    |
Phase 6: Report Synthesis
├── Top drug candidates with evidence grades
├── Clinical trial opportunities
├── Recommended immediate actions
└── OUTPUT: Final report

Phase Summaries

Phase 1: Pathogen Identification

Classify via NCBI Taxonomy (query param). Identify related pathogens with existing drugs for knowledge transfer. Determine genome/proteome availability.

Knowledge transfer principle: Drugs effective against related pathogens are the highest-priority repurposing candidates. A protease inhibitor for SARS-CoV-1 is immediately relevant to SARS-CoV-2. Look up the related pathogen's approved drugs in ChEMBL before generating candidates from first principles.

Phase 2: Target Identification

Search UniProt for pathogen proteins (reviewed). Check ChEMBL for drug precedent. Score targets by: Essentiality (30%), Conservation (25%), Druggability (25%), Drug precedent (20%). Aim for 5+ targets.

Phase 3: Structure Prediction

Use NvidiaNIM AlphaFold2 for top 3 targets. Assess pLDDT confidence. Only dock structures with pLDDT > 70 (active site > 90 preferred). Fallback: alphafold_get_prediction or ESMFold_predict_structure.

Phase 4: Drug Repurposing Screen

Source candidates from: related pathogen drugs, broad-spectrum antivirals, target class drugs (DGIdb). Dock top 20+ candidates via get_diffdock_info. Rank by docking score and evidence tier.

Phase 4.5: Pathway Analysis

Use KEGG to identify essential metabolic pathways. Map host-pathogen interaction points. Identify pathway-based drug targets beyond direct protein inhibition.

Phase 5: Literature Intelligence

Search PubMed (peer-reviewed), BioRxiv/MedRxiv (preprints - critical for outbreaks), ArXiv (computational), ClinicalTrials.gov (active trials). Track citations via OpenAlex. Note: preprints are NOT peer-reviewed.

Phase 6: Report Synthesis

Aggregate all findings into final report. Grade every candidate. Provide 3+ immediate actions, clinical trial opportunities, and research priorities.


Evidence Grading

Tier Symbol Criteria Example
T1 [T1] FDA approved for this pathogen Remdesivir for COVID
T2 [T2] Clinical trial evidence OR approved for related pathogen Favipiravir
T3 [T3] In vitro activity OR strong docking + mechanism Sofosbuvir
T4 [T4] Computational prediction only Novel docking hits

Completeness Checklist

Phase 1: Pathogen ID

  • Taxonomic classification complete
  • Related pathogens identified
  • Genome/proteome availability noted

Phase 2: Targets

  • 5+ targets identified
  • Essentiality documented
  • Conservation assessed
  • Drug precedent checked

Phase 3: Structures

  • Structures predicted for top 3 targets
  • pLDDT confidence reported
  • Binding sites identified

Phase 4: Drug Screen

  • 20+ candidates screened
  • FDA-approved drugs prioritized
  • Docking scores reported
  • Top 5 candidates detailed

Phase 5: Literature

  • Recent papers summarized
  • Active trials listed
  • Resistance data noted

Phase 6: Recommendations

  • 3+ immediate actions
  • Clinical trial opportunities
  • Research priorities

Fallback Chains

Primary Tool Fallback 1 Fallback 2
NvidiaNIM_alphafold2 alphafold_get_prediction ESMFold_predict_structure
get_diffdock_info NvidiaNIM_boltz2 Manual docking
NCBIDatasets_suggest_taxonomy UniProtTaxonomy_get_taxon Manual classification
ChEMBL_search_drugs drugbank_vocab_search PubChem bioassays

References

File Contents
TOOLS_REFERENCE.md Complete tool documentation
phase_details.md Detailed code examples and procedures for each phase
report_template.md Report template with section headers, checklist, and evidence grading
CHECKLIST.md Pre-delivery verification checklist (quality, citations, docking)
EXAMPLES.md Full worked examples (coronavirus, CRKP, limited-info scenarios)
how to use tooluniverse-infectious-disease

How to use tooluniverse-infectious-disease 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-infectious-disease
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-infectious-disease

The skills CLI fetches tooluniverse-infectious-disease 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-infectious-disease

Reload or restart Cursor to activate tooluniverse-infectious-disease. Access the skill through slash commands (e.g., /tooluniverse-infectious-disease) 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.452 reviews
  • Aditi Martinez· Dec 28, 2024

    tooluniverse-infectious-disease fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Dhruvi Jain· Dec 24, 2024

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

  • Ishan Farah· Dec 20, 2024

    We added tooluniverse-infectious-disease from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Liam Haddad· Dec 8, 2024

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

  • Olivia Liu· Dec 4, 2024

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

  • Noah Liu· Nov 27, 2024

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

  • Ishan Rahman· Nov 23, 2024

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

  • Hiroshi Thomas· Nov 19, 2024

    We added tooluniverse-infectious-disease from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Oshnikdeep· Nov 15, 2024

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

  • Ishan Flores· Nov 11, 2024

    tooluniverse-infectious-disease fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 52

1 / 6