CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

drug-interaction-checker

Check for interactions between multiple medications, including severity classification and mechanism explanations.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/drug-interaction-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 contains a solid executable core (CLI commands, parameters, output schema, real one-level-deep references) but is wrapped in substantial generated-feeling boilerplate: duplicated sections, dangling "See above" cross-references, and generic checklists that consume context without adding skill-specific value. Trimming to the drug-interaction specifics would roughly halve its length while preserving everything actionable. The workflow and usage sections need consolidation into one concrete, validated sequence.

Suggestions

Merge the duplicate sections: combine "Example Usage" + "Usage", and "Quick Check" + "Audit-Ready Commands" (both run py_compile), and collapse Workflow/Implementation Details/run plan into a single concrete sequence; remove the dangling "See `## X` above" filler lines.

Drop or move generic boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Response Template) out of SKILL.md into a reference file or delete it — none of it is specific to drug interaction checking.

Fix the example to use a real invocation from the skill's directory (drop the fabricated `cd "20260318/scientific-skills/..."` path) and add a validation checkpoint comparing script output against the documented JSON schema.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with several padded or duplicated sections: Usage appears twice ("## Example Usage" and "## Usage"), py_compile is repeated in both "## Quick Check" and "## Audit-Ready Commands", workflow guidance is spread across "## Workflow", "## Implementation Details", and the example run plan, and generic boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) adds no skill-specific value. Dangling filler like "See `## Features` above for related details" appears repeatedly. Not a 1 because the core reference content (severity table, parameters, output format) is genuinely useful and not concept-explanation padding.

2 / 5

Actionability

Concrete executable guidance dominates: `python scripts/main.py --drugs "Warfarin" "Aspirin" "Ibuprofen"`, a module import example, a full parameters table, and a complete output JSON schema. Minor gaps keep it below 5: the example usage opens with a bogus `cd "20260318/scientific-skills/..."` path that won't exist in a user's workspace, and "Edit the in-file CONFIG block" refers to a block the skill does not actually document.

4 / 5

Workflow Clarity

A five-step workflow exists with an explicit fallback path and error-handling rules, but the steps are abstract ("Confirm the user objective", "Use the packaged script path") rather than concrete drug-checking steps, and they compete with two other workflow-ish sections. Validation is limited to `py_compile` with no verification of actual output correctness. This matches 'steps listed but validation gaps' better than the mostly-checkpointed anchor 4.

3 / 5

Progressive Disclosure

Referenced bundle files are real and one level deep: `references/interactions_db.json`, `references/severity_criteria.md`, and `references/cyp450_substrates.json` all exist and are clearly listed in the References and Data Sources sections. Not 5 because the inline severity table duplicates content that belongs in `severity_criteria.md`, and the duplicated sections dilute navigation.

4 / 5

Total

13

/

20

Passed

Description

58%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 concrete and domain-specific but one-sided: it states what the skill does without any 'Use when' trigger guidance, so Claude may not reliably select it at the right moments. Adding a trigger clause with natural terms like 'drug interactions' or 'medication safety check' would raise both completeness and trigger quality. It is grammatically clean and appropriately concise.

Suggestions

Append a trigger clause such as: "Use when the user mentions drug interactions, medication combinations, mixing medicines, or needs a medication safety check."

Include the natural keyword 'drug' (e.g., 'drug-drug interactions') since that is the phrase users and clinicians most often say.

Optionally mention the clinical guidance/management output to round out the capability list.

DimensionReasoningScore

Specificity

"Check for interactions between multiple medications, including severity classification and mechanism explanations" names the domain plus three concrete actions (multi-drug interaction checking, severity classification, mechanism explanations), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because it omits clinical management recommendations and output formats that the skill actually supports.

4 / 5

Completeness

The description clearly answers 'what' but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete and multi-part, not vague.

3 / 5

Trigger Term Quality

Terms like "interactions", "medications", and "severity" are relevant, but the most natural user phrase "drug interactions" / "medication interactions" never appears and there are no synonyms or trigger phrasing variations. Better than 2 (keywords exist and are domain-specific rather than generic), but not the good coverage of 4.

3 / 5

Distinctiveness Conflict Risk

"interactions between multiple medications" carves out a clear clinical niche with minimal overlap risk against generic data/document skills. Not 5 because without explicit trigger phrases it could marginally overlap with other medical/pharmacology skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/drug-interaction-checker/SKILL.md

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.