tooluniverse-drug-research

14
0
Source

Generates comprehensive drug research reports with compound disambiguation, evidence grading, and mandatory completeness sections. Covers identity, chemistry, pharmacology, targets, clinical trials, safety, pharmacogenomics, and ADMET properties. Use when users ask about drugs, medications, therapeutics, or need drug profiling, safety assessment, or clinical development research.

Install

mkdir -p .claude/skills/tooluniverse-drug-research && curl -L -o skill.zip "https://mcp.directory/api/skills/download/1959" && unzip -o skill.zip -d .claude/skills/tooluniverse-drug-research && rm skill.zip

Installs to .claude/skills/tooluniverse-drug-research

About this skill

Drug Research Strategy

Comprehensive drug investigation using 50+ ToolUniverse tools across chemical databases, clinical trials, adverse events, pharmacogenomics, and literature.

KEY PRINCIPLES:

  1. Report-first approach - Create report file FIRST, then populate progressively
  2. Compound disambiguation FIRST - Resolve identifiers before research
  3. Citation requirements - Every fact must have inline source attribution
  4. Evidence grading - Grade claims by evidence strength (T1-T4)
  5. Mandatory completeness - All sections must exist, even if "data unavailable"
  6. English-first queries - Always use English drug/compound names in tool calls, even if the user writes in another language. Only try original-language terms as a fallback. Respond in the user's language

Workflow Overview

1. Report-First Approach (MANDATORY)

DO NOT show the search process or tool outputs to the user. Instead:

  1. Create the report file FIRST - [DRUG]_drug_report.md with all 11 section headers and [Researching...] placeholders. See REPORT_TEMPLATE.md for the full template.
  2. Progressively update the report - Replace placeholders with findings as you query each tool.
  3. Use ALL relevant tools - Query multiple databases for each data type; cross-reference across sources.

2. Citation Requirements (MANDATORY)

Every piece of information MUST include its source. Use inline citations:

*Source: PubChem via `PubChem_get_compound_properties_by_CID` (CID: 4091)*

3. Progressive Writing Workflow

Step 1:  Create report file with all section headers
Step 2:  Resolve compound identifiers -> Update Section 1
Step 3:  Query PubChem/ADMET-AI/DailyMed SPL -> Update Section 2 (Chemistry)
Step 4:  Query FDA Label MOA + ChEMBL + DGIdb -> Update Section 3 (Mechanism)
Step 5:  Query ADMET-AI tools -> Update Section 4 (ADMET)
Step 6:  Query ClinicalTrials.gov -> Update Section 5 (Clinical)
Step 7:  Query FAERS/DailyMed -> Update Section 6 (Safety)
Step 8:  Query PharmGKB -> Update Section 7 (Pharmacogenomics)
Step 9:  Query DailyMed/Orange Book -> Update Section 8 (Regulatory)
Step 10: Query PubMed/literature -> Update Section 9 (Literature)
Step 11: Synthesize findings -> Update Executive Summary & Section 10
Step 12: Document all sources -> Update Section 11 (Data Sources)

Compound Disambiguation (Phase 1)

CRITICAL: Establish compound identity before any research.

Identifier Resolution Chain

1. PubChem_get_CID_by_compound_name(compound_name)
   -> Extract: CID, canonical SMILES, formula

2. ChEMBL_search_compounds(query=drug_name)
   -> Extract: ChEMBL ID, pref_name

3. DailyMed_search_spls(drug_name)
   -> Extract: Set ID, NDC codes (if approved)

4. PharmGKB_search_drugs(query=drug_name)
   -> Extract: PharmGKB ID (PA...)

Handle Naming Ambiguity

IssueExampleResolution
Salt formsmetformin vs metformin HClNote all CIDs; use parent compound
Isomersomeprazole vs esomeprazoleVerify SMILES; separate entries if distinct
Prodrugsenalapril vs enalaprilatDocument both; note conversion
Brand confusionDifferent products same nameClarify with user

Research Paths Summary

Each path has detailed tool chains and output examples in REPORT_GUIDELINES.md.

PATH 1: Chemical Properties & CMC

Tools: PubChem properties -> ADMET-AI physicochemical -> ADMET-AI solubility -> DailyMed chemistry/description Output: Physicochemical table, Lipinski assessment, QED score, salt forms, formulation comparison

PATH 2: Mechanism & Targets

Tools: DailyMed MOA -> ChEMBL activities (NOT ChEMBL_get_molecule_targets) -> ChEMBL target details -> DGIdb -> PubChem bioactivity Critical: Derive targets from activities filtered to pChEMBL >= 6.0. Avoid ChEMBL_get_molecule_targets. Output: FDA MOA text, target table with UniProt/potency, selectivity profile

PATH 3: ADMET Properties

Tools: ADMET-AI (bioavailability, BBB, CYP, clearance, toxicity) Fallback: DailyMed clinical_pharmacology + pharmacokinetics + drug_interactions Critical: If ADMET-AI fails, automatically use fallback. Never leave Section 4 empty.

PATH 4: Clinical Trials

Tools: search_clinical_trials -> compute phase counts -> extract outcomes/AEs -> fda_pharmacogenomic_biomarkers Critical: Section 5.2 must show actual counts by phase/status in table format.

PATH 5: Post-Marketing Safety

Tools: FAERS (reactions, seriousness, outcomes, deaths, age) + DailyMed (DDI, dosing, warnings) Critical: Include FAERS date window, seriousness breakdown, and limitations paragraph.

PATH 6: Pharmacogenomics

Tools: PharmGKB (search -> details -> annotations -> guidelines) Fallback: DailyMed pharmacogenomics section + PubMed literature

PATH 7: Regulatory & Patents

Tools: FDA Orange Book (search, approval history, exclusivity, patents, generics) + DailyMed (special populations via LOINC codes) Note: US-only data; document EMA/PMDA limitation.

PATH 8: Real-World Evidence

Tools: ClinicalTrials.gov (OBSERVATIONAL studies) + PubMed (real-world, registry, surveillance)

PATH 9: Comparative Analysis

Tools: Abbreviated tool chains for each comparator + head-to-head trial search + PubMed meta-analyses


FDA Label Core Fields

For approved drugs, retrieve these DailyMed sections early (after getting set_id):

BatchSectionsMaps to Report
Phase 1mechanism_of_action, pharmacodynamics, chemistrySections 2-3
Phase 2clinical_pharmacology, pharmacokinetics, drug_interactionsSections 4, 6.5
Phase 3warnings_and_cautions, adverse_reactions, dosage_and_administrationSections 6, 8.2
Phase 4pharmacogenomics, clinical_studies, description, inactive_ingredientsSections 5, 7

Fallback Chains

Primary ToolFallbackUse When
PubChem_get_CID_by_compound_nameChEMBL_search_compoundsName not in PubChem
ChEMBL_get_molecule_targetsUse ChEMBL_search_activities insteadAlways avoid this tool
ChEMBL_get_bioactivity_by_chemblidPubChem_get_bioactivity_summary_by_CIDNo ChEMBL ID
DailyMed_search_splsPubChem_get_drug_label_info_by_CIDDailyMed timeout
PharmGKB_search_drugsDailyMed PGx sections + PubMedPharmGKB unavailable
PharmGKB_get_dosing_guidelinesDailyMed pharmacogenomics sectionPharmGKB API error
FAERS_count_reactions_by_drug_eventDocument "FAERS unavailable" + use label AEsAPI error
ADMETAI_* (all tools)DailyMed clinical_pharmacology + pharmacokineticsInvalid SMILES or API error

Quick Reference: Tools by Use Case

Use CasePrimary ToolFallbackEvidence
Name -> CIDPubChem_get_CID_by_compound_nameChEMBL_search_compoundsT1
PropertiesPubChem_get_compound_properties_by_CIDADMET-AI physicochemicalT1/T2
FDA MOADailyMed_get_spl_sections_by_setid (mechanism_of_action)-T1
TargetsChEMBL_search_activities -> ChEMBL_get_targetDGIdb_get_drug_infoT1
ADMETADMETAI_predict_* (5 tools)DailyMed PK sectionsT2/T1
Trialssearch_clinical_trials-T1
Trial outcomesextract_clinical_trial_outcomes-T1
FAERSFAERS_count_reactions_by_drug_eventLabel adverse_reactionsT1
Dose modsDailyMed_get_spl_sections_by_setid (dosage, warnings)-T1
PGxPharmGKB_search_drugsDailyMed PGx + PubMedT2/T1
LabelDailyMed_search_splsPubChem_get_drug_label_info_by_CIDT1
LiteraturePubMed_search_articlesEuropePMC_search_articlesVaries
RegulatoryFDA_OrangeBook_* toolsDailyMed label dataT1

See TOOLS_REFERENCE.md for the complete tool listing with parameters and input format requirements.


Type Normalization

Many tools require string inputs. Always convert IDs before API calls:

  • ChEMBL IDs, PubMed IDs, NCT IDs: convert int -> str
  • SMILES for ADMET-AI: pass as list ["SMILES_STRING"]
  • FAERS drug names: use UPPERCASE (e.g., "METFORMIN")
  • ChEMBL IDs: full format "CHEMBL1431" not "1431"
  • PharmGKB IDs: PA prefix "PA450657" not "450657"

Common Use Cases

Use CasePrimary SectionsLight Sections
Approved Drug ProfileAll 11 sectionsNone
Investigational Compound1, 2, 3, 4, 95, 6, 7, 8
Safety Review1, 5, 6, 7, 92, 3, 4, 8
ADMET Assessment1, 2, 43, 5, 6, 7, 8, 9
Clinical Development Landscape1, 5, 92, 3, 4, 6, 7, 8

Always maintain all section headers but adjust depth based on query focus and data availability.


When NOT to Use This Skill

  • Target research -> Use target-intelligence-gatherer skill
  • Disease research -> Use disease-research skill
  • Literature-only -> Use literature-deep-research skill
  • Single property lookup -> Call tool directly
  • Structure similarity search -> Use PubChem_search_compounds_by_similarity directly

Additional Resources

  • Report template: REPORT_TEMPLATE.md - Initial file template, citation format, evidence grading, scorecard, audit template
  • Report guidelines: REPORT_GUIDELINES.md - Detailed section-by-section instructions with output examples
  • Tool reference: TOOLS_REFERENCE.md - Complete tool listing with parameters and input formats
  • Verification checklist: CHECKLIST.md - Section-by-section pre-delivery verification
  • Examples: EXAMPLES.md - Detailed workflow examples for different use cases

More by mims-harvard

View all →

tooluniverse-precision-oncology

mims-harvard

Provide actionable treatment recommendations for cancer patients based on molecular profile. Interprets tumor mutations, identifies FDA-approved therapies, finds resistance mechanisms, matches clinical trials. Use when oncologist asks about treatment options for specific mutations (EGFR, KRAS, BRAF, etc.), therapy resistance, or clinical trial eligibility.

150

devtu-fix-tool

mims-harvard

Fix failing ToolUniverse tools by diagnosing test failures, identifying root causes, implementing fixes, and validating solutions. Use when ToolUniverse tools fail tests, return errors, have schema validation issues, or when asked to debug or fix tools in the ToolUniverse framework.

40

tooluniverse-binder-discovery

mims-harvard

Discover novel small molecule binders for protein targets using structure-based and ligand-based approaches. Creates actionable reports with candidate compounds, ADMET profiles, and synthesis feasibility. Use when users ask to find small molecules for a target, identify novel binders, perform virtual screening, or need hit-to-lead compound identification.

30

tooluniverse-chemical-compound-retrieval

mims-harvard

Retrieves chemical compound information from PubChem and ChEMBL with disambiguation, cross-referencing, and quality assessment. Creates comprehensive compound profiles with identifiers, properties, bioactivity, and drug information. Use when users need chemical data, drug information, or mention PubChem CID, ChEMBL ID, SMILES, InChI, or compound names.

20

tooluniverse-pharmacovigilance

mims-harvard

Analyze drug safety signals from FDA adverse event reports, label warnings, and pharmacogenomic data. Calculates disproportionality measures (PRR, ROR), identifies serious adverse events, assesses pharmacogenomic risk variants. Use when asked about drug safety, adverse events, post-market surveillance, or risk-benefit assessment.

160

tooluniverse-rare-disease-diagnosis

mims-harvard

Provide differential diagnosis for patients with suspected rare diseases based on phenotype and genetic data. Matches symptoms to HPO terms, identifies candidate diseases from Orphanet/OMIM, prioritizes genes for testing, interprets variants of uncertain significance. Use when clinician asks about rare disease diagnosis, unexplained phenotypes, or genetic testing interpretation.

20

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

289790

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

213415

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

213296

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

219234

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

172200

rust-coding-skill

UtakataKyosui

Guides Claude in writing idiomatic, efficient, well-structured Rust code using proper data modeling, traits, impl organization, macros, and build-speed best practices.

166173

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.