CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gene-database

Query the NCBI Gene database via E-utilities and the NCBI Datasets API; use it when you need to search genes by symbol/ID and retrieve annotations (RefSeq, GO, location, phenotype) for single or batch gene lists.

Quality

81%

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

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 is highly actionable with verified executable commands and a sensible split between SKILL.md, two reference files, and scripts. Its weaknesses are generic API-knowledge padding, hedged phrasing, and a batch workflow lacking validation/recovery steps.

Suggestions

Trim sections that restate knowledge Claude already has: the generic HTTP 400/429 meanings and the 'Output/data formats' list; keep only API-specific mappings (e.g., 404 = Gene ID not found) to raise conciseness.

Add a validation/feedback step to the batch workflow, e.g., 'After a batch run, check the report for unresolved symbols, re-query them or flag them for manual review, and retry 429/5xx with exponential backoff' — required to lift workflow clarity above the batch-operation cap of 3.

Replace hedged phrasing ('The following examples assume the repository provides these scripts', 'If present in the repository, consult') with direct references to the files, since scripts/ and references/ both exist in the bundle.

DimensionReasoningScore

Conciseness

The commands and rate-limit specifics are tight, but the body spends tokens on knowledge Claude already has (generic HTTP 400/429 meanings, an 'Output/data formats' section restating JSON/XML/text) and hedges ('If present in the repository', 'when supported by the chosen endpoint/workflow') that add noise without adding information.

3 / 5

Actionability

Every example is a copy-paste-ready command whose flags match the actual bundled scripts (verified: --search/--organism/--id/--format, --gene-id/--symbol/--taxon/--output, --file/--ids/--organism/--output), covering search, ID retrieval, symbol+taxon fetch, and both batch modes.

5 / 5

Workflow Clarity

Per-task commands are unambiguous, but the batch annotation workflow has no validation or feedback loop (no step to verify unresolved symbols, re-query failures, or confirm output completeness), and the rubric caps batch operations without validation at 3.

3 / 5

Progressive Disclosure

Two real one-level-deep references (references/api_reference.md, references/common_workflows.md) are clearly labeled with their content and scripts are properly separated; the 'If present in the repository, consult' hedge unnecessarily obscures references that do exist.

4 / 5

Total

15

/

20

Passed

Description

87%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 with a clear what and an explicit, concrete use-when clause covering single and batch lookups. The only deductions are the second-person 'you need' phrasing, a missing synonym or two ('Entrez'), and omission of the biological-context search feature.

DimensionReasoningScore

Specificity

Multiple concrete actions are named ('search genes by symbol/ID', 'retrieve annotations (RefSeq, GO, location, phenotype)', 'single or batch gene lists'), but coverage has a minor gap (the biological-context search capability from the body is omitted) and 'use it when you need' is second-person phrasing, which the rubric penalizes by 1.

4 / 5

Completeness

Both questions are answered explicitly: 'Query the NCBI Gene database via E-utilities and the NCBI Datasets API' states the what, and 'use it when you need to search genes by symbol/ID and retrieve annotations... for single or batch gene lists' is an explicit, concrete when-clause.

5 / 5

Trigger Term Quality

Good natural-term coverage ('gene', 'symbol/ID', 'RefSeq', 'GO', 'phenotype', 'batch gene lists', 'NCBI Gene') that users would actually say; a few natural synonyms like 'Entrez' or 'gene name lookup' are missing.

4 / 5

Distinctiveness Conflict Risk

'NCBI Gene database', 'E-utilities', 'NCBI Datasets API', and 'RefSeq' define a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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