CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

drugbank-database

Programmatic access to DrugBank drug and target data; use when you need to download, parse, and analyze DrugBank XML for properties, interactions, pathways, and pharmacology.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/drugbank-database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-organized, highly actionable skill body: a complete executable end-to-end example, the critical namespace gotcha, performance guidance for large XML, and real one-level-deep reference files. The main costs are redundancy (Key Features vs. Dependencies, extraction patterns vs. the code) and coverage gaps where advertised workflows (targets, pathways, downloading) have no example, plus an oversized inline code block that should be split out.

Suggestions

Merge "Key Features" into "Dependencies" (they list the same five libraries) and cut "Core extraction patterns" from Implementation Details since the example code already demonstrates each XPath — this would lift conciseness without losing information.

Add short runnable snippets for the advertised but unserved cases: a drugbank-downloader invocation in Example Usage and a minimal drug–target extraction pattern, or point to references/drug-queries.md for them.

Move the full example code to a file under references/ or scripts/ (keeping a ~10-line quick-start inline), and add one-line descriptions to the three "Further references" entries so navigation is self-describing.

DimensionReasoningScore

Conciseness

The body is mostly efficient — the code example and Implementation Details (namespace gotcha, iterparse note) earn their tokens — but there is real redundancy: the "Key Features" section ("Programmatic download... via drugbank-downloader", "XML parsing... using lxml", "pandas DataFrames", "networkx", "rdkit") duplicates the Dependencies section almost item-for-item, and "Core extraction patterns" re-lists XPath expressions already fully shown in the example code. This matches the 3 anchor ("mostly efficient but includes some unnecessary explanation or could be tightened"); not 4 because two whole sections are duplicative rather than minor instances, and not 2 because nothing explains concepts Claude wouldn't know.

3 / 5

Actionability

The example is complete, executable Python (parse XML with the namespace map, extract a drug table, extract DDIs, build a networkx graph, rank by degree), and the "Core extraction patterns" give copy-paste XPath recipes. Not 5 because advertised use cases lack any code: no example for target extraction, pathway extraction, or an actual drugbank-downloader invocation — minor gaps matching the 4 anchor ("mostly executable guidance; concrete code or commands with minor gaps"); not 3 because what is present is fully executable, not pseudocode.

4 / 5

Workflow Clarity

The example docstring numbers the sequence ("1) Parse a local DrugBank XML file 2) Extract a minimal drug table 3) Extract drug-drug interactions 4) Build a DDI graph") with prerequisites stated up front, and the code embeds sanity outputs ("Drugs:", "Interactions:", node/edge counts, head() previews) plus dropna on the primary ID. This matches the 4 anchor ("clear sequence with most checkpoints present; minor validation gaps") — the checkpoints are implicit print statements with no guidance on interpreting them or recovering from a missing/invalid XML file, which keeps it below 5; the read-only analysis workflow is not destructive/batch, so the workflow cap of 3 does not apply, and the sequence is far too complete for 3.

4 / 5

Progressive Disclosure

The body is well sectioned (When to Use, Key Features, Dependencies, Example Usage, Implementation Details) and closes with clearly signaled, one-level-deep references to three real files ("See: references/data-access.md", "references/drug-queries.md", "references/interactions.md" — all verified to exist), matching the 4 anchor ("good structure; most content appropriately placed; references mostly clear; minor organization gaps"). Not 5 because the ~95-line inline code example could largely live in a separate example file, the "Further references" entries carry no description of what each file contains, and the scripts/ directory is never surfaced from the body (only indirectly via references/data-access.md); not 3 because structure and signaling are clearly better than "references present but not clearly signaled".

4 / 5

Total

15

/

20

Passed

Description

73%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, domain-specific description that names concrete actions and data categories with an explicit "use when" clause, anchored by the unambiguous DrugBank name. Its main weaknesses are the second-person "use when you need" phrasing (penalized on specificity) and a "when" clause that mirrors the "what" rather than adding distinct trigger synonyms like DDI or medication interactions.

Suggestions

Rewrite in third person to avoid the specificity penalty, e.g., "Programmatic access to DrugBank drug and target data. Use when the user asks to download, parse, or analyze DrugBank XML..." instead of "use when you need to download".

Add natural trigger synonyms users would say, such as "drug–drug interactions (DDI)", "drug–target mapping", "ATC codes", and "drugbank.xml", to strengthen trigger-term coverage and distinctiveness.

Differentiate the "when" clause from the "what" clause by naming distinct use contexts (e.g., "when building DDI networks, knowledge graphs, or drug property tables from DrugBank data").

DimensionReasoningScore

Specificity

The description lists several concrete actions ("download, parse, and analyze DrugBank XML") across four data domains ("properties, interactions, pathways, and pharmacology"), which fits the 4 anchor ("lists several specific actions; minor gaps") — but the second-person phrasing "use when you need to download" triggers the rubric's 1-point specificity penalty, lowering it to 3. Not 2 because the domain is named with multiple real actions, not generic.

3 / 5

Completeness

Both "what" ("Programmatic access to DrugBank drug and target data") and "when" ("use when you need to download, parse, and analyze DrugBank XML") are present, matching the 4 anchor. Not 5 because the "when" clause largely restates the "what" rather than adding distinct concrete trigger phrases (e.g., "when the user mentions DrugBank IDs or drug–drug interactions"); not 3 because the "Use when..." clause is explicit, not merely implied.

4 / 5

Trigger Term Quality

Good natural-keyword coverage: "DrugBank", "drug and target data", "DrugBank XML", "interactions", "pharmacology" — phrases a user would naturally say. Not 5 because common synonyms and variations are missing ("drug–drug interactions", "DDI", "medication", no file extension like .xml mentioned on its own); not 3 because coverage clearly exceeds "some relevant keywords" with domain-specific natural terms.

4 / 5

Distinctiveness Conflict Risk

"DrugBank" is a uniquely named database with no competing skill niche, so the trigger is highly distinct with minimal conflict risk — a clear match for the 5 anchor ("clear niche with distinct triggers; minimal conflict risk"). Not 4 because nothing in the description overlaps with adjacent skills (e.g., generic cheminformatics or PubMed skills).

5 / 5

Total

16

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/drugbank-database/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.