CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ncbi-sequence-fetch

Retrieve protein and nucleotide sequences from NCBI databases using E-utilities. Supports direct accession lookup, CDS translation, gene+organism search, locus lookup, PubMed-linked sequences, patent protein extraction, and organism+length fallback search. Use when you need to fetch biological sequences by accession, gene name, locus tag, PubMed ID, or patent number.

Quality

86%

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

75%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 well-structured, executable reference: every subcommand has concrete commands, a clear retrieval cascade orders the workflows, and result-selection criteria are spelled out. Weaknesses are cosmetic but real — duplicated subcommand listings, two broken code/markdown blocks in sections 3 and 9, and an orphaned bundle file (references/citation.bib) that is never surfaced to the reader.

Suggestions

Fix the malformed code fences in the Patent Sequence Search section (the two `uv run ... patent-search` examples are inline text, not fenced bash blocks) and the broken numbered list in the CDS Translate section so all examples are copy-paste executable.

Eliminate the duplication between the Overview's 10-item subcommand list and the Utility Scripts section — keep the overview as a one-line index of names only, or drop it and let the section headers serve as the index.

Reference references/citation.bib in the body (e.g., a line in the Reference or Core Rules section noting when to cite the Sayers 2025 E-utilities paper), since it is a provided bundle file that is currently undiscoverable.

DimensionReasoningScore

Conciseness

The body is largely tight — each subcommand gets one descriptive line plus executable commands, and it never explains concepts Claude already knows (no 'what is NCBI' padding). Minor inefficiencies: the Overview re-lists all 10 subcommands that the Utility Scripts section then re-describes, and the Prerequisites section runs long. Fits 'efficient; minor instances that could be trimmed' rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Nearly all guidance is copy-paste ready: 'uv run scripts/ncbi_fetch.py fetch-protein XP_022033624 -o /tmp/result.json' and similar concrete invocations with real flags for every subcommand. Section 9's patent examples are mangled ('`bash uv run scripts/ncbi_fetch.py patent-search --patent-number US10123456...' rendered as inline code instead of fenced blocks) and section 3's numbered method list is broken markdown, so a couple of examples are not cleanly executable — minor gaps, not missing steps.

4 / 5

Workflow Clarity

A clear 7-step 'Standard Sequence Retrieval Cascade' sequences the subcommands by priority, and 'Interpreting Results' gives explicit selection criteria (target_length match, header relevance, 'RefSeq > GenPept > patent' source priority) plus fallback guidance ('If the accession is a genomic record... fall back to a homology-based approach'). It stops short of explicit verify checkpoints per step (e.g., 'confirm returned length matches expected before returning'), matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

Good structure: the body clearly signals 'scripts/ncbi_fetch.py — Single script with subcommands' (a real, verified bundle file) and organizes the 10 subcommands under headed sections with an overview index. However, the bundle's references/citation.bib (the Sayers 2025 E-utilities citation) is never mentioned anywhere in the body — an unreferenced bundle file — a minor organization/navigation gap that keeps it below the well-signaled-references anchor.

4 / 5

Total

16

/

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 example: it states a concrete capability set in third person, explicitly names the data source and mechanism, and closes with an explicit 'Use when...' trigger clause enumerating the natural lookup terms. The only gap is a handful of missing synonyms (FASTA, retrieve) that keeps trigger coverage just short of comprehensive.

DimensionReasoningScore

Specificity

Quotes: 'Supports direct accession lookup, CDS translation, gene+organism search, locus lookup, PubMed-linked sequences, patent protein extraction, and organism+length fallback search' — seven concrete, distinct capabilities plus a specific mechanism ('using E-utilities'), comprehensively covering the tool's subcommands with no vague filler. Third person voice throughout ('Retrieve', 'Supports').

5 / 5

Completeness

Explicitly answers both questions: 'what' — 'Retrieve protein and nucleotide sequences from NCBI databases using E-utilities' with enumerated capabilities; 'when' — 'Use when you need to fetch biological sequences by accession, gene name, locus tag, PubMed ID, or patent number' with concrete trigger phrases. This mirrors the 5-anchor example structure.

5 / 5

Trigger Term Quality

Quotes: 'fetch biological sequences by accession, gene name, locus tag, PubMed ID, or patent number' plus 'protein and nucleotide sequences from NCBI' — natural phrases users would say, covering the main lookup vectors. A few natural synonyms are missing (e.g., 'FASTA', 'Entrez', 'retrieve/download sequence'), keeping it just below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Quotes: 'from NCBI databases using E-utilities' and 'by accession, gene name, locus tag, PubMed ID, or patent number' — a clear niche (NCBI sequence retrieval) with distinct, domain-anchored triggers; minimal overlap risk with other bioinformatics skills.

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