CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

92%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable reference body with a clear progressive workflow and good file-based disclosure. Its main weakness is mild redundancy from restating tool chains across several tables, and the referenced bundle files are not present in the review directory.

Suggestions

Consolidate tool listings: the Fallback Chains, Quick Reference, and Research Paths tables restate overlapping tool sets — merge into a single canonical reference and link to it to trim ~240 lines.

Verify the bundle files referenced in the body (REPORT_TEMPLATE.md, REPORT_GUIDELINES.md, TOOLS_REFERENCE.md, CHECKLIST.md, EXAMPLES.md) are actually shipped alongside SKILL.md; none were present in references/, scripts/, or assets/.

Consider moving the inline 'Research Paths Summary' detail (9 paths) fully into REPORT_GUIDELINES.md and leaving only a one-line pointer per path, since that section repeats tool chains already covered elsewhere.

DimensionReasoningScore

Conciseness

Largely efficient (dense tables, assumes competence, no beginner concept explanations), but at ~240 lines it repeats the same tool names across the Fallback Chains, Quick Reference, and Research Paths tables and could be consolidated.

2 / 3

Actionability

Highly executable: exact tool names, concrete normalization rules ('CHEMBL1431' full format, FAERS UPPERCASE, SMILES as list), a numeric pChEMBL >= 6.0 cutoff, and copy-ready identifier-resolution chains.

3 / 3

Workflow Clarity

A clearly sequenced 12-step progressive-writing workflow with mandatory report-first ordering, per-path fallback chains as error-recovery loops, and a referenced pre-delivery CHECKLIST.md verification step.

3 / 3

Progressive Disclosure

SKILL.md acts as a well-signaled overview with one-level-deep markdown links to REPORT_TEMPLATE.md, REPORT_GUIDELINES.md, TOOLS_REFERENCE.md, CHECKLIST.md, and EXAMPLES.md, splitting detail appropriately.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person description that concretely enumerates capabilities and gives explicit, natural trigger phrasings. It cleanly distinguishes the skill from adjacent research skills.

DimensionReasoningScore

Specificity

Lists multiple concrete profiling actions — 'mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history' — each naming a distinct capability.

3 / 3

Completeness

Clearly answers both 'what' (comprehensive drug profiling with enumerated dimensions) and 'when' via an explicit 'Use for ...' clause with concrete triggering scenarios.

3 / 3

Trigger Term Quality

Includes natural phrasings a user would actually say, e.g. "'tell me about drug X' queries" and "full drug investigation reports", plus role-based triggers (clinicians, researchers, regulatory work).

3 / 3

Distinctiveness Conflict Risk

Occupies a clear drug-research niche with distinct triggers; unlikely to fire for the related target/disease/literature skills it itself redirects to in 'When NOT to Use'.

3 / 3

Total

12

/

12

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

relative_links

Relative link issues: 8 missing

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.