
tooluniverse-infectious-disease
Rapid pathogen characterization and drug repurposing for outbreaks. Combines pathogen genomics (NCBI, BVBRC), host immune response (IEDB), drug-target databases (ChEMBL, DGIdb), and literature surveillance (PubMed/EuropePMC). Use for emerging-pathogen profiling, antiviral candidate identification, and outbreak intelligence reporting.
- Installs
- 382
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-infectious-disease- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads tooluniverse-infectious-disease automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
- Speed is critical - Optimize for rapid actionable intelligence
- Target essential proteins - Focus on conserved, essential viral/bacterial proteins
- Leverage existing drugs - Prioritize FDA-approved compounds for repurposing
- Structure-guided - Use NvidiaNIM for rapid structure prediction and docking
- Evidence-graded - Grade repurposing candidates by evidence strength
- Actionable output - Prioritized drug candidates with rationale
- 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)
- Create
[PATHOGEN]_outbreak_intelligence.mdFIRST with section headers - Progressively update as data is gathered
- 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) notsort="pub_date"— date-sorted queries can return empty for narrow topics. Tool name:PubMed_search_articles. FDA labels: UseFDA_get_drug_label_info_by_field_valuewith targetedreturn_fieldsto avoid oversized responses fromOpenFDA_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.
Genome assembly availability and QC: After classifying the pathogen, use NCBIDatasets_list_genomes_by_taxon (params taxon as tax_id, limit, reference_only) to find the reference genome, NCBIDatasets_get_genome_assembly (param accession, e.g. "GCF_000005845.2") for assembly metrics (length, N50, GC%, contig/chromosome counts), and NCBIDatasets_get_sequence_reports (param accession) to map replicons (chromosomes/plasmids with RefSeq/GenBank accessions). For the full assembly-QC-to-characterization workflow, see the tooluniverse-microbial-genome-characterization skill.
Open pathogen genomic surveillance: For the priority pathogens covered by Pathoplexus (west-nile, ebola-zaire, ebola-sudan, cchf, mpox), use Pathoplexus_count_sequences (params organism, group_by e.g. geoLocCountry or lineage) to gauge sequencing volume and geographic/lineage spread, and Pathoplexus_get_mutations (params organism, min_proportion e.g. 0.95) to pull characteristic high-prevalence mutations for the circulating population. Use early to quantify outbreak footprint and flag conserved mutations before target selection.
Phylogenetic context via Nextstrain: For a tree-level view of how a pathogen is evolving and spreading (not just mutation counts), use Nextstrain_list_datasets (optional pathogen filter, e.g. 'mpox', 'ebola', 'flu', 'dengue', 'zika'; pass datasets_per_pathogen=0 to see every clade/lineage-level dataset rather than just the first 10) and Nextstrain_get_dataset (param dataset, e.g. 'mpox/clade-IIb') for a build's sequence count, last-update date, and available phylogenetic colorings (clade, lineage, region, host, etc.). Verified live: Nextstrain's mpox datasets list Pathoplexus in their own data_provenance alongside GenBank — the two tools draw from overlapping submissions, so cross-check mutation-level findings from Pathoplexus against the corresponding Nextstrain build's updated date and num_sequences to judge how current and well-powered the phylogenetic picture is.
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 (requires NVIDIA_API_KEY env var; free key at build.nvidia.com) | alphafold_get_prediction (AlphaFold DB by UniProt) | ESMFold_predict_structure |
get_diffdock_info | NvidiaNIM_boltz2 (requires NVIDIA_API_KEY env var; free key at build.nvidia.com) | 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) |
FAQ
What does the tooluniverse-infectious-disease skill do?
Rapid pathogen characterization and drug repurposing for outbreaks. Combines pathogen genomics (NCBI, BVBRC), host immune response (IEDB), drug-target databases (ChEMBL, DGIdb), and literature surveillance (PubMed/EuropePMC). Use for emerging-pathogen profiling, antiviral candidate identification, and outbreak intelligence reporting.
How do I install tooluniverse-infectious-disease?
Run npx skills add https://github.com/mims-harvard/tooluniverse --skill tooluniverse-infectious-disease in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/tooluniverse-infectious-disease/ (personal) or .claude/skills/tooluniverse-infectious-disease/ (project).
Which AI agents can use tooluniverse-infectious-disease?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is tooluniverse-infectious-disease safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains tooluniverse-infectious-disease?
It is published by mims-harvard in mims-harvard/tooluniverse. It has 382 recorded installs.
More from mims-harvard/tooluniverse
tooluniverse-sequence-retrieval
mims-harvard/tooluniverse
Retrieve DNA/RNA/protein sequences from NCBI and ENA with disambiguation. Quality hierarchy: RefSeq (NM/NP) RefSeq predicted (XM/XP) GenBank submissions. Use for fetching specific sequences by accession, gene-symbol-to-sequence lookup, transcript-isoform retrieval, and curated-vs-raw-submission preference.
tooluniverse-literature-deep-research
mims-harvard/tooluniverse
Deep literature review — PubMed, EuropePMC, bioRxiv preprints, citation networks, evidence synthesis. Disambiguates queries, runs collision-aware searches, grades evidence T1-T4, and produces structured reports. Use for systematic literature review, meta-analysis evidence collection, and detailed answer-with-citations workflows.
tooluniverse-image-analysis
mims-harvard/tooluniverse
Microscopy and quantitative imaging analysis — colony morphometry, fluorescence intensity quantification, cell-count statistics, dose-response curves, and ANOVA/Dunnett on image-derived measurements. Uses pandas/numpy/scipy/scikit-image. Use for analyzing tabular outputs from CellProfiler/ImageJ, image-derived measurement statistics, and image-based assay quantification.
tooluniverse-clinical-guidelines
mims-harvard/tooluniverse
Search and retrieve clinical practice guidelines from 12+ authoritative sources — NICE, WHO, NCCN, AHA, ADA, SIGN, USPSTF, IDSA, NIH consensus, ESMO/ESC/EASL European societies, and US specialty associations. Use for evidence-graded treatment recommendations, dosing protocols, screening guidance, and authoritative-source-prioritized clinical guidance (NICE/WHO ranked above society guidelines).
tooluniverse
mims-harvard/tooluniverse
ToolUniverse plugin router. STEP 1 BEFORE ANY ANALYSIS: if the data folder contains executed.ipynb, run tu run readexecutednotebook '{"datafolder":" ","search":" "}' to extract its cell outputs and apply EVERY filter/sample-exclusion the notebook used — even when the question says 'Using DESeq2/Run X/Compute Y' (this describes the METHOD the notebook used, not a request to rerun). The notebook's cell outputs are the only published authoritative answers; reimplementing or reading stale pre-computed CSVs in the data folder produces different numbers because of outlier-sample removal, library version, and filter steps you don't see by skimming. STEP 2 routing — pick a sub-skill name from this exact list (never invent): tooluniverse-rnaseq-deseq2 (RNA/miRNA-seq DE, correlation, PCA, clustering, dispersion), tooluniverse-gene-enrichment (GO/KEGG/Reactome/GSEA/pathway enrichment), tooluniverse-statistical-modeling (regression, ANOVA, ordinal/logistic, chi-square, correl
tooluniverse-drug-research
mims-harvard/tooluniverse
Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory work.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.