CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chembl-database

Query the ChEMBL database for bioactive molecules, targets, bioactivities, and approved drugs; use this when you need to filter by physicochemical properties (e.g., MW, LogP), chemical structure (SMILES), or retrieve drug mechanism information.

Quality

81%

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

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 solid, executable skill body whose main weakness is redundancy: 'When to Use', 'Key Features', and parts of 'Implementation Details' repeat the same capability list three times. The core workflow is clearly sequenced and detail is appropriately pushed to the bundled reference and script files, but the SMILES structure-search capability lacks any concrete example.

Suggestions

Merge 'When to Use' and 'Key Features' into a single section — they currently restate the same five capabilities in near-identical wording, and trim 'Implementation Details' bullets that re-explain what the example code already shows.

Add a concrete, runnable SMILES/structure-search example (or state explicitly that the client does not support it) instead of the vague 'where supported by the API/client' phrasing.

Show a one-line invocation example for the bundled scripts/query_chembl.py CLI (e.g., 'python scripts/query_chembl.py molecule --term aspirin') so users can run it directly, and move the bundle-file pointers into a clearly labeled 'References' section rather than tucking them under 'Dependencies'.

DimensionReasoningScore

Conciseness

The content is mostly efficient — it does not explain concepts Claude already knows and the example code is tight — but there is real redundancy: the 'When to Use' and 'Key Features' sections restate the same five capabilities in near-identical wording, and several 'Implementation Details' bullets (filtering model, pagination, bioactivity fields) re-explain what the example code already demonstrates. This fits the level-3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened'); it is not level 2 because there is no conceptual padding or educational fluff, and not level 4 because the duplicated capability lists are a clear trim target.

3 / 5

Actionability

The guidance is mostly executable: a complete, runnable Python example covering molecule search, MW filtering, target lookup, bioactivity, and mechanism retrieval with concrete field names and operators ('pref_name__icontains', 'molecule_properties__mw_freebase__lte=500'), plus an install command. It falls short of level 5 because the SMILES/structure-search capability is described only vaguely ('where supported by the API/client', 'as documented in references/api_reference.md') with no concrete example, and the bundled scripts/query_chembl.py CLI is mentioned but never shown how to invoke.

4 / 5

Workflow Clarity

The example code lays out a clear numbered sequence (1–5: name search, property filter, target lookup, activity retrieval, mechanism retrieval) with one explicit checkpoint ('raise SystemExit("No molecules found for query.")') and a note to handle missing keys, matching the level-4 anchor 'clear sequence with most checkpoints present; minor validation gaps'. It is not level 5 because there are no error-recovery guidance (e.g., handling empty activity/mechanism results or API errors), though it is not capped at 3 since these are read-only queries, not destructive or batch operations.

4 / 5

Progressive Disclosure

The body stays at overview level and correctly pushes detail to real, verified bundle files — references/api_reference.md (which does contain the filter syntax and resource list) and scripts/query_chembl.py — with pointers from the Dependencies section and Implementation Details ('consult references/api_reference.md for the authoritative list'). This matches the level-4 anchor: good structure, references mostly clear, minor organization gaps — the file pointers sit under 'Dependencies' with hedged wording ('optional, if present in this repository') rather than a dedicated, well-signaled references section. It is not level 5 for that reason, but well above level 3 since nothing that belongs in a separate file is inlined and references are one level deep.

4 / 5

Total

15

/

20

Passed

Description

87%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 that clearly states what the skill does and when to use it, with concrete domain examples (MW, LogP, SMILES) that make it highly discoverable and distinctive. The only deductions are the second-person phrasing in the trigger clause and a few missing common synonyms such as 'compounds' or 'IC50'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with concrete examples — 'Query the ChEMBL database for bioactive molecules, targets, bioactivities, and approved drugs', 'filter by physicochemical properties (e.g., MW, LogP)', 'chemical structure (SMILES)', 'retrieve drug mechanism information' — which matches the level-5 anchor's comprehensiveness. However, the 'when' clause uses second-person voice ('use this when you need to filter'), and the rubric guidelines mandate a 1-point specificity reduction for second-person phrasing, bringing it to 4.

4 / 5

Completeness

It explicitly answers both questions: the 'what' is 'Query the ChEMBL database for bioactive molecules, targets, bioactivities, and approved drugs' and the 'when' is a concrete trigger clause — 'use this when you need to filter by physicochemical properties (e.g., MW, LogP), chemical structure (SMILES), or retrieve drug mechanism information'. This matches the level-5 anchor ('clearly and explicitly answers both what AND when with concrete trigger phrases'); it is not level 4 because the 'when' is not merely present but specific and multi-trigger.

5 / 5

Trigger Term Quality

Natural domain terms are well covered: 'bioactive molecules', 'approved drugs', 'MW', 'LogP', 'SMILES', 'drug mechanism' — terms a medicinal-chemistry user would actually say. It falls short of the level-5 anchor because common synonyms and variations such as 'compounds', 'IC50/Ki/potency', or 'drug discovery' are missing, but it clearly exceeds level 3 ('some relevant keywords but missing common variations') on breadth and naturalness.

4 / 5

Distinctiveness Conflict Risk

It names a specific database (ChEMBL) and distinctive domain triggers (MW, LogP, SMILES, mechanism of action), creating a clear niche with minimal overlap risk against generic search or data skills. This matches the level-5 anchor; no neighboring anchor fits better since the triggers are highly specific to bioactivity/drug data.

5 / 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

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