CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ena-database

Access the European Nucleotide Archive (ENA) via REST APIs and FTP/Aspera to search and retrieve sequences, raw reads (FASTQ), assemblies, and metadata when you have accession IDs or need metadata-driven discovery for genomics pipelines.

Quality

83%

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

68%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 delivers a fully executable, error-aware example and a sound one-level-deep reference structure, but it describes its capabilities three times across "When to Use", "Key Features", and "Implementation Details", and the bulk-download pattern lacks explicit validation checkpoints required for batch operations.

Suggestions

Merge or remove the "Key Features" section (it restates both "When to Use" and "Implementation Details") and describe rate limiting once instead of in three places.

Add explicit validation checkpoints to the search→download pattern: confirm expected run/file counts after the Portal search, and verify downloaded FASTQ file sizes or checksums before proceeding.

Trim the inline "Query parameters and outputs (practical notes)" to the minimal essential fields and defer full parameter detail to references/api_reference.md to avoid duplication.

DimensionReasoningScore

Conciseness

The capability surface is described three times over: "Key Features" bullets ("Multi-object ENA coverage", "Two primary API styles", "Operational guidance: rate limiting awareness (HTTP 429)") restate both "When to Use" and "Implementation Details", and rate limiting is covered in three places (Key Features bullet, the script's 429 backoff, and the "Rate limiting and robustness" section). No padding of concepts Claude already knows, but anchor 3 ("mostly efficient... could be tightened") fits better than 4 because the redundancy exceeds minor instances.

3 / 5

Actionability

A complete, runnable script with real endpoints ("https://www.ebi.ac.uk/ena/portal/api/search"), a concrete parameter dict (result, query, fields, format, limit), 429 backoff handling, and a run command ("python ena_example.py PRJEB1234"), plus concrete URLs for the xref and CRAM registry services. Copy-paste ready and covers the common search→fetch→taxonomy cases — anchor 5.

5 / 5

Workflow Clarity

"Recommended pipeline pattern (search → resolve → download → cache)" gives a clear sequence, and the code implicitly handles errors (429 backoff, raise_for_status, empty-results check), but the batch/bulk download workflow has no explicit validation checkpoints (e.g., verifying expected run/file counts, or downloaded FASTQ integrity/completeness). Per the rubric guideline, batch operations without validation cap workflow_clarity at 3; checkpoints are implicit in code and absent for the download stage — anchor 3, not 4.

3 / 5

Progressive Disclosure

A single, well-signaled, one-level-deep reference — "For detailed endpoint and parameter documentation, see `references/api_reference.md`" (verified to exist, 489 lines holding the full parameter tables) — with the body keeping overview, example, and operational guidance. Anchor 4 rather than 5 because "Query parameters and outputs (practical notes)" duplicates parameter detail the reference already covers, so the split is not fully clean.

4 / 5

Total

15

/

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, dense, third-person description that explicitly answers both what and when with comprehensive object-type coverage and domain-specific triggers. The only weakness is a few missing natural trigger synonyms (e.g., "download", concrete accession prefixes like SRR/ERR/PRJEB).

DimensionReasoningScore

Specificity

Concrete actions quoted: "Access the European Nucleotide Archive (ENA) via REST APIs and FTP/Aspera to search and retrieve sequences, raw reads (FASTQ), assemblies, and metadata" — search plus retrieval across all major ENA object types with explicit transport mechanisms. Matches anchor 5 ("multiple specific concrete actions; comprehensive coverage"); not 4, since both metadata-driven discovery and accession-based retrieval are named with no meaningful coverage gap.

5 / 5

Completeness

Explicit what ("Access the ENA via REST APIs and FTP/Aspera to search and retrieve sequences, raw reads (FASTQ), assemblies, and metadata") and explicit when ("when you have accession IDs or need metadata-driven discovery for genomics pipelines") with concrete trigger phrases. Anchor 5; not 4, since the when-clause is explicit and specific rather than merely present. Third-person voice is used, so no voice penalty applies.

5 / 5

Trigger Term Quality

Natural terms present: "ENA", "European Nucleotide Archive", "raw reads (FASTQ)", "accession IDs", "assemblies", "metadata", "genomics pipelines". Matches anchor 4 ("good keyword coverage; a few natural terms missing") — not 5, because common user phrasings like "download" and the accession prefixes users actually paste (SRR/ERR/PRJEB) are absent from the description.

4 / 5

Distinctiveness Conflict Risk

Names a single authoritative source ("European Nucleotide Archive (ENA)") with domain-specific triggers ("accession IDs", "genomics pipelines"), giving a clear niche with minimal conflict risk — the only conceivable overlap is a generic NCBI/SRA skill, which the explicit ENA naming avoids. Anchor 5.

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