CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ensembl-database

Access Ensembl REST API for vertebrate genomic data; use when you need gene/ID lookups, sequence retrieval, variant effect prediction (VEP), or homology/assembly coordinate mapping.

Quality

76%

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

Quality

Content

50%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 skill's real content (sections 1–5) is accurate, executable, and properly references a genuine one-level-deep bundle file. But the body is preceded by an entire generic template half that duplicates every section header, contradicts the real dependencies, and pads the token budget, dragging conciseness and workflow clarity down.

Suggestions

Delete the generic template half (the unnumbered 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', 'Implementation Details' sections) and keep only the numbered sections 1–5, which contain the actual content.

Resolve the contradictory dependency specs: the template half says Python '3.10+' while section 3 says '>=3.8' — pick one and state the 'ensembl_rest' client dependency once.

Remove the boilerplate example with the nonexistent timestamped path ('cd "20260316/scientific-skills/…"') and the placeholder 'edit the in-file CONFIG block' run plan; the verified CLI examples in section 4 already cover usage.

DimensionReasoningScore

Conciseness

The body is two concatenated documents: the first half is generic template filler ('Structured execution path designed to keep outputs consistent and reviewable', 'Use this skill when a evidence insight task needs a packaged method instead of ad-hoc freeform output') that duplicates every section header the second half covers. This matches the 2 anchor ('noticeably verbose; several unnecessary explanations or padded sections'); not 3, because the redundancy is an entire half of the file rather than minor trimmable passages; not 1, because the second half is lean and accurate.

2 / 5

Actionability

Section 4 provides copy-paste-ready CLI commands verified against the script ('--action lookup --species human --symbol BRCA2', '--action vep --species human --hgvs "ENST00000380152.8:c.68_69delAG"') with all parameters documented. Not 5: the template half's example references a nonexistent timestamped path ('cd "20260316/scientific-skills/…"') and adds ambiguity alongside the real commands.

4 / 5

Workflow Clarity

Two conflicting run plans coexist (a generic 4-step 'Example run plan' vs. the direct CLI examples), and the duplicated Dependencies sections contradict each other (Python '3.10+' vs '>=3.8'), leaving the sequence muddled with no validation checkpoint. Fits the 3 anchor ('steps listed but… checkpoints missing or implicit'); not 4 because the duplication and contradiction exceed minor gaps; not 2 because concrete, executable steps are present.

3 / 5

Progressive Disclosure

The reference is well-signaled and one level deep ('For the exact REST paths, required parameters, and response schemas, see: references/api_endpoints.md' — verified to exist), but the body's duplicated section structure (two 'When to Use', two 'Key Features', two 'Dependencies', two 'Example Usage' sections) impairs navigation. Matches the 3 anchor ('some structure but could be better organized'); not 4 because the organization gaps are more than minor.

3 / 5

Total

12

/

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 description: concrete, third-person, with an explicit 'use when…' trigger clause enumerating all four capabilities. Its only weakness is trigger-term breadth — a few natural synonyms (ortholog, HGVS, GRCh37/GRCh38) are absent.

DimensionReasoningScore

Specificity

The description lists four concrete actions — 'gene/ID lookups, sequence retrieval, variant effect prediction (VEP), or homology/assembly coordinate mapping' — which comprehensively covers the skill's capabilities, matching the 5 anchor ('multiple specific concrete actions; comprehensive coverage').

5 / 5

Completeness

It explicitly answers both what ('Access Ensembl REST API for vertebrate genomic data' plus the four capabilities) and when ('use when you need gene/ID lookups, sequence retrieval, variant effect prediction (VEP), or homology/assembly coordinate mapping') with concrete trigger phrases, exactly matching the 5 anchor.

5 / 5

Trigger Term Quality

Good natural-term coverage ('gene/ID lookups', 'sequence retrieval', 'VEP', 'homology', 'coordinate mapping', 'Ensembl') that users would actually say, but common synonyms and variations are missing (e.g., 'ortholog', 'HGVS', 'GRCh37/GRCh38', 'assembly lift-over'). Fits the 4 anchor ('good keyword coverage; a few natural terms missing') rather than 5's requirement of synonyms/extensions.

4 / 5

Distinctiveness Conflict Risk

'Ensembl REST API' plus the specific genomics operations define a clear niche with distinct triggers and minimal conflict risk against generic data-processing or document skills. Not 4, because no closely related skill would plausibly capture these triggers.

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.

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