CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-drug-research

Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory work.

Quality

81%

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-research in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 operations manual with concrete tool chains, fallback logic, and a clear sequenced workflow. Its weaknesses are padded prose sections that assume less competence than the rest of the document, and a progressive-disclosure scheme whose five referenced files are all missing from the bundle.

Suggestions

Trim the long inline 'live-verified' prose paragraphs (DrugCentral, NIH DSLD) down to the tool name, purpose, and a one-line example; move detailed example outputs into a reference file.

Add an explicit final validation step inside the 12-step workflow (e.g., 'Step 13: run the CHECKLIST.md verification before delivering the report') instead of deferring verification entirely to an external file.

Ship the referenced bundle files (REPORT_TEMPLATE.md, REPORT_GUIDELINES.md, TOOLS_REFERENCE.md, CHECKLIST.md, EXAMPLES.md) in the skill directory or inline the minimal needed content — all five links are currently broken in the provided bundle.

Cut the 'LOOK UP, DON'T GUESS' exhortation and the generic target→pathway→phenotype mechanism reasoning chain; keep only skill-specific lookup rules.

DimensionReasoningScore

Conciseness

The body is mostly efficient — dense tables, tool chains, and fallback mappings that carry real non-obvious operational knowledge — but includes content that could be tightened: the ~120-word DrugCentral paragraph and ~140-word NIH DSLD paragraph each embed 'live-verified' example outputs inline, the 'LOOK UP, DON'T GUESS' section is exhortation ('your first instinct should be to SEARCH for it'), and the 5-level 'Drug Mechanism Reasoning' causal chain (target → pathway → phenotype → outcome) restates pharmacology Claude already knows. It is not a 4 because these padded sections are more than minor trimmable instances; not a 2 because the bulk of the document is genuinely lean, high-signal reference material.

3 / 5

Actionability

Guidance is concrete and near-executable: exact tool chains with parameter names ('PubChem_get_CID_by_compound_name(compound_name)'), explicit type-normalization rules ('full format "CHEMBL1431" not "1431"', 'FAERS drug names: use UPPERCASE', 'SMILES ... pass as list'), a ready-to-copy inline citation format, and per-failure fallback tables. It is not a 5 because full parameter and input-format details are deferred to TOOLS_REFERENCE.md, which is not present in the bundle, leaving some calls not fully specified from the body alone.

4 / 5

Workflow Clarity

The 12-step Progressive Writing Workflow sequences every step to a specific report section, the Compound Disambiguation chain orders identifier resolution before research, and the fallback chains function as explicit error-recovery loops ('If ADMET-AI fails, automatically use fallback. Never leave Section 4 empty.'). It is not a 5 because final verification is delegated entirely to CHECKLIST.md (absent from the bundle) rather than an inline validate-before-deliver checkpoint; not a 3 because sequencing and most checkpoints (mandatory placeholders, fallback triggers) are explicit.

4 / 5

Progressive Disclosure

The SKILL.md itself is well organized with clearly signaled, one-level-deep references ('See [REPORT_TEMPLATE.md](REPORT_TEMPLATE.md)', a dedicated 'Additional Resources' section listing REPORT_TEMPLATE.md, REPORT_GUIDELINES.md, TOOLS_REFERENCE.md, CHECKLIST.md, EXAMPLES.md). However, none of these five referenced files exist in the provided bundle (no references/, scripts/, or assets/ directories), so every link is broken, and long inline prose (the DrugCentral and NIH DSLD 'live-verified' paragraphs) is content that belongs in those reference files. Not a 2 because the overview structure and reference signaling are prominent and well-designed; not a 4 because the actual bundle structure does not deliver the referenced files.

3 / 5

Total

14

/

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 description: concrete and comprehensive on capabilities, with an explicit 'Use for...' clause containing natural conversational trigger phrases. The only gap is missing common synonyms ('medication', 'side effects') that lay users might say.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capability areas — "mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history" — giving comprehensive, specific coverage of the drug-profiling domain. It is not a 4 because the enumerated scope spans the full domain with named sub-capabilities rather than showing minor gaps; each listed item is a concrete, verifiable data domain rather than generic filler.

5 / 5

Completeness

Both 'what' and 'when' are explicitly answered: the 'what' is the enumerated profiling domains ("Comprehensive drug profiling — mechanism, ... approval history"), and the 'when' is a concrete "Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles..." clause with multiple explicit trigger scenarios. Voice is third-person; nothing is inferred beyond what is stated.

5 / 5

Trigger Term Quality

Natural phrases a user would actually say are present: "'tell me about drug X' queries", "drug interactions", "adverse events", "drug profiles", plus audience triggers ("clinicians, researchers, or regulatory work"). It is not a 5 because common lay synonyms such as "medication", "medicine", or "side effects" are missing; not a 3 because keyword coverage goes well beyond 'some relevant keywords' — it includes direct conversational trigger phrasing.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (single-drug investigation) with distinct triggers ('drug X' queries, drug profile assembly) that would not naturally fire for adjacent skills like target research, disease research, or general literature search. It is not a 4 because the enumerated scope (FAERS, pharmacogenomics, approval history) is distinctive enough that overlap risk with a closely related skill is minimal.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 missing

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

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