Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Drug Interaction Screening

ASecurity

Screening for drug-drug interactions — mechanistic prediction, database checks, and clinical risk assessment.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgoapidatabase

Works with

cliapi

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill drug-interaction-screening --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Drug Interaction Screening?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Drug Interaction Screening
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-drug-interaction-screening/badge)](https://www.skillsdirectory.com/skills/aicodedecode-drug-interaction-screening)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: drug-interaction-screening
description: Screening for drug-drug interactions — mechanistic prediction, database checks, and clinical risk assessment.
category: scientific
---

## Overview

drug-interaction-screening covers the systematic identification and assessment of drug-drug
interactions (DDIs): pharmacokinetic mechanisms (CYPs, transporters), pharmacodynamic interactions
(additive effects, antagonism), database and literature checking, and translating interaction
data into clinical risk assessment. Polypharmacy makes this a daily necessity, not a specialty.

## When to use

- Medication review for polypharmacy patients: identifying clinically relevant DDIs.
- Mechanistic prediction: CYP/transporter-mediated PK interactions for new combinations.
- Checking resources: interaction databases, FDA labels, primary literature.
- Risk stratification: which interactions need action vs monitoring vs no concern.
- Designing DDI clinical studies (inhibitor/inducer trials).
- Building or evaluating interaction-checking tools.

## Core concepts

- **PK interaction mechanisms.** Absorption (chelation, pH, P-gp), distribution (protein-binding
  displacement — rarely clinically relevant alone), metabolism (CYP inhibition/induction),
  excretion (renal transporter inhibition). CYP-mediated interactions dominate clinical practice.
- **Key CYPs.** CYP3A4 (most drugs; inhibited by azoles, macrolides, grapefruit; induced by
  rifampin, carbamazepine, St. John's wort), CYP2D6 (polymorphic — poor vs ultrarapid
  metabolizers differ hugely), CYP2C9 (warfarin, phenytoin), CYP2C19 (clopidogrel activation —
  PPIs reduce it), CYP1A2 (induced by smoking). Know strong inhibitors/inducers of each.
- **Inhibition vs induction timing.** Inhibition starts/stops quickly (days); induction takes
  1-2 weeks to develop and to wash out (enzyme synthesis/degradation). Stopping an inducer
  causes drug levels to rise over weeks — a common missed interaction.
- **Transporters.** P-gp (digoxin, dabigatran — efflux inhibition raises levels), OATP1B1
  (statins), OCT2/MATE (metformin). Transporter interactions are underappreciated and
  increasingly in labels.
- **PD interactions.** Additive pharmacology: QT prolongation (multiple QT drugs), bleeding
  (anticoagulant + antiplatelet + NSAID), sedation (CNS depressants), serotonin syndrome
  (serotonergic combos), hypotension, hypoglycemia. These need no PK mechanism — combined
  effect is the interaction.
- **Clinical significance framework.** Severity (what happens: minor vs life-threatening) ×
  probability (how certain, how large the exposure change: AUC ratio ≥5 = strong) ×
  manageability (dose adjust? monitor? avoid?). Most database "interactions" are theoretical —
  triage ruthlessly.
- **Resources.** FDA labels (7. Drug Interactions sections), dedicated databases (check ≥2 —
  they disagree), primary literature for high-stakes decisions. Database severity ratings are
  inconsistent across tools — read the evidence, not just the red/yellow/green.
- **Patient factors.** Age, renal/hepatic function, pharmacogenomics (CYP2D6/2C19 status),
  and narrow-therapeutic-index drugs (warfarin, lithium, digoxin, immunosuppressants) amplify
  every interaction. The same DDI is trivial in one patient and dangerous in another.

## Practical workflow

1. **Reconcile.** Complete medication list including OTCs, herbals, supplements, PRNs, and
   recent changes — interactions hide in the unasked-about drugs.
2. **Screen.** Run through ≥1 interaction database; supplement with label checks for
   narrow-index drugs.
3. **Triage.** Severity × probability × manageability; focus on narrow-therapeutic-index drugs
   and high-risk combos (anticoagulants, QT drugs, CNS depressants, serotonergics).
4. **Assess mechanistically.** Is the mechanism plausible for this patient (dose, timing,
   inducer washout, genetics)? Check primary evidence for major decisions.
5. **Act.** Avoid/substitute, dose-adjust, separate administration times, or monitor
   (levels, ECG, symptoms) — with a documented plan and follow-up.
6. **Document and counsel.** Record the assessment and plan; tell the patient what to watch
   for.
7. **Reassess.** On every medication change — interactions are dynamic.

## Common pitfalls

- Alert fatigue: treating all database flags equally (most are noise).
- Missing inducer washout timing (weeks-long effects after stopping).
- Protein-binding displacement overcalled as clinically relevant.
- Herbal/OTC products omitted from screening (St. John's wort, grapefruit).
- PD interactions missed while hunting PK mechanisms.
- Single-database reliance (databases disagree substantially).
- No patient-specific risk stratification (same flag, different danger).
- Timing of interacting-drug initiation/stopping not factored into risk windows.
- Pharmacodynamic interactions in elderly patients underestimated (additive CNS effects).
- Renal/hepatic impairment amplifying a "moderate" interaction into a severe one.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →