CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gnomad-database

Query the Genome Aggregation Database (gnomAD). Use when determining the rarity or allele frequency of specific genetic variants, retrieving gene constraint metrics (pLI, LOEUF) to assess loss-of-function intolerance, finding variants in a genomic region or gene, or querying structural variants. Don't use for analyzing individual patient genomes, tracking somatic mutations in cancer (use COSMIC), or requesting raw sequencing reads (use ENA).

Quality

95%

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

90%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 tight, highly actionable reference skill: executable verified commands, gnomAD-specific data semantics only where needed, and clean sections. The only gaps are the absence of query-failure/validation guidance and an unreferenced bundled citation file.

Suggestions

Add a brief validation step after each query, e.g. 'Check the output JSON for an "error" key or empty results before reporting frequencies; retry after the script's rate-limit backoff if the request failed.'

Reference the bundled citation in the References section (e.g. 'Cite gnomAD as described in references/citation.bib when using results in reports') so the file is discoverable from SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean and operational: prerequisites, two core rules, three command templates, and two reference URLs. The only explanatory material (the FAF definition and the 'oe_lof_upper' field mapping for LOEUF) is gnomAD-specific API/data semantics Claude would not know, so every token earns its place. It does not match the level-4 anchor since there is no over-explanation to trim.

5 / 5

Actionability

Fully executable, copy-paste-ready 'uv run' commands for all three scripts with real flags, output paths, and input-format examples ('1-55516888-G-GA', 'rs1800562'); the documented flags match the actual script CLIs in the bundle. Matches the top anchor of executable commands covering the common cases.

5 / 5

Workflow Clarity

Prerequisites are sequenced with a conditional checkpoint (license file exists → notify → record), and each query usage is unambiguous. However, there is no validation or error-recovery guidance for query outcomes (e.g., inspecting the output JSON for API errors or empty results), so it fits 'clear sequence with most checkpoints present; minor validation gaps' rather than the top anchor requiring explicit validation steps and feedback loops.

4 / 5

Progressive Disclosure

Good structure: clear sections, scripts clearly signaled with absolute paths and per-script usage, and external documentation links. The body is ~60 lines (outside the under-50-line exception), and the bundled references/citation.bib is never mentioned in SKILL.md, so one reference is undiscoverable — a minor organization gap that fits the level-4 anchor rather than 'easy navigation' with all references well-signaled.

4 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete capability list, explicit natural-language triggers, and clear negative boundaries that disambiguate neighboring databases. Third-person voice is used throughout and nothing is padded.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'determining the rarity or allele frequency of specific genetic variants', 'retrieving gene constraint metrics (pLI, LOEUF)', 'finding variants in a genomic region or gene', 'querying structural variants' — comprehensively covering gnomAD's query capabilities. This matches the anchor for multiple specific concrete actions with comprehensive coverage, not the level below (which allows minor gaps).

5 / 5

Completeness

Explicitly answers both 'what' (query gnomAD for allele frequencies, constraint metrics, region variants, structural variants) and 'when' via a concrete 'Use when determining...' clause with multiple trigger phrases. It also adds explicit 'Don't use for...' boundaries, clearly matching the top anchor rather than the level 4 anchor where 'when' could be more specific.

5 / 5

Trigger Term Quality

Covers the natural terms users would say for this domain: 'rarity', 'allele frequency', 'pLI', 'LOEUF', 'loss-of-function intolerance', 'genomic region', 'structural variants', 'gnomAD', plus the full database name. Synonym coverage (rarity/allele frequency, pLI/LOEUF/loss-of-function) is thorough, so it fits the comprehensive-coverage anchor rather than 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (gnomAD population genetics queries) with distinct domain triggers, and it explicitly disambiguates adjacent skills ('use COSMIC' for somatic cancer mutations, 'use ENA' for raw sequencing reads). Minimal conflict risk, matching the top anchor.

5 / 5

Total

20

/

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