CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 investigation workflow with executable code and fallback strategies throughout. It is mostly concise and well-organized, though validation checkpoints between steps are implicit rather than explicit.

Suggestions

Add explicit validation/verification steps between major steps (e.g., confirm a non-empty target list before proceeding to off-target analysis) to strengthen the workflow's feedback loops.

Trim the Investigation Philosophy section to the essential chain, since the rest of the skill already demonstrates the approach concretely.

Consider extracting the per-tool API reference detail into a bundled reference file to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient and code-focused, explicitly assuming Claude's pharmacology knowledge ('The LLM already knows drug pharmacology'), though the Investigation Philosophy section and some prose could be trimmed slightly.

4 / 5

Actionability

Provides copy-paste ready, executable `tu.tools.*` calls with concrete parameters across all eight steps, plus a fallback-strategy table covering common failure cases.

5 / 5

Workflow Clarity

A clearly numbered 8-step sequence with fallback/error-recovery guidance and an evidence-hierarchy checklist, but lacks explicit output-validation checkpoints between steps.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and no bundle files; all content is appropriately inline for a workflow guide, with only minor organization gaps.

4 / 5

Total

17

/

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.

A strong, specific description that clearly states what the skill does and when to use it, with concrete action chains and named data sources. Trigger-term coverage is good but could include a few more natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in a chain ('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', giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (the trace chain and data sources) and 'when' ('Use for understanding how a drug works, identifying off-target effects...'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases like 'mechanism of action', 'how a drug works', and 'off-target effects', but a few common synonyms or phrasings users might say are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (drug mechanism tracing) with distinct triggers and named data sources, minimizing overlap with sibling pharmacology skills.

5 / 5

Total

19

/

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.

Validation15 / 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
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.