CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ensembl-skill

Submit compact Ensembl REST API requests for lookup, overlap, cross-reference, and variation endpoints. Use when a user wants concise Ensembl summaries

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 highly actionable, well-organized skill body: executable examples, explicit input/output contracts, and clear error signaling. The only improvement is removing the duplicated example between the "Input" and "Execution" sections.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of known concepts, but the "## Execution" echo block duplicates the first "Common Ensembl pattern" verbatim and header guidance appears in both the rules and the examples — minor duplication that could be trimmed.

4 / 5

Actionability

Fully executable copy-paste command (echo JSON | python scripts/rest_request.py), two complete JSON payload patterns, exact required/optional fields, and concrete endpoint paths covering the common cases.

5 / 5

Workflow Clarity

Simple single-task skill (invoke one script) with an unambiguous action: the input contract, preferred paths, success output shape, and failure shape (ok=false with error.code/error.message) are all explicitly specified; no destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and no need for external references; the single bundle file (scripts/rest_request.py) exists, is correctly referenced, and the body explicitly states no additional runtime references are required.

5 / 5

Total

19

/

20

Passed

Description

83%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, third-person description with concrete endpoint actions and a distinct niche. Its main weakness is the narrow "Use when" clause, which covers only summary requests rather than the full range of described capabilities, and limited synonym coverage in trigger terms.

Suggestions

Broaden the trigger clause to cover the described capabilities, e.g. "Use when a user wants to look up Ensembl gene/transcript IDs, query genomic regions, fetch cross-references or variant data, or get concise Ensembl summaries."

Add natural synonyms users would actually say, such as "Ensembl ID", "gene ID", "genomic region", and "variant", to improve trigger matching.

Keep the description in third person and avoid adding vague qualifiers like "compact" without tying them to a concrete behavior.

DimensionReasoningScore

Specificity

"Submit compact Ensembl REST API requests for lookup, overlap, cross-reference, and variation endpoints" lists four concrete endpoint actions that comprehensively match the skill's supported paths; no coverage gaps within its scope.

5 / 5

Completeness

The "what" is explicit (submit compact REST requests across four endpoint families) and a "Use when..." clause exists, but the trigger ("a user wants concise Ensembl summaries") is narrower than the described capabilities, omitting lookup, overlap, and variation query use cases.

4 / 5

Trigger Term Quality

Natural terms like "Ensembl", "REST API", "lookup", and "concise Ensembl summaries" are present, but common user phrasings such as "Ensembl ID", "gene lookup", "genomic region", or "variant" are missing.

4 / 5

Distinctiveness Conflict Risk

"Ensembl REST API" is a clear niche with distinct triggers; no realistic overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openai/plugins

Path

plugins/life-science-research/skills/ensembl-skill/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.