CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

drug-discovery

Drug discovery: ChEMBL search, drug-likeness, interactions.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/research/drug-discovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The body is a highly actionable, executable set of API workflows with clear sequencing and a genuinely useful one-level-deep ADMET reference. Its main weaknesses are moderate: the shipped scripts are invisible from SKILL.md (and their functionality is duplicated inline), and the description of capabilities in the body is broader than the frontmatter advertises.

Suggestions

Reference the bundled scripts in the body (e.g. in each workflow: "For batch use, see scripts/chembl_target.py and scripts/ro5_screen.py") instead of duplicating their functionality inline — this would shrink SKILL.md and make all three bundle files discoverable.

Add a short error-recovery note for API failures (HTTP errors, empty JSON, rate-limit 429s) to close the workflow validation gap; the scripts already model this behavior.

Trim the persona opener and the "world's largest open bioactivity database" aside — they add tokens without adding guidance Claude does not already have.

DimensionReasoningScore

Conciseness

Nearly every token is executable code with concrete example IDs ("CHEMBL203", "CHEMBL25 (aspirin)"), with only minor trimmable padding: the "You are an expert pharmaceutical scientist" persona opener, the "world's largest open bioactivity database" aside, and inline bash pipelines that duplicate functionality already shipped in scripts/. This is efficient with minor instances of over-explanation, not the fully lean anchor.

4 / 5

Actionability

Every workflow is a complete, copy-paste-ready bash pipeline that handles URL-encoding and JSON parsing end-to-end, with specific example inputs covering the common cases (target search, bioactivity lookup, molecule properties, drug-likeness, interactions, adverse events, gene-disease). The bundled scripts (chembl_target.py, ro5_screen.py) are even more robust with error handling and rate limiting.

5 / 5

Workflow Clarity

Five workflows are clearly numbered, titled, and self-contained, and the Reasoning Guidelines give a numbered analysis sequence (state values, apply rule sets, flag liabilities, suggest optimizations, cite source); inline code checks for empty results ("No interaction data found", "Target not found"). Minor validation gaps remain — no explicit feedback loop for API failures or rate-limit errors — and the cap at 3 does not apply since these are read-only single queries, not destructive or batch operations.

4 / 5

Progressive Disclosure

The body is well-sectioned and references/ADMET_REFERENCE.md is clearly signaled one level deep ("See references/ADMET_REFERENCE.md for detailed guidance"), but 2 of the 3 bundle files (scripts/chembl_target.py, scripts/ro5_screen.py) are never mentioned anywhere in the body, and ~150 lines of inline code duplicate them. Content that should point to the separate scripts is inlined and the navigation to most of the bundle is missing, which exceeds anchor 4's "minor organization gaps".

3 / 5

Total

16

/

20

Passed

Description

57%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.

The description identifies a distinct niche with recognizable core actions, but it is a terse fragment rather than a complete description: it lacks any "Use when..." trigger guidance, omits several of the skill's actual capabilities, and misses common trigger synonyms such as "adverse events" or "side effects".

Suggestions

Add an explicit trigger clause, e.g. "Use when researching drugs, compounds, drug targets, bioactivity, drug-likeness (Lipinski/Veber), drug interactions, or adverse events."

Convert the fragment list into full verb phrases covering the skill's actual workflows, e.g. "Searches ChEMBL for bioactive compounds, computes Lipinski/Veber drug-likeness via PubChem, and looks up drug interactions and adverse events via openFDA."

Include natural synonyms users would say — "side effects", "pharmacology", "medicinal chemistry", "PubChem", "FDA labels" — to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Drug discovery") and a few concrete action fragments ("ChEMBL search, drug-likeness, interactions"), but they are terse noun phrases with gaps in coverage (no PubChem lookup, target-disease association, or adverse-event analysis). This matches the anchor for naming the domain with 1-2 concrete actions but not comprehensive coverage.

3 / 5

Completeness

A clear "what" is present (ChEMBL search, drug-likeness, interactions) but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Terms like "Drug discovery", "ChEMBL", "drug-likeness", and "interactions" are natural phrases users would say, but common variations and synonyms are missing — no "adverse events", "side effects", "pharmacology", "medicinal chemistry", "PubChem", or "FDA". Some relevant keywords present, but missing common variations.

3 / 5

Distinctiveness Conflict Risk

"Drug discovery: ChEMBL search" carves out a clear niche with distinctive triggers (ChEMBL, drug-likeness) that virtually no other skill would claim, so conflict risk is minimal. The generic word "interactions" is fully disambiguated by the drug-discovery frame.

5 / 5

Total

14

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/research/drug-discovery/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.