CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dbsnp-database

Use when you want to look up, map, and search for short genetic variants (SNPs, indels) in NCBI's dbSNP database. Resolves between rsIDs, genomic coordinates in VCF format, and HGVS strings. For an rsID, returns variant type, gene associations, clinical significance, allele frequencies, and genomic coordinates (GRCh38).

Quality

84%

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

71%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.

A highly actionable, well-structured CLI reference with executable examples for every command, real-world workflows, and thoughtful mistake-proofing (assembly fallback, truncation handling, HTTP 500 recovery). Its weaknesses are systematic redundancy — the same warnings repeated across Core Rules, callouts, and Common Mistakes — and bundle references (api-notes.md, citation.bib) that exist on disk but are never signaled from SKILL.md, leaving them effectively unreachable.

Suggestions

Consolidate repeated warnings: state each caution (search-region vs. resolve-variant, HGVS quoting, X/Y numeric chromosomes, --full payload size, assembly fallback) once in its most relevant location and have the Common Mistakes section reference rather than restate them.

Add a short 'References' section pointing to references/api-notes.md (NCBI endpoint details) and references/citation.bib (how to cite dbSNP) so the bundle files are discoverable from SKILL.md.

Add explicit validation steps to the Typical Workflows (e.g., 'verify the rsids array is non-empty before calling get-variant; if empty, check the assembly and ref allele per the troubleshooting section') to close the feedback loop.

DimensionReasoningScore

Conciseness

Mostly dense, skill-specific operational detail (assembly accessions, X=23/Y=24 conventions, retmax ceilings), but the same cautions are systematically repeated: the search-region warning appears in Core Rules, the CAUTION callout, and Common Mistakes; HGVS quoting and the X/Y chromosome rule each appear three times; the API-key/credentials instructions and --full warning are each stated twice. This goes beyond "minor instances that could be trimmed" (anchor 4), fitting anchor 3's "could be tightened".

3 / 5

Actionability

Every subcommand has copy-paste-ready invocations with real example values (`uv run scripts/dbsnp_cli.py resolve-variant 8 19962213 C T --output /tmp/resolve.json`), explicit argument lists with defaults, expected output JSON shapes, and worked two-step workflows covering the common cases. Not 4 because there are no gaps — even edge conventions (numeric X/Y chromosomes, quoting HGVS) are given as executable specifics.

5 / 5

Workflow Clarity

Multi-step workflows (resolve → get-variant, HGVS → rsID → coordinates) are clearly sequenced, and error recovery is addressed via the HTTP 500 troubleshooting section ("DO NOT RETRY... switch assembly") and the search-region truncated/note feedback. Not 5 because the workflow steps themselves lack explicit validation checkpoints (e.g., "check rsids is non-empty before running get-variant"); not 3 because checkpoints and recovery paths are largely present, just implicit in the workflows.

4 / 5

Progressive Disclosure

The body is well-structured (prerequisites, command selection guide, per-command sections, workflows, troubleshooting), and the wrapper script is consistently referenced, but the bundle's references/api-notes.md (endpoint/API implementation details) and references/citation.bib are never mentioned anywhere in SKILL.md — verified by grep — so those files are undiscoverable. This matches anchor 3: "references present but not clearly signaled", rather than 2, since the body itself has strong organization and nothing that belongs in a separate file is inlined.

3 / 5

Total

15

/

20

Passed

Description

91%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, domain-precise actions with explicit "Use when" trigger guidance and comprehensive natural keywords (rsID, SNP, HGVS, VCF, dbSNP). The only deductions are the second-person phrasing ("you want to") and minor overlap risk on the clinical-significance claim. The skill's actual scope boundaries (vs. ClinVar/gnomAD siblings) are well documented in the body but not reflected in the description itself.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage — "look up, map, and search for short genetic variants (SNPs, indels)", "Resolves between rsIDs, genomic coordinates in VCF format, and HGVS strings", and returns "variant type, gene associations, clinical significance, allele frequencies, and genomic coordinates (GRCh38)" — which matches the anchor-5 example's breadth. However, the description uses second person ("Use when you want to..."), which per the judging guidelines reduces the specificity score by 1.

4 / 5

Completeness

Explicitly answers both: what ("Resolves between rsIDs, genomic coordinates in VCF format, and HGVS strings... returns variant type, gene associations, clinical significance, allele frequencies") and when ("Use when you want to look up, map, and search for short genetic variants"). Matches the anchor-5 example structure with concrete trigger guidance, so not 4.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms: "genetic variants", "SNPs", "indels", "dbSNP", "rsIDs", "VCF", "HGVS", "allele frequencies", "clinical significance", "genomic coordinates (GRCh38)" — exactly the terms a user needing dbSNP lookups would say. Not 4 because no commonly-used variant-domain trigger phrase is missing; users in this domain ask with precisely these identifiers and formats.

5 / 5

Distinctiveness Conflict Risk

The dbSNP/rsID-resolution niche is distinct with clear triggers (rsID, VCF, HGVS lookups), but advertising "clinical significance" as a returned field creates minor overlap with a dedicated ClinVar-style skill, matching "mostly distinct; minor overlap risk with closely related skills". Not 5 because the clinical-significance claim could pull pathogenicity-focused queries that belong to a sibling skill; not 3 because the core identifier-resolution triggers are unambiguous.

4 / 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

google-deepmind/science-skills

Path

skills/dbsnp_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.