Query Ensembl genome database REST API for 250+ species. Gene lookups, sequence retrieval, variant analysis, comparative genomics, orthologs, VEP predictions, for genomic research.
77
77%
Does it follow best practices?
Impact
65%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/ensembl-database/SKILL.mdQuality
Discovery
82%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 genomics researchers. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others. The technical terminology is appropriate for the target audience.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Ensembl, needs genomic data, mentions species comparisons, or requests variant effect predictions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Gene lookups, sequence retrieval, variant analysis, comparative genomics, orthologs, VEP predictions' - these are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the domain context. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Ensembl', 'genome', 'gene lookups', 'sequence retrieval', 'variant analysis', 'orthologs', 'VEP predictions', 'genomic research' - these are terms bioinformaticians would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Ensembl genome database REST API' and '250+ species' - this is a clear niche that would not conflict with general bioinformatics or other database skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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 covering the full range of Ensembl API capabilities. The main weaknesses are some verbosity in introductory sections and workflows that list steps without explicit validation checkpoints. The progressive disclosure and actionability are strong points.
Suggestions
Remove or condense the 'When to Use This Skill' section - the capabilities section already makes usage clear
Add validation checkpoints to the Common Workflows (e.g., 'Verify gene ID exists before proceeding to transcript retrieval')
Trim the Overview paragraph - Claude doesn't need to know EMBL-EBI maintains it or that it's 'comprehensive'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanations (e.g., 'comprehensive resource for vertebrate genomic data maintained by EMBL-EBI') and the 'When to Use This Skill' section largely restates what the capabilities section covers. Could be tightened by removing redundant descriptions. | 2 / 3 |
Actionability | Provides fully executable Python code examples for all major operations, including both the ensembl_rest package and direct REST API approaches. Code is copy-paste ready with realistic parameters like actual gene IDs and symbols. | 3 / 3 |
Workflow Clarity | The 'Common Workflows' section lists steps but lacks validation checkpoints or error recovery guidance within the workflows themselves. The error handling example is good but separate from the workflows. No explicit 'verify before proceeding' steps for multi-step processes. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, references to external files (api_endpoints.md, ensembl_query.py), and appropriate depth. The overview is concise with detailed examples inline where needed, and advanced resources are clearly signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
71add64
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.