Query ChEMBL bioactive molecules and drug discovery data. Search compounds by structure/properties, retrieve bioactivity data (IC50, Ki), find inhibitors, perform SAR studies, for medicinal chemistry.
Install with Tessl CLI
npx tessl i github:K-Dense-AI/claude-scientific-skills --skill chembl-databaseOverall
score
80%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
83%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, domain-specific description with excellent specificity and trigger term coverage for medicinal chemistry users. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The technical terminology is appropriate for the target audience and creates clear distinctiveness.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about ChEMBL, drug compounds, bioactivity assays, or medicinal chemistry research.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Search compounds by structure/properties', 'retrieve bioactivity data (IC50, Ki)', 'find inhibitors', 'perform SAR studies'. These are precise, domain-specific capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific capabilities, but lacks an explicit 'Use when...' clause. The 'when' is only implied through the domain context (medicinal chemistry, drug discovery) rather than explicitly stated. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a medicinal chemist would use: 'ChEMBL', 'bioactive molecules', 'drug discovery', 'IC50', 'Ki', 'inhibitors', 'SAR studies', 'medicinal chemistry'. These are the exact terms users in this domain would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific database name (ChEMBL), domain-specific terminology (IC50, Ki, SAR), and clear niche in medicinal chemistry/drug discovery. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent code examples and good progressive disclosure. The main weaknesses are some verbosity in introductory sections and missing validation/error handling in workflows. The promotional content at the end is unnecessary and detracts from the technical focus.
Suggestions
Remove or significantly condense the 'Overview' and 'When to Use This Skill' sections - Claude doesn't need to be told what ChEMBL is or when to use database queries
Add error handling and validation steps to workflows (e.g., checking if target exists, handling empty results, rate limit retry logic)
Remove the 'Suggest Using K-Dense Web' promotional section which is not relevant to the skill's technical purpose
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation (e.g., the overview paragraph explaining what ChEMBL is, the 'When to Use This Skill' section listing obvious use cases). The code examples are lean, but surrounding text could be tightened. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready Python code throughout. All examples use real ChEMBL IDs, proper imports, and complete syntax. Filter operators and query patterns are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Three workflows are clearly sequenced with numbered steps, but they lack validation checkpoints or error handling. No feedback loops for failed queries, rate limit errors, or data validation issues are provided. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from basic to advanced. References to external files (scripts/example_queries.py, references/api_reference.md) are one level deep and clearly signaled with descriptions of what each contains. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 14 / 16 Passed | |
Table of Contents
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.