CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 highly actionable with executable code and a clear download→parse→extract→analyze pipeline, but it lacks validation/verification checkpoints for a batch XML workflow and carries minor redundancy between the code and prose patterns.

Suggestions

Add an explicit validation/verification step in the workflow (e.g., assert non-null primary DrugBank IDs, check record counts against expectations, or validate XML against the DrugBank schema before analysis) to lift workflow clarity above the batch-operation cap.

De-duplicate the "Core extraction patterns" section against the example code, or move the worked example into a reference file and keep only the key XPath patterns inline.

Flesh out the thin reference files (drug-queries.md, interactions.md) or consolidate them so the SKILL.md overview can lean more on one-level-deep detail rather than inlining the full example.

DimensionReasoningScore

Conciseness

Mostly efficient and domain-specific, but the "Core extraction patterns" section duplicates XPath already shown in the code block, and the data-modeling notes lightly re-explain pandas/networkx concepts Claude already knows.

4 / 5

Actionability

The example is fully executable, copy-paste-ready Python with real imports, namespace handling, and XPath covering parsing, drug/interaction extraction, DDI graph construction, and degree analysis.

5 / 5

Workflow Clarity

A numbered end-to-end sequence is present, but this batch XML-processing workflow has no validation or verification checkpoints (no checks on extracted IDs, no error handling, no output validation), which caps the score per the batch-operation rule.

3 / 5

Progressive Disclosure

Clear sectioned overview with three real, one-level-deep references (data-access.md, drug-queries.md, interactions.md) signaled via "See:" links; the large inline code block and thin reference files leave minor organization gaps.

4 / 5

Total

16

/

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, specific description that clearly states capabilities and an explicit use-when trigger tied to DrugBank XML processing. Minor improvement possible by adding synonyms (e.g., "drug database") and the .xml extension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("download, parse, and analyze") across four specific data domains (properties, interactions, pathways, pharmacology), giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers "what" (programmatic access to DrugBank drug and target data) and "when" via a concrete "use when you need to download, parse, and analyze..." trigger clause.

5 / 5

Trigger Term Quality

Good natural-keyword coverage ("DrugBank", "drug and target data", "interactions", "pathways", "pharmacology") but misses common synonyms and the .xml file extension that users might mention.

4 / 5

Distinctiveness Conflict Risk

DrugBank is a clear, narrow niche with distinct triggers (DrugBank XML, drug/target data) and minimal overlap risk with other skills.

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.

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