CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-drug-mechanism-research

Trace drug mechanism of action — primary target → downstream signaling → pathway perturbation → tissue/organ effect → clinical outcome. Uses DrugBank, ChEMBL, KEGG, Reactome, STRING. Use for understanding how a drug works, identifying off-target effects, mechanism-based combination therapy design, and writing mechanism sections of reports.

Quality

84%

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.

A well-constructed investigation workflow: every step has executable tool calls with response parsing, reasoning strategies for interpretation, and fallback paths. The main deductions are a non-executable snippet in the comparison section, a few sentences restating known pharmacology, and the absence of explicit validation checkpoints.

Suggestions

Fix the 'Comparing Two Drugs' snippet: DailyMed_parse_clinical_pharmacology(drug_name=drug[0]) contradicts Step 5's two-step setid process — show the setid resolution or use a tool signature that actually accepts a drug name.

Trim step-intro sentences that restate pharmacology Claude already knows (e.g. 'Most drugs bind more than one target at clinical concentrations', 'Pharmacogenomic variants affect how a patient responds to the drug') to raise conciseness.

Add explicit validation checkpoints between steps (e.g. confirm the ChEMBL ID resolved and the primary target was identified before proceeding to pathway mapping) to strengthen workflow clarity.

Remove DrugBank from the frontmatter description (or add its usage) — the body uses ChEMBL, KEGG, Reactome, STRING, OpenTargets, DailyMed, CPIC, PharmGKB, and PubMed/EuropePMC, but DrugBank never appears.

DimensionReasoningScore

Conciseness

The body is dense with earning content — executable tu.tools calls, response-parsing loops, reasoning strategies, and a fallback table — and explicitly disclaims teaching known pharmacology ('The LLM already knows drug pharmacology. This skill teaches HOW TO INVESTIGATE'). However, several step intros restate knowledge Claude already has, e.g. 'Most drugs bind more than one target at clinical concentrations' and 'Pharmacogenomic variants affect how a patient responds to the drug', fitting 'Efficient; minor instances of over-explanation that could be trimmed' (4) rather than 5's every-token-earns-its-place.

4 / 5

Actionability

Nearly all guidance is copy-paste-ready with concrete function names, parameters, and parsing of real response shapes (e.g. moa["data"]["drug"]["mechanismsOfAction"]["rows"]). One real gap: the 'Comparing Two Drugs' snippet calls DailyMed_parse_clinical_pharmacology(drug_name=drug[0]), contradicting Step 5's documented two-step setid-based signature, so it is not executable as written. This fits anchor 4 ('concrete code or commands with minor gaps') rather than 5.

4 / 5

Workflow Clarity

A clear 8-step sequence (resolve drug → target → off-target → pathway → label → PGx → literature → integrate) with per-step fallbacks, a consolidated fallback strategies table, and documented known issues ('OpenTargets_get_associated_targets_by_drug_chemblId may fail'). Checkpoints are implicit rather than explicit — there is no 'verify the ChEMBL ID resolved before proceeding' style validation — so it matches anchor 4 ('Clear sequence with most checkpoints present; minor validation gaps') rather than 5. The destructive/batch cap does not apply since this is a read-only investigation workflow.

4 / 5

Progressive Disclosure

No bundle files (references/, scripts/, assets/) exist, so this is a standalone skill; structure is good with numbered step sections, a consistent format, an evidence hierarchy, a report template, and a fallback table. The per-step code is integral to the workflow rather than a separable API reference, fitting anchor 4 ('Good structure; most content is appropriately placed; minor organization gaps') rather than 3, though at ~280 lines a references/ split of tool API details could improve it.

4 / 5

Total

16

/

20

Passed

Description

88%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.

A strong description: it states a concrete investigation pipeline, names its data sources, and provides an explicit 'Use for...' clause covering four distinct trigger scenarios. The only weaknesses are a few missing natural trigger synonyms and minor overlap with adjacent pharmacology skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities: 'Trace drug mechanism of action — primary target → downstream signaling → pathway perturbation → tissue/organ effect → clinical outcome', plus 'identifying off-target effects, mechanism-based combination therapy design, and writing mechanism sections of reports', and names the concrete data sources used (ChEMBL, KEGG, Reactome, STRING). This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' rather than 4, since no meaningful capability gap remains.

5 / 5

Completeness

It explicitly answers 'what' (trace MOA through the target→pathway→organ→outcome chain using named databases) and 'when' via an explicit 'Use for understanding how a drug works, identifying off-target effects, mechanism-based combination therapy design, and writing mechanism sections of reports' clause with concrete trigger scenarios. Both what and when are clearly and explicitly present, matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural user phrases are present: 'mechanism of action', 'understanding how a drug works', 'off-target effects'. However, common variations a user would naturally say are missing from the description itself — 'pharmacology', 'drug target', 'MOA', 'pharmacodynamics' — so it fits 'Good keyword coverage; a few natural terms missing' (4) rather than the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (mechanism-of-action tracing), but the description's inclusion of 'identifying off-target effects' and 'mechanism-based combination therapy design' overlaps with sibling skills such as adverse-event detection and network pharmacology. It fits 'Mostly distinct; minor overlap risk with closely related skills' (4) rather than 5's minimal conflict risk.

4 / 5

Total

18

/

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

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-drug-mechanism-research/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.