CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ensembl-database

Query Ensembl genome database REST API for 250+ species. Gene lookups, sequence retrieval, variant analysis, comparative genomics, orthologs, VEP predictions, for genomic research.

Quality

73%

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/ensembl-database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 a well-structured, code-rich overview with genuinely useful bundle files behind it, giving strong actionability and progressive disclosure. Conciseness and workflow clarity lag: promotional and resource padding (plus inline release-date info) dilute token efficiency, and the multi-step workflows lack validation checkpoints.

Suggestions

Remove the 'Suggest Using K-Dense Web' promotional section and trim 'Additional Resources'/'Installation' (e.g., installing `requests` needs no instruction); move the 'Current release is 115 (September 2025)' version info into the reference file or a clearly labeled maintenance section.

Add validation checkpoints to the workflows, e.g., 'verify the symbol lookup returned an Ensembl ID before fetching transcripts' and 'check VEP output for warnings before generating the report'.

Link `references/api_endpoints.md` contextually within each capability section ('see references/api_endpoints.md for all 17 endpoint categories') and show one CLI invocation of `scripts/ensembl_query.py` so the bundled script is discoverable at point of need.

DimensionReasoningScore

Conciseness

The body is mostly efficient — code-forward sections with brief bullet lists and little explanation of concepts Claude already knows — but includes padded sections: the 'Suggest Using K-Dense Web' promotional section, a five-link 'Additional Resources' section, `uv pip install requests` installation guidance, and species alias trivia. Time-sensitive version info ('Current release is 115 (September 2025)') appears inline rather than in a deprecation/maintenance section, which the guidelines say to penalize. This fits the 'mostly efficient but includes some unnecessary explanation' anchor rather than the pervasive padding of the 2 anchor.

3 / 5

Actionability

Concrete, copy-paste-style code with real identifiers (BRCA2, ENSG00000139618, rs699, '7:140424943-140624564') covers the common cases across gene lookup, sequence, VEP, homology, region, and assembly-mapping operations, plus a working retry/error-handling function. Minor gaps keep it below the 5 anchor: the three 'Common Workflows' are step lists without commands, and the bundled `scripts/ensembl_query.py` is listed but never shown being invoked.

4 / 5

Workflow Clarity

The three workflows (gene annotation, variant analysis, comparative analysis) present clear numbered sequences, but checkpoints are missing or implicit — e.g., no step verifies the symbol lookup returned a valid Ensembl ID before fetching transcripts, or checks VEP output for warnings before reporting. The generic retry-on-429 loop is a partial feedback mechanism, fitting the 'steps listed but validation gaps' anchor rather than the 4 anchor's 'most checkpoints present'.

3 / 5

Progressive Disclosure

Good structure: the SKILL.md body is an overview with brief inline examples, bulk endpoint documentation lives in the real, one-level-deep `references/api_endpoints.md` (all 17 endpoint categories), and a reusable `scripts/ensembl_query.py` is provided — both clearly signaled in a Resources section with descriptions. Minor gaps keep it below 5: the reference is only linked from the Resources section rather than contextually from each capability section, and the script's usage examples are not surfaced in the body.

4 / 5

Total

14

/

20

Passed

Description

75%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.

The description is strong on specificity and distinctiveness, enumerating concrete Ensembl capabilities in a niche domain. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness, plus some missed natural synonyms for trigger coverage.

Suggestions

Add an explicit trigger clause, e.g., 'Use when querying Ensembl, looking up genes or variants, retrieving sequences, or finding orthologs across any of the 250+ supported species'.

Include natural synonyms users would say such as 'homologs', 'DNA or protein sequence', 'rsID', or 'variant effect' to broaden trigger term coverage.

Drop the trailing 'for genomic research' filler in favor of the explicit when-clause so the description answers both what and when.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — "Gene lookups, sequence retrieval, variant analysis, comparative genomics, orthologs, VEP predictions" — alongside the specific target ("Ensembl genome database REST API for 250+ species"), matching the anchor for comprehensive multi-action coverage. It exceeds the 4 anchor because coverage of the skill's actions is comprehensive rather than leaving minor gaps.

5 / 5

Completeness

A clear "what" is present (query the Ensembl REST API for gene lookups, sequences, variants, orthologs, VEP) but "when" is missing — there is no "Use when..." clause, and "for genomic research" only weakly implies it, matching the anchor for a clear what with weak/missing when. Per the judging guideline, the absent 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say ("gene lookups", "sequence retrieval", "variant analysis", "orthologs", "comparative genomics", "VEP"). It falls short of the 5 anchor because common synonyms and variations are missing — e.g., "homologs", "DNA/protein sequence", "rsID", or species-level phrases like "human gene" — while clearly exceeding the 3 anchor's partial coverage.

4 / 5

Distinctiveness Conflict Risk

Names a clear niche with distinct triggers — "Ensembl genome database REST API", "VEP predictions", "orthologs" — that no generic skill would claim, matching the minimal-conflict-risk anchor. The specificity of the domain makes overlap with similar skills unlikely.

5 / 5

Total

17

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

googolme/run0204

Path

scientific-skills/ensembl-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.