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

The canonical home for this skill is tooluniverse-drug-mechanism-research in mims-harvard/ToolUniverse

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-structured, highly actionable workflow: eight sequenced steps with executable tool calls, reasoning strategies, fallbacks, and an evidence hierarchy. The main gaps are a DailyMed parameter inconsistency in the comparison snippet, implicit rather than explicit validation checkpoints, and a modest opportunity to move the report template and tool catalog into reference files.

Suggestions

Fix the inconsistent DailyMed signature: the comparison snippet calls `DailyMed_parse_clinical_pharmacology(drug_name=...)` but Step 5 documents it as `operation` + `setid`; align one of them so both snippets are copy-paste executable.

Add explicit validation checkpoints between steps (e.g., "verify the ChEMBL ID resolved and matches the drug name before Step 2") to turn the implicit sequence into a checklist-style workflow.

Move the full report structure template and/or the complete tool-call catalog into a one-level-deep reference file to keep SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

The body is efficient and explicitly assumes Claude's pharmacology knowledge ("The LLM already knows drug pharmacology. This skill teaches HOW TO INVESTIGATE"). Each step pairs a short rationale with focused tool calls, and the reasoning strategies add non-obvious judgment rather than padding. It is not a 5 because of minor trimmable text — the investigation chain is restated in both the "Investigation Philosophy" section and Step 2's framing ("The first question: what does this drug bind to..."), and a few transitions are conversational. It is clearly above 3 since no section explains concepts Claude already knows.

4 / 5

Actionability

Nearly all guidance is concrete, executable tool invocations with realistic arguments (real ChEMBL IDs, gene symbols, setid two-step flow) plus response-parsing loops, a fallback table, and extracted key fields. It is not a 5 because of a signature inconsistency: the comparison section calls `DailyMed_parse_clinical_pharmacology(drug_name=drug[0])` while Step 5 documents the same tool as taking `operation` and `setid` parameters — one of these snippets would fail if copied. Still well above 3, since everything else is copy-paste ready rather than pseudocode.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with per-step purpose, code, and reasoning strategy, plus a consolidated fallback-strategies table and a known-issue note for a failing tool — good error-recovery guidance. It is not a 5 because validation checkpoints are implicit rather than explicit (e.g., no "confirm the ChEMBL ID resolved before proceeding" gate between Steps 1 and 2), and no tier-based evidence-reconciliation instructions for when sources conflict. This is a read-only research workflow, so the destructive/batch validation cap does not apply.

4 / 5

Progressive Disclosure

The skill is a single well-organized file with clear section headers per step, a comparison section, and a fallback table — easy to navigate. Since no bundle files exist, everything is inline, which is defensible for a workflow guide of this size, and each section is compact. It is not a 5 because a ~280-line file could offload some material (the full report template, the complete tool-call catalog) to one-level-deep reference files, which would keep SKILL.md a leaner overview.

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 answers what and when explicitly, uses concrete action language and natural trigger phrases, and names its data sources. The only improvements are adding a few more natural synonyms (e.g., pharmacodynamics, MOA) and sharpening the boundary against closely related pharmacology skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Trace drug mechanism of action — primary target → downstream signaling → pathway perturbation → tissue/organ effect → clinical outcome", "identifying off-target effects", "mechanism-based combination therapy design", and "writing mechanism sections of reports" — and names the data sources (DrugBank, ChEMBL, KEGG, Reactome, STRING). This matches the anchor for comprehensive, specific concrete actions. It is not a 4 because coverage spans the full trace chain plus three distinct use cases with no significant gaps.

5 / 5

Completeness

It explicitly answers both questions: the "what" is the target→pathway→outcome trace with named data sources, and the "when" is 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. This is a direct match for the top anchor; it is not a 4 because the when-clause is specific rather than generic.

5 / 5

Trigger Term Quality

Natural user phrasing is present: "mechanism of action", "how a drug works", "off-target effects", "combination therapy". These are phrases users would actually say, matching the good-coverage anchor. It falls short of 5 because common synonyms such as "pharmacodynamics", "drug targets", or the abbreviation "MOA" are absent from the description itself, leaving a few natural trigger terms missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — tracing drug mechanism of action through molecular targets and pathways — with distinct trigger phrases, so it is mostly distinguishable. However, "off-target effects" and "combination therapy design" overlap with sibling pharmacology skills (e.g., network pharmacology, adverse-event detection), which is minor overlap risk with closely related skills rather than the minimal-conflict profile of a 5.

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

plugins/tooluniverse/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.