CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-drug-drug-interaction

Assess drug-drug interactions — CYP metabolic interactions (substrate/inhibitor/inducer), transporter (P-gp, BCRP, OATP) effects, pharmacodynamic synergy/antagonism, clinical significance scoring, and management recommendations. Use for polypharmacy review, prescribing decision support, and safety analysis when adding or switching drugs.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is highly actionable with a clear phased workflow and a real offline reference script, but it is verbose in explaining general pharmacology and inlines material that would be better split into reference files.

Suggestions

Trim general pharmacology exposition (perpetrator-victim basics, induction/inhibition timing, glucuronidation mechanics) to the non-obvious essentials to improve conciseness.

Move the full covered-interactions table and UGT tutorial into a references/ file, keeping only a short pointer and the highest-value example in SKILL.md.

Add an explicit validate-fix-retry checkpoint (e.g., re-run failed tool calls or re-grade evidence before finalizing) to the workflow to strengthen error recovery.

DimensionReasoningScore

Conciseness

The body is mostly efficient but spends substantial prose explaining general pharmacology Claude already knows (perpetrator-victim basics, induction/inhibition timing, glucuronidation mechanics), which could be tightened despite the genuinely non-obvious UGT1A4 core.

3 / 5

Actionability

Copy-paste-ready pharmacology_ref.py invocations with real flags, a concrete covered-interactions table, an explicit numeric risk-scoring formula, named external tools, and a precise report-file naming scheme make the guidance fully executable across common cases.

5 / 5

Workflow Clarity

A clear Phase 1-6 sequence, a MANDATORY report-first workflow, and a Success Criteria checklist provide most checkpoints, but there is no explicit validate-fix-retry error-recovery loop on the analysis itself.

4 / 5

Progressive Disclosure

The single bundle file (scripts/pharmacology_ref.py) is real and clearly referenced one level deep with well-organized sections, but the SKILL.md inlines reference-style material (full interaction table, UGT tutorial, severity prose) that could be split into separate files.

4 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and clearly scoped to drug-drug interaction analysis with explicit 'what' and 'when' guidance. It is near-exemplary, with only minor room for more trigger-term synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — CYP substrate/inhibitor/inducer assessment, transporter (P-gp/BCRP/OATP) effects, pharmacodynamic synergy/antagonism, clinical significance scoring, and management recommendations — giving comprehensive coverage rather than just 1-2 actions.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated assessment capabilities) and 'when' ('Use for polypharmacy review, prescribing decision support, and safety analysis when adding or switching drugs') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrases like 'polypharmacy review', 'prescribing decision support', 'safety analysis', and 'adding or switching drugs' are present, but a few common synonyms (e.g., 'medication interactions') are missing relative to the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

A clear specialized DDI-analysis niche with distinct triggers; unlikely to fire for unrelated skills, so conflict risk is minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mims-harvard/ToolUniverse
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.