tooluniverse-drug-repurposing

Identify and rank drug repurposing candidates using target, compound, and disease network analysis.

1.7k|254|Updated Mar 3, 2025
One-click install
npx skills add https://github.com/mims-harvard/ToolUniverse --skill tooluniverse-drug-repurposing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tooluniverse-drug-repurposing
Source: https://github.com/mims-harvard/ToolUniverse/tree/main/plugins/tooluniverse/skills/tooluniverse-drug-repurposing
Command: npx skills add https://github.com/mims-harvard/ToolUniverse --skill tooluniverse-drug-repurposing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tooluniverse.

What problem does it solve?

Finding new uses for existing drugs requires manually cross-referencing disease targets, drug databases, safety records, and literature across many disconnected sources. This Skill automates that multi-database workflow to generate and rank evidence-based repurposing hypotheses.

Core Features & Use Cases

  • Three Repurposing Strategies: Target-based (disease targets to drugs), compound-based (approved drugs to new indications), and disease-driven (disease to targets to existing drugs) workflows.
  • Multi-Database Integration: Queries OpenTargets, DrugBank, DGIdb, ChEMBL, PubChem, FDA, FAERS, PubMed, and ClinicalTrials.gov through ToolUniverse.
  • Scoring & Ranking Framework: Composite 0-100 viability score combining target association, safety profile, literature evidence, and drug properties, plus dose-feasibility checks against ChEMBL bioactivity data.
  • Use Case: Given an orphan disease, retrieve its genetically associated targets from OpenTargets, find approved drugs hitting those targets via DGIdb and DrugBank, screen FDA warnings and FAERS adverse events, then rank candidates by evidence score for clinical evaluation.

Quick Start

Use the drug repurposing skill to find approved drugs that could be repurposed for rheumatoid arthritis and rank them by evidence and safety.

Frequently Asked Questions about tooluniverse-drug-repurposing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find drug repurposing candidates for a disease?

Start with OpenTargets to get genetically associated targets for the disease, then query DGIdb and DrugBank for approved drugs hitting those targets. Score candidates on target association, safety profile, literature evidence, and drug properties using the 0-100 viability framework.

What databases does drug repurposing analysis require?

The workflow integrates OpenTargets for disease-target associations, DrugBank and DGIdb for drug-target interactions, ChEMBL for bioactivity data, FDA and FAERS for safety profiles, and PubMed plus ClinicalTrials.gov for evidence. All are accessed through the ToolUniverse SDK.

How do I check if a drug dose is feasible for a new target?

Compare the drug's IC50 or Ki values for the new target against its original target using ChEMBL bioactivity data. If the new target requires more than 10x the concentration achievable at approved doses, the candidate is unlikely to be clinically feasible.

Why does a disease lookup return no results in OpenTargets?

Disease lookups fail when using non-standard terminology or synonyms not in the EFO ontology. Try alternate disease names, broader disease categories, or query directly with a known EFO identifier instead of the disease name.

Can FAERS adverse event data be used to find repurposing opportunities?

Yes, adverse events can indicate therapeutic effects in different contexts, such as weight loss side effects suggesting obesity treatment potential. Query FAERS reaction counts by drug, then filter for approved drugs with acceptable serious-event rates.

What are the limitations of computational drug repurposing predictions?

Network proximity and target overlap alone do not establish efficacy; mechanism rationale and dose feasibility are required. Computational candidates need experimental validation, and existing clinical trial evidence should always be checked first before prioritizing predictions.