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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is tooluniverse-sequence-retrieval in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 retrieval workflow (Phases 0-3) is well sequenced, actionable, and backed by real tool calls, fallback chains, and error handling. However, the body bloats to ~300 lines by repeating the curation hierarchy multiple times and inlining six extended tool-catalog sections that belong in reference files, hurting both conciseness and progressive disclosure.

Suggestions

Move the extended tool catalogs (UniProt proteomes, UniParc/UniRef, BioSamples, BioThings, Bioregistry/Identifiers.org/TogoID, dbfetch) into reference files under references/, keeping one-line 'See X for Y' pointers in SKILL.md — this would cut the body by roughly half and fix progressive disclosure.

State the curation-quality hierarchy (RefSeq > RefSeq predicted > GenBank) exactly once — the Curation Level Tiers table — and delete the restatements in 'Domain Reasoning' and 'Reasoning Framework'.

Compress the 'verified live' narrative walkthroughs to the gotcha plus one compact example call/response pair, dropping the blow-by-blow test transcripts (e.g. the full SARS-CoV-2 proteome chain and EGFR UniParc narrative).

DimensionReasoningScore

Conciseness

Mostly efficient operational content, but with real padding: the curation-quality hierarchy (RefSeq > predicted > GenBank) is repeated four times (frontmatter, 'Domain Reasoning', 'Reasoning Framework', 'Curation Level Tiers'), and the long 'verified live' narrative transcripts (e.g. the SARS-CoV-2 proteome chain and EGFR UniParc walkthroughs) recount full test runs where the gotcha plus one compact example would suffice. This fits 'Mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Concrete tool calls with real parameter names and formats (tu.tools.NCBI_search_nucleotide with organism/gene/strain/keywords/seq_type/limit), explicit fallback chains, an error-to-response table, and real example invocations with actual outputs. Minor gaps keep it below fully copy-paste-ready: snippets use unbound placeholders (accession=accessions) with no complete end-to-end runnable example.

4 / 5

Workflow Clarity

Clear sequenced phases (Clarify → Disambiguate → Retrieve → Report) with an identity checklist, fallback chains, and an error-handling table forming feedback loops. Falls short of the top anchor because verification of the retrieved sequence (e.g. confirming organism/strain matches the request, per Synthesis Question 4) is posed as a question rather than an explicit checkpoint inside the workflow.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so everything lives in a ~300-line SKILL.md. Section headers are clear, but roughly half the body — the extended per-tool catalogs (UniProt proteomes, UniParc/UniRef, BioSamples, BioThings, Bioregistry/TogoID, dbfetch) — is reference material that clearly belongs in separate files with one-line pointers. This matches 'Some structure but content that should be separate is inline'.

3 / 5

Total

14

/

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: concrete, third-person, and comprehensive on capabilities, with an explicit 'Use for' clause enumerating trigger scenarios. The only minor gap is a few missing natural synonyms for how users phrase sequence-fetching requests.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions in third person: "Retrieve DNA/RNA/protein sequences from NCBI and ENA with disambiguation", "fetching specific sequences by accession, gene-symbol-to-sequence lookup, transcript-isoform retrieval, and curated-vs-raw-submission preference". This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage', and even adds a concrete quality hierarchy (RefSeq > predicted > GenBank).

5 / 5

Completeness

It explicitly answers both questions: 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 top anchor with an explicit 'Use for' clause covering concrete trigger scenarios.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say: "sequences by accession", "gene-symbol-to-sequence lookup", "transcript-isoform retrieval", "DNA/RNA/protein", plus database names NCBI and ENA. A few natural variations are missing (e.g. "get sequence", "FASTA", "fetch gene sequence"), placing it at 'Good keyword coverage; a few natural terms missing' rather than the comprehensive-with-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (biological sequence retrieval from NCBI/ENA) with distinctive vocabulary — RefSeq prefixes (NM_/NP_/XM_/XP_), GenBank, transcript isoforms — that no adjacent skill (e.g. generic search or proteomics-analysis skills) would share, minimizing wrong-skill triggering.

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

plugins/tooluniverse/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.