CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-sequence-retrieval

Retrieve DNA/RNA/protein sequences from NCBI and ENA with disambiguation. Quality hierarchy: RefSeq (NM_/NP_) > RefSeq predicted (XM_/XP_) > GenBank submissions. Use for fetching specific sequences by accession, gene-symbol-to-sequence lookup, transcript-isoform retrieval, and curated-vs-raw-submission preference.

Quality

78%

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 ./plugin/skills/tooluniverse-sequence-retrieval/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 core Phases 0–3 workflow is well-sequenced and actionable with concrete tool calls, fallbacks, and error handling, but the body is bloated: the curation hierarchy is repeated four times and half the file is a tangential tool catalog with verbose "verified live" anecdotes that should live in reference files. Splitting the tool catalog into references/ and de-duplicating the hierarchy would dramatically cut token cost without losing clarity.

Suggestions

Move the UniProt/UniParc/UniRef/BioSamples/BioThings/Bioregistry/TogoID/dbfetch sections into references/*.md files and keep only a one-line "Use when..." pointer per tool in SKILL.md, fixing progressive_disclosure and cutting the body roughly in half.

State the RefSeq (NM_/NP_) > predicted (XM_/XP_) > GenBank curation hierarchy exactly once (e.g., in the "Domain Reasoning" or "Curation Level Tiers" section) and delete the redundant restatements in "Reasoning Framework" and "Accession guidance".

Compress the "verified live" narrative examples into short factual bullets (input → key output → gotcha), keeping the genuinely non-obvious quirks (e.g., "Cell membrane" vs "plasma membrane", ENA 404 on RefSeq) while trimming the step-by-step recounting.

DimensionReasoningScore

Conciseness

The body is noticeably verbose in several places: the RefSeq>predicted>GenBank curation hierarchy is stated four times (frontmatter-echo in "Domain Reasoning", "Reasoning Framework", "Accession guidance", and the "Curation Level Tiers" table), and lines ~154–305 are a ~150-line catalog of tangential tools (UniParc, UniRef, BioSamples, BioThings, Bioregistry, TogoID, dbfetch) padded with long "verified live" narrative anecdotes. This fits the 2 anchor (several unnecessary/padded sections) rather than 3's "some unnecessary explanation or could be tightened".

2 / 5

Actionability

Concrete, mostly executable guidance: real tool calls with parameters ("tu.tools.NCBI_search_nucleotide(operation="search", organism=..., limit=10)"), a parameter reference ("format (fasta/genbank)"), fallback chains, and an error→response table with verified real outputs. Not 5 because the tooluniverse/"tu.tools" context is never established and result-structure assumptions like result["data"]["uids"] cannot be verified as copy-paste ready.

4 / 5

Workflow Clarity

A clear Phase 0→3 sequence with explicit skip conditions, an identity checklist, fallback chains, and an error-handling table, plus the "LOOK UP DON'T GUESS: Never assume accession numbers... Always retrieve and verify" directive. It fits 4 (clear sequence, most checkpoints present) rather than 5 because recovery is table-based rather than an explicit validate→fix→retry loop, and rather than 3 because checkpoints and fallbacks are explicitly present.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the entire ~305-line body is inline — including a "Tool Reference", "Search Parameters Reference", and ~150 lines of tangential Uni*/dbfetch tool documentation that clearly belongs in separate reference files, with zero pointers to any external file. This matches the 2 anchor (content that clearly belongs in separate files is inlined) rather than 3, since there are no separate-file references at all, only inline bulk.

2 / 5

Total

12

/

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 description: it names concrete actions, an explicit "Use for..." clause with four trigger scenarios, and a distinctive database/accession framing that separates it from neighboring skills. The only weakness is a couple of stilted trigger phrases and a few missing natural synonyms (e.g., FASTA).

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with named databases and identifier conventions: "Retrieve DNA/RNA/protein sequences from NCBI and ENA with disambiguation", "fetching specific sequences by accession", "gene-symbol-to-sequence lookup", "transcript-isoform retrieval". Coverage is comprehensive rather than having only minor gaps, matching the 5 anchor; it is not 4 because the action list spans the skill's full use-case space.

5 / 5

Completeness

Explicitly answers both: "what" ("Retrieve DNA/RNA/protein sequences from NCBI and ENA with disambiguation") and "when" ("Use for fetching specific sequences by accession, gene-symbol-to-sequence lookup, transcript-isoform retrieval, and curated-vs-raw-submission preference"). This mirrors the 5 anchor's structure of concrete trigger phrases attached to an explicit Use-when clause.

5 / 5

Trigger Term Quality

Good natural-term coverage: "DNA", "RNA", "protein sequences", "accession", "transcript isoform", "RefSeq", "GenBank", "NCBI", "ENA". However, phrases like "gene-symbol-to-sequence lookup" and "curated-vs-raw-submission preference" are stilted rather than what a user would naturally say, and common phrasings such as "FASTA" or "get the gene sequence" are missing — fitting the 4 anchor (good coverage, a few natural terms missing) rather than 5 (comprehensive including synonyms).

4 / 5

Distinctiveness Conflict Risk

A clear niche (sequence retrieval from NCBI/ENA with a curation hierarchy) with distinctive triggers like "accession", "RefSeq", "transcript-isoform". The database names and accession-prefix framing separate it from generic gene-annotation or document skills, so conflict risk is minimal — matching the 5 anchor rather than 4's "minor overlap risk with closely related skills".

5 / 5

Total

19

/

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

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-sequence-retrieval/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.