CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gwas-database

Query NHGRI-EBI GWAS Catalog for SNP-trait associations. Search variants by rs ID, disease/trait, gene, retrieve p-values and summary statistics, for genetic epidemiology and polygenic risk scores.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/gwas-database/SKILL.md
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 body is highly actionable with executable REST API examples and well-sequenced workflows, but it suffers from duplication with its own reference file and padding that inflates token cost. The main structural fix is pushing the detailed endpoint/field reference content into the already-existing api_reference.md and trimming concept explanations and repeated URL listings. Removing the promotional K-Dense section would also improve token efficiency.

Suggestions

Move the detailed endpoint specifications, response field tables, and duplicated code examples out of SKILL.md and into references/api_reference.md, keeping only a quick-start example and the clearly signaled pointer that already exists.

Trim padding: the Overview's explanation of what the GWAS Catalog is, the generic external-resource listings (Ensembl, dbSNP, gnomAD), the three repeated URL/resource sections, and the promotional K-Dense Web section.

Add brief error-recovery guidance to the workflows (e.g., what to do on non-200 responses or empty result pages) to close the feedback-loop gap.

DimensionReasoningScore

Conciseness

The core endpoint, field, and pagination documentation earns its place, but the body pads with content Claude already knows (the Overview's explanation of what the GWAS Catalog is, the generic Ensembl/dbSNP/gnomAD resource listings), repeats the same URLs across three sections, includes near-duplicate code examples, and ends with a promotional K-Dense section. This is more than 'some' tightening but the bulk is genuinely domain-specific, so it sits at 3 rather than 2.

3 / 5

Actionability

Mostly executable guidance: real endpoints with concrete params, HAL `_embedded` response parsing, pagination handling, and a complete copy-paste pandas pipeline with rate limiting. Minor gaps keep it from 5 — placeholder accessions like 'GCSTXXXXXX', and the summary-statistics download example that is mostly comments rather than working code.

4 / 5

Workflow Clarity

Five clearly sequenced numbered workflows with checkpoints (significance filtering, quality assessment, status-code checks in the integration example) cover the main use cases. It falls short of 5 because the workflows lack explicit error-recovery/feedback loops; queries are read-only so the destructive/batch validation cap does not apply.

4 / 5

Progressive Disclosure

The bundle contains references/api_reference.md (793 lines) which is clearly signaled with a descriptive section and 'Consult this reference when...' guidance, but the body inlines ~250 lines of endpoint specs, field tables, and code examples that substantially duplicate that reference file (endpoints, pagination, HAL links). This matches anchor 3 — content that should be separate is inline — rather than 4, because the split leaves significant duplication.

3 / 5

Total

14

/

20

Passed

Description

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

The description is specific and domain-distinct, naming the GWAS Catalog and several concrete query capabilities with natural bioinformatics keywords. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness at 3 and leaves the activation conditions implicit. Adding an explicit when-clause with common trigger phrases would raise it to the strong tier.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user mentions GWAS, SNP associations, rs IDs, genome-wide association studies, or polygenic risk scores.'

Include common synonyms and phrasings users actually say — 'variant', 'genome-wide association', 'trait association', 'GWAS' — to improve trigger term coverage.

Mention study/publication metadata retrieval to close the minor coverage gap in stated capabilities.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Search variants by rs ID, disease/trait, gene', 'retrieve p-values and summary statistics') with only minor gaps in coverage (no mention of study metadata or region searches), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive-coverage anchor at 5.

4 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance; the trailing 'for genetic epidemiology and polygenic risk scores' is purpose framing, not a when-trigger, which per the rubric caps completeness at 3. It is not a 4 because the when is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('SNP-trait associations', 'rs ID', 'disease/trait', 'p-values', 'polygenic risk scores'), but common variations like 'variant', 'genome-wide association', and 'GWAS' as a standalone trigger word are missing, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The NHGRI-EBI GWAS Catalog niche with distinct triggers (rs IDs, SNP-trait associations, p-values) is mostly distinct with only minor overlap risk against PGS Catalog or general variant-annotation skills, fitting the 'mostly distinct; minor overlap risk' anchor rather than the minimal-conflict anchor at 5.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (608 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

googolme/run0204

Path

scientific-skills/gwas-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.