Systematic analysis of drug-drug interactions with evidence-based risk scoring, mechanism identification, and clinical management recommendations.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontooluniverse-drug-drug-interactionExecute the skills CLI command in your project's root directory to begin installation:
Fetches tooluniverse-drug-drug-interaction from mims-harvard/tooluniverse and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate tooluniverse-drug-drug-interaction. Access via /tooluniverse-drug-drug-interaction in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
1.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
1.2K
stars
Systematic analysis of drug-drug interactions with evidence-based risk scoring, mechanism identification, and clinical management recommendations.
KEY PRINCIPLES:
Before querying any external database, consult the local reference script for instant answers on CYP/UGT roles and known critical interactions:
scripts/pharmacology_ref.py (no external dependencies, runs offline)
# Q927 pattern — valproate + lamotrigine:
python scripts/pharmacology_ref.py --type interaction --drug1 "valproate" --drug2 "lamotrigine"
# What does a drug do to UGT enzymes?
python scripts/pharmacology_ref.py --type ugt_inhibitor --drug "valproate"
# What enzymes metabolise a drug?
python scripts/pharmacology_ref.py --type ugt_substrate --drug "lamotrigine"
python scripts/pharmacology_ref.py --type cyp_substrate --drug "warfarin"
# Which drugs inhibit / induce a specific CYP?
python scripts/pharmacology_ref.py --type cyp_inhibitor --enzyme "CYP3A4"
python scripts/pharmacology_ref.py --type cyp_inducer --enzyme "CYP2C9"
# Narrow therapeutic index checklist:
python scripts/pharmacology_ref.py --type narrow_ti
# All known interactions for one drug:
python scripts/pharmacology_ref.py --type all_interactions --drug "lamotrigine"
Covered interactions include (severity / mechanism):
| Pair | Severity | Key mechanism |
|---|---|---|
| valproate + lamotrigine | Major | UGT1A4 inhibition → 2× lamotrigine levels + SJS risk |
| carbamazepine + lamotrigine | Major | UGT1A4 induction → 50% ↓ lamotrigine |
| oral contraceptives + lamotrigine | Major | UGT1A4 induction → 50% ↓ lamotrigine |
| valproate + phenytoin | Major | CYP2C9 inhibition + protein displacement |
| carbamazepine + valproate | Moderate | Epoxide hydrolase inhibition → toxic metabolite ↑ |
| simvastatin + ketoconazole | Contraindicated | CYP3A4 inhibition → rhabdomyolysis |
| simvastatin + clarithromycin | Contraindicated | CYP3A4 inhibition → rhabdomyolysis |
| rifampin + warfarin | Major | CYP2C9 induction → INR collapse |
| amiodarone + warfarin | Major | CYP2C9 inhibition → INR rise |
| clopidogrel + omeprazole | Moderate | CYP2C19 inhibition → reduced antiplatelet activation |
| quinidine + digoxin | Major | P-gp inhibition → 2× digoxin levels |
| lithium + NSAIDs | Major | Reduced renal clearance → lithium toxicity |
| fluoxetine + MAOIs | Contraindicated | Serotonin syndrome |
The script also covers UGT2B7 substrates (morphine, zidovudine) inhibited by valproate, UGT1A1 induction by rifampin, and the complete narrow therapeutic index list with monitoring parameters.
When uncertain about any scientific fact, SEARCH databases first (PubMed, UniProt, ChEMBL, ClinVar, etc.) rather than reasoning from memory. A database-verified answer is always more reliable than a guess.
When a patient develops NEW symptoms after starting a new medication, the FIRST question is: could the new drug be interacting with an existing medication? Specifically check: (1) Does the new drug inhibit metabolism of an existing drug? (2) Does the new drug have additive pharmacodynamic effects?
Apply when users:
Before querying any database, apply this reasoning framework to predict interactions mechanistically.
In every drug interaction, identify two roles:
For each drug pair, ask these questions in order:
Special case -- Prodrugs: If the victim is a prodrug that requires metabolic activation, inhibiting its activating enzyme reduces efficacy (not toxicity). Inducing its activating enzyme may increase efficacy or toxicity of the active metabolite.
Most DDI reasoning focuses on CYP450 (Phase I metabolism), but Phase II conjugation reactions — especially glucuronidation via UGT enzymes — cause some of the most dangerous drug interactions. These are frequently missed because agents default to CYP-centric reasoning.
Core principle: UGT enzymes (UGT1A4, UGT2B7, UGT1A1, etc.) conjugate drugs with glucuronic acid for renal elimination. When a UGT inhibitor is co-administered with a UGT substrate, the substrate accumulates because its primary elimination pathway is blocked.
The valproate + lamotrigine paradigm (IDX 927 pattern):
Other critical UGT interactions:
Reasoning algorithm for UGT interactions:
Use scripts/pharmacology_ref.py --type ugt_inhibitor --drug "[drug]" and --type ugt_substrate --drug "[drug]" for rapid UGT lookup.
When a patient is on 3+ drugs, interactions can cascade. A common pattern:
Scenario: Patient on Drug A (CYP3A4 substrate) + Drug B (CYP3A4 inducer) at steady state. Drug C (CYP3A4 inhibitor) is added.
Key reasoning principles for cascading effects:
When a patient on multiple medications develops an adverse drug reaction:
Example (IDX 927): Elderly patient on lamotrigine develops seizures and rash after adding valproate.
Use the temporal pattern of symptoms to narrow the mechanism:
For any suspected drug interaction, classify it by asking:
1. Is this pharmacokinetic? (One drug changes the LEVEL of another)
2. Is this pharmacodynamic? (Both drugs act on the SAME SYSTEM)
3. Is this pharmaceutical? (Drugs interact BEFORE reaching the body)
Most clinically significant interactions are pharmacokinetic, pharmacodynamic, or both simultaneously. Always consider mixed PK+PD interactions, which tend to be the most dangerous.
Assess severity by reasoning about the victim drug's properties, not by memorizing lists:
Therapeutic index determines risk tolerance:
Prodrug logic inverts the prediction:
Severity classification process:
Management follows directly from the mechanism:
DO NOT show intermediate tool outputs or search processes. Instead:
Create report file FIRST - Before any data collection:
DDI_risk_report_[DRUG1]_[DRUG2].md (or _polypharmacy.md for 3+)[Analyzing...] in each sectionApply clinical reasoning FIRST - Before running tools, reason through:
Progressively update - As database data is gathered:
[Analyzing...] with findingsFinal deliverable - Complete markdown report with recommendations
Query tools in this order:
ChEMBL_get_drug_mechanisms or KEGG_get_drug for CYP substrate/inhibitor/inducer datadrugbank_get_drug_interactions_by_drug_name_or_id for known transporter interactions (P-gp, OATP, OAT, OCT)Transporter interactions (check when CYP analysis incomplete):
DailyMed_get_spl_by_setid - highest evidence tierPubMed_search_articles - second tierRisk Score (0-100):
For each Major/Contraindicated interaction:
Before finalizing DDI report:
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Solid pick for teams standardizing on skills: tooluniverse-drug-drug-interaction is focused, and the summary matches what you get after install.
tooluniverse-drug-drug-interaction has been reliable in day-to-day use. Documentation quality is above average for community skills.
tooluniverse-drug-drug-interaction is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
tooluniverse-drug-drug-interaction fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend tooluniverse-drug-drug-interaction for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for tooluniverse-drug-drug-interaction matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: tooluniverse-drug-drug-interaction is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added tooluniverse-drug-drug-interaction from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in tooluniverse-drug-drug-interaction — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: tooluniverse-drug-drug-interaction is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 49