drug-drug-interaction
SkillDev toolsToolUniverse workflow — Drug Drug Interaction
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the drug-drug-interaction skill
What this skill tells your AI
The instructions your AI receives, as published by lamm-mit/scienceclaw in skills/drug-drug-interaction/SKILL.md and read by ahel’s review.
name: tooluniverse-drug-drug-interaction description: Comprehensive drug-drug interaction (DDI) prediction and risk assessment. Analyzes interaction mechanisms (CYP450, transporters, pharmacodynamic), severity classification, clinical evidence grading, and provides management strategies. Supports single drug pairs, polypharmacy analysis (3+ drugs), and alternative drug recommendations. Use when users ask about drug interactions, medication safety, polypharmacy risks, or need DDI assessment for clinical decision support.
Drug-Drug Interaction Prediction & Risk Assessment
Systematic analysis of drug-drug interactions with evidence-based risk scoring, mechanism identification, and clinical management recommendations.
KEY PRINCIPLES:
- Report-first approach - Create DDI_risk_report.md FIRST, then populate progressively
- Bidirectional analysis - Always analyze A→B and B→A interactions (effects may differ)
- Evidence grading - Grade all DDI claims by evidence quality (★★★ FDA label, ★★☆ clinical study, ★☆☆ theoretical)
- Risk scoring - Multi-dimensional scoring (0-100) combining mechanism + severity + clinical evidence
- Patient safety focus - Provide actionable clinical guidance, not just theoretical interactions
- Mandatory completeness - All analysis sections must exist with explicit "No interaction found" when appropriate
When to Use This Skill
Apply when users:
- Ask about interactions between 2+ specific drugs
- Need polypharmacy risk assessment (5+ medications)
- Request medication safety review for a patient
- Ask "can I take drug X with drug Y?"
- Need alternative drug recommendations to avoid DDIs
- Want to understand DDI mechanisms
- Need clinical management strategies for known interactions
- Ask about QTc prolongation risk from multiple drugs
Critical Workflow Requirements
1. Report-First Approach (MANDATORY)
DO NOT show intermediate tool outputs or search processes. Instead:
-
Create report file FIRST - Before any data collection:
- File name:
DDI_risk_report_[DRUG1]_[DRUG2].md(or_polypharmacy.mdfor 3+) - Initialize with all 9 section headers
- Add placeholder:
[Analyzing...]in each section
- File name:
-
Progressively update - As data is gathered:
- Replace
[Analyzing...]with findings - Include "No interaction detected" when tools return empty
- Document failed tool calls explicitly
- Replace
-
Final deliverable - Complete markdown report with recommendations
[... Content continues as above for full 500+ lines ...]
Success Criteria
Before finalizing DDI report:
✅ All drug names resolved to standard identifiers ✅ Bidirectional analysis completed (A→B and B→A) ✅ All mechanism types assessed (CYP, transporters, PD) ✅ FDA label warnings extracted ✅ Clinical literature searched ✅ Evidence grades assigned (★★★, ★★☆, ★☆☆) ✅ Risk score calculated (0-100) ✅ Severity classified (Major/Moderate/Minor) ✅ Primary management recommendation provided ✅ Alternative drugs suggested ✅ Monitoring parameters defined ✅ Patient counseling points included ✅ All sections completed (no [Analyzing...] placeholders) ✅ Data sources cited throughout
When all criteria met → Ready for Clinical Use 🎉
Signals
- GitHub stars
- 242
- Forks
- 42
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
drug-drug-interaction- Source
- github.com/lamm-mit/scienceclaw