CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

embl-ebi-ols

Query and search the EMBL-EBI Ontology Lookup Service (OLS) for biomedical ontology terms, definitions, and hierarchies across 250+ ontologies (e.g., GO, DOID, HP). Use when the user asks to search for terms, retrieve details, navigate hierarchies (parents, children, ancestors), look up properties and individuals, get autocomplete suggestions, or access ontology metadata and statistics.

Quality

89%

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

82%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 highly actionable, executable reference for the OLS utility scripts with a clearly sequenced two-step resolution workflow and proper one-level reference separation. Weaknesses are modest: redundant guidance across the Recipes/Utility/Workflow sections, no error-recovery path for failed or empty searches, and an unreferenced citation.bib in the bundle.

Suggestions

Consolidate the overlapping 'Quick Recipes', 'Workflow', and per-script documentation into one navigation pattern (e.g., keep recipes + options, fold the Workflow section's restated guidance into it) to remove redundancy.

Add a brief error-recovery note for zero-hit searches (e.g., when --exact returns nothing, retry without --exact or with a synonym) instead of the absolute 'do NOT search across multiple ontologies' rule.

Reference references/citation.bib in the body (e.g., in a Reference section alongside api_reference.md) so every bundle file is discoverable.

DimensionReasoningScore

Conciseness

The body is dense and operational — copy-paste commands, option tables, no explanations of concepts Claude already knows. Minor trimming opportunities remain: the "Quick Recipes", "Utility Scripts", and "Workflow" sections restate overlapping guidance, and the "--output is required for all scripts" callout is repeated per-script (and contradicted by per-script "default: stdout" entries). Not level 5 ('every token earns its place') given this redundancy, but well above the noticeably-verbose level 2-3 range.

4 / 5

Actionability

Every script has fully executable, copy-paste-ready commands (e.g., `uv run scripts/search_ols.py --query "diabetes" --rows 5 --output /tmp/ols_search_results.json`), all flags documented with concrete values, and worked multi-step examples use real IDs (DOID:5844, GO:0005634). Covers the common cases comprehensively.

5 / 5

Workflow Clarity

The multi-step entity-resolution pattern is explicitly sequenced ("exactly 2 steps": search with --exact --rows 1, then get relations) and the Workflow section gives a clear 8-step decision sequence. Operations are read-only API queries, so the destructive/batch validation cap does not apply, but there are no checkpoints or feedback loops for failure cases (e.g., zero-hit searches — the "do NOT search across multiple ontologies" rule forbids any fallback), leaving it at 'most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

Good structure: option docs and recipes are appropriately inline for a script-driven skill, and the API reference is clearly signaled and one level deep ([references/api_reference.md](references/api_reference.md), verified to exist). However, bundle file references/citation.bib is never mentioned anywhere in SKILL.md, a minor organization gap that keeps it below the 'easy navigation, content appropriately split' top anchor.

4 / 5

Total

17

/

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.

The description is a strong exemplar: it states concrete capabilities in third person and pairs them with an explicit 'Use when' clause enumerating the trigger scenarios. Trigger-term coverage is good though not exhaustive of natural synonyms, which is the only dimension not at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "Query and search", "retrieve details", "navigate hierarchies (parents, children, ancestors)", "look up properties and individuals", "get autocomplete suggestions", "access ontology metadata and statistics" — with comprehensive coverage of the API surface in third person. No material capability is left out, so it exceeds the 'minor gaps' level 4 anchor.

5 / 5

Completeness

Explicitly answers both: what ("Query and search the EMBL-EBI Ontology Lookup Service (OLS) for biomedical ontology terms, definitions, and hierarchies") and when ("Use when the user asks to search for terms, retrieve details, navigate hierarchies..., get autocomplete suggestions, or access ontology metadata and statistics") — mirroring the anchor-5 example structure.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("search for terms", "parents, children, ancestors", "autocomplete suggestions", named ontologies GO/DOID/HP), but a few natural user phrasings are missing (e.g., "synonyms", "subtypes", "find a GO term"). Fits the 'good coverage, a few natural terms missing' anchor rather than the comprehensive level 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche: the named EMBL-EBI OLS service with ontology-specific triggers (hierarchies, properties/individuals, ontology metadata) is distinct from generic search or documentation skills; conflict risk is minimal.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

google-deepmind/science-skills

Path

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