CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

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

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill body with concrete executable tool calls and clear fallback/error guidance. Its two weaknesses are modest redundancy between the Domain Reasoning and Reasoning Framework sections and the absence of an explicit verify-before-report checkpoint in the retrieval workflow.

Suggestions

Add an explicit validation checkpoint in Phase 2/3: before reporting, verify the returned accession, organism, and strain match the request (the skill's own 'LOOK UP DON'T GUESS' principle applies to results too, not just queries).

Merge 'Domain Reasoning' and 'Reasoning Framework' into a single section to remove the duplicated coverage of the RefSeq/GenBank hierarchy, accession guidance, and cross-database reconciliation.

Consider demoting one of the two redundant ALL-CAPS directives ('IMPORTANT' and 'LOOK UP DON'T GUESS') into a single concise rule to reduce token weight.

DimensionReasoningScore

Conciseness

The body is largely lean and table-driven with no concept-explanation padding, but the 'Domain Reasoning' and 'Reasoning Framework' sections substantially restate each other (both cover the RefSeq-over-GenBank hierarchy, accession guidance, and cross-database reconciliation), and the bold ALL-CAPS directives add token weight without proportional value, leaving it 'mostly efficient but could be tightened' rather than fully lean.

2 / 3

Actionability

It provides concrete, executable Python tool calls with named parameters (NCBI_search_nucleotide, NCBI_get_sequence, ena_get_entry), explicit fallback chains, a parameter reference, and an error-handling table, matching the level-3 'fully executable code/commands; specific examples' anchor.

3 / 3

Workflow Clarity

Phases 0-3 are clearly sequenced with decision trees, fallback chains, and an error table, but there is no validation/verification checkpoint: nothing tells Claude to confirm the retrieved sequence actually matches the requested organism/strain or accession before reporting, and the rubric caps workflow clarity at 2 when validation is missing for retrieval-style operations.

2 / 3

Progressive Disclosure

The skill is a single self-contained SKILL.md with no bundle files (references/, scripts/, assets/ are absent), and the content is organized into well-labeled one-level sections (Workflow, Phases, Tool Reference, Search Parameters Reference) with no nested references, matching the simple-skill allowance for scoring 3 on well-organized content.

3 / 3

Total

10

/

12

Passed

Description

85%

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, specific description with explicit 'Use for' trigger guidance and a clear, narrow niche. The main weakness is trigger-term quality: useful technical keywords are present but the phrasing leans toward domain jargon and accession prefixes rather than the natural terms a user would actually say.

Suggestions

Lead the 'Use for' clause with natural user phrasings (e.g. 'fetch a gene sequence', 'get a FASTA by accession', 'look up a protein sequence') before the technical scenarios.

Move the detailed accession-prefix hierarchy (XM_/XP_, RefSeq vs GenBank) out of the description and into the body; it is disambiguation detail, not a trigger.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: 'Retrieve DNA/RNA/protein sequences from NCBI and ENA with disambiguation' plus 'fetching specific sequences by accession, gene-symbol-to-sequence lookup, transcript-isoform retrieval, and curated-vs-raw-submission preference', matching the level-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

It explicitly answers both what ('Retrieve DNA/RNA/protein sequences from NCBI and ENA with disambiguation') and when via an explicit 'Use for ...' clause listing the triggering scenarios, matching the level-3 anchor for clearly answering both what AND when.

3 / 3

Trigger Term Quality

It includes relevant terms like 'sequences', 'accession', 'gene-symbol', and 'transcript-isoform', but it is heavily padded with technical jargon (e.g. 'RefSeq predicted (XM_/XP_)', 'curated-vs-raw-submission preference') and omits common natural phrasings such as 'fetch a gene sequence' or 'get a FASTA', so it sits at the 'some relevant keywords but missing common variations' level rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and clearly bounded (NCBI/ENA sequence retrieval with accession-prefix disambiguation), and its triggers are distinct enough that it is unlikely to fire for unrelated skills, matching the level-3 'clear niche with distinct triggers' anchor.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mims-harvard/ToolUniverse
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.