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

83%

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

71%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-engineered orchestration skill: concrete tool chains, fallbacks, type normalization, and a clear 12-step report-first workflow, with only minor verbosity. Its main structural weakness is that all five referenced bundle files are missing, so the detailed template, guidelines, tool reference, and checklist it leans on are unavailable.

Suggestions

Ship the referenced bundle files (REPORT_TEMPLATE.md, REPORT_GUIDELINES.md, TOOLS_REFERENCE.md, CHECKLIST.md, EXAMPLES.md) alongside SKILL.md, or inline the essential parts (e.g., the 11 section headers and the pre-delivery checklist) so the skill is self-sufficient.

Since TOOLS_REFERENCE.md carries the full parameter listings, inline the parameter signatures for the most-used tools (PubChem, ChEMBL, DailyMed, FAERS) in SKILL.md to close the actionability gap if the reference file may be absent.

Add an explicit inline validation step (e.g., 'Before delivery, verify every section placeholder is replaced and each fact has a source citation') instead of relying solely on the external CHECKLIST.md.

Deduplicate the fallback information between the 'Fallback Chains' and 'Quick Reference: Tools by Use Case' tables, and trim the live-verified example narratives to one line each.

DimensionReasoningScore

Conciseness

The body is dense and operational — tool chains, fallback tables, and type-normalization rules with almost no padding or explanation of concepts Claude already knows. It falls short of a 5 because the DrugCentral and DSLD paragraphs carry long live-verified example narratives, and fallback information is repeated across the 'Fallback Chains' and 'Quick Reference' tables, so a moderate trim is possible.

4 / 5

Actionability

Concrete tool calls with argument names (e.g., 'DrugCentral_get_targets(chem_id=<InChIKey or ChEMBL ID>)', 'PubChem_get_CID_by_compound_name(compound_name)'), exact ID formats ('CHEMBL1431', 'PA450657'), uppercase FAERS names, and expected extracted fields make most guidance executable. It is not a 5 because the complete parameter listing is deferred to TOOLS_REFERENCE.md, which is not present in the bundle, leaving per-tool parameter details incomplete.

4 / 5

Workflow Clarity

A 12-step progressive writing workflow, a phase-ordered disambiguation chain, per-path tool sequences, and explicit fallback loops ('If ADMET-AI fails, automatically use fallback. Never leave Section 4 empty') give a clear sequence with most checkpoints present. It is not a 5 because pre-delivery verification is delegated entirely to CHECKLIST.md rather than an inline validation step, and Section 5.2's count-table requirement is the only hard in-body output check.

4 / 5

Progressive Disclosure

The SKILL.md is structured as a proper overview with well-signaled, one-level-deep references (REPORT_TEMPLATE.md, REPORT_GUIDELINES.md, TOOLS_REFERENCE.md, CHECKLIST.md, EXAMPLES.md) — nominally a 5 pattern. However, none of these referenced files exist in the bundle (no references/, scripts/, or assets/ directories), so every pointer is broken and the navigation the skill depends on does not resolve; this drops it to 3.

3 / 5

Total

15

/

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: third-person, specific, and comprehensive about both capabilities and explicit trigger scenarios, with no fluff. The only room for improvement is broader natural-term coverage (synonyms like 'medication') and sharpening the boundary against the dedicated drug-interaction and literature-research skills.

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' — which is comprehensive, specific coverage of what a drug profile contains, matching the anchor-5 example's level of enumeration. It is not a 4 because no meaningful capability area is missing for this domain.

5 / 5

Completeness

It clearly answers both halves: the 'what' is 'Comprehensive drug profiling' with the enumerated capability areas, and the 'when' is explicit with concrete trigger phrases — "Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory work." This matches the anchor-5 example pattern; a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

It includes natural phrases users would actually say: "tell me about drug X", "full drug investigation reports", "drug profiles", and audience terms like 'clinicians, researchers, or regulatory work'. A few common natural terms are missing (e.g., 'medication', 'pharmacology', 'drug safety review'), so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (whole-drug investigation via chemical/clinical/safety databases) with distinct triggers. It is not a 5 because 'drug interactions' as a listed capability overlaps the dedicated drug-drug-interaction skill, and the broad "tell me about drug X" trigger could also plausibly route to literature-deep-research — minor overlap with closely related skills, fitting anchor 4.

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

relative_links

Relative link issues: 8 missing

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

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