CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

encode-api

Access the ENCODE Project REST API to search for and retrieve biological data (biosamples, experiments, etc.). Use this skill when the user needs to query ENCODE data, search by keywords, or retrieve specific objects by accession ID.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/encode-api/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 has a solid executable core — verified script functions, copy-pasteable examples, and useful API details — but it is wrapped in generic templated boilerplate that dilutes the token budget, and it contains dangling references (missing requirements.txt, wrong-direction cross-reference, machine-specific cd path). Trimming the filler and fixing the broken references would move this to a good example.

Suggestions

Cut the generic template sections (When to Use, Key Features, Implementation Details, Output Contract, Validation and Safety Rules, Failure Handling) or fold their one useful line each into the Usage section — they are boilerplate that adds no ENCODE-specific knowledge.

Fix the dangling references: replace 'pip install -r requirements.txt' with 'pip install requests' (no requirements.txt exists in the bundle), correct 'See ## Usage above' to point forward, and remove the machine-specific 'cd "20260316/..."' path.

Make the workflow concrete: replace abstract steps like 'Run a final validation pass' with a checkpoint tied to the script, e.g. 'run python scripts/encode_client.py --help to confirm arguments, verify the JSON result is non-empty, and check the HTTP status on errors'.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template boilerplate that assumes Claude's competence is low: 'Use this skill when the request matches its documented task boundary', 'Structured execution path designed to keep outputs consistent and reviewable', plus padded sections (Key Features, Implementation Details, Output Contract, Validation and Safety Rules, Failure Handling) that teach nothing ENCODE-specific. Not a 1 because the Usage and API Reference sections are lean and earn their tokens.

2 / 5

Actionability

The Usage section gives complete, executable examples ('from scripts.encode_client import search_encode', 'search_encode(term="bone chip", limit=10)', 'get_object(accession="ENCBS000AAA")') and both functions exist in the script. Not a 5 because of concrete gaps: the dependency instruction references a non-existent 'requirements.txt', the bash example cds into a machine-specific path ('20260316/scientific-skills/Evidence Insight/encode-api'), and 'See ## Usage above' points the wrong direction (Usage appears later in the file).

4 / 5

Workflow Clarity

A sequence exists ('Recommended Workflow' and the numbered 'Example run plan'), but the steps are abstract ('Select the documented execution path', 'Run a final validation pass') with no concrete checkpoints tied to the script. It fits the score-3 anchor — sequence present but checkpoints implicit — rather than 4, because validation is described only generically and the only concrete check ('python scripts/encode_client.py --help') is isolated in a separate section.

3 / 5

Progressive Disclosure

Section headers give real structure and the single bundle file (scripts/encode_client.py) is correctly referenced, but the body inlines ~70 lines of generic template content that serves no navigational purpose, cites a missing 'requirements.txt', and the broken cross-reference ('See ## Usage above') hampers navigation. This matches the score-3 anchor of some structure with organization gaps; not a 2 because the core content is genuinely sectioned and the primary script path is clear.

3 / 5

Total

12

/

20

Passed

Description

87%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: third-person voice, explicit what and when, concrete actions, and domain-specific trigger terms. Minor room to broaden action and synonym coverage, but it closely matches the rubric's good examples.

DimensionReasoningScore

Specificity

The description names the domain and several concrete actions — 'search for and retrieve biological data (biosamples, experiments, etc.)', 'search by keywords', 'retrieve specific objects by accession ID'. Not a 5 because coverage is limited to search/retrieve and omits other API capabilities, leaving minor gaps.

4 / 5

Completeness

Both parts are explicit: what — 'Access the ENCODE Project REST API to search for and retrieve biological data'; when — 'Use this skill when the user needs to query ENCODE data, search by keywords, or retrieve specific objects by accession ID'. This matches the score-5 anchor with concrete trigger phrases; not below because neither half is missing or vague.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'query ENCODE data', 'search by keywords', 'accession ID', 'biosamples, experiments'. A few natural synonyms are missing (e.g., 'genomics data', 'ENCODE project annotations'), keeping it below a 5; it is clearly above a 3 because the terms present are ones a user would naturally say.

4 / 5

Distinctiveness Conflict Risk

A clear niche (the ENCODE Project REST API) with distinct, domain-locked triggers ('ENCODE data', 'accession ID', 'biosamples, experiments'); minimal overlap risk with other skills. It is not a 4 because no closely related skill would plausibly capture these triggers.

5 / 5

Total

18

/

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