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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/gwas-database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable, executable guidance with clearly sequenced workflows, but the skill is noticeably verbose and fails progressive disclosure: the referenced api_reference.md file does not exist, and its intended content is duplicated inline instead. Shipping the reference file and cutting duplicated examples would fix both weaknesses.

Suggestions

Create references/api_reference.md and move the endpoint details, field dictionaries, and repeated query examples there; keep only quick-start examples in SKILL.md so the advertised reference is real rather than dangling.

Merge sections "3. REST API Access" and "4. Query Examples and Patterns", which repeat near-identical requests.get snippets, and trim the 10-bullet "When to Use" list and Overview prose to cut token bloat.

Add validation/checkpoint steps (like the Workflow 1 error-recovery note) to Workflows 3–5, e.g., verify returned gene coordinates or confirm API status before batch pagination loops.

DimensionReasoningScore

Conciseness

The ~600-line body duplicates itself: sections "3. REST API Access" and "4. Query Examples and Patterns" repeat nearly identical requests.get snippets, and the Overview/"When to Use" sections pad with explanation (e.g., a 10-bullet use-case list and prose describing what the GWAS Catalog is). Several sections could be cut or collapsed into the reference file.

2 / 5

Actionability

Fully executable, copy-paste-ready Python with real base URLs, endpoints, parameters, pagination, and a complete query_gwas_catalog() function covering the common cases. Placeholders like GCSTXXXXXX are explicitly framed as examples, which the rubric permits.

5 / 5

Workflow Clarity

Five workflows are clearly sequenced with numbered steps, and Workflow 1 includes an error-recovery path ("If API returns non-200 status: Check EFO ID validity... fall back to web interface") plus an explicit checkpoint. Validation is lighter in Workflows 2–5, but these are read-only queries where destructive/batch feedback loops do not apply — minor gaps keep this just below 5.

4 / 5

Progressive Disclosure

The body advertises "references/api_reference.md" with a dedicated section on when to consult it, but no references/ directory exists — the single external reference is dangling. Meanwhile the bulk API-detail content (endpoints, field dictionaries, repeated examples) that belongs in that file is inlined in the ~22KB body, matching the 'content that clearly belongs in separate files is inlined' anchor despite good section headers.

2 / 5

Total

13

/

20

Passed

Description

70%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, specific description of a distinct resource with good natural trigger terms, undermined by the absence of an explicit 'Use when...' clause and a few missing synonyms. Adding a when-to-use clause and terms like "variant" and "genome-wide association" would raise it.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user mentions GWAS, SNPs, rs IDs, trait/disease associations, or genome-wide association studies."

Include common user phrasings/synonyms such as "variant", "genetic association", "genome-wide significant", and "risk allele" alongside the existing terms.

Mention study/publication metadata retrieval (PMID, GCST accessions) so the description's capability coverage matches the skill body.

DimensionReasoningScore

Specificity

"Search variants by rs ID, disease/trait, gene, retrieve p-values and summary statistics" lists several concrete, named actions. Not a 5 because coverage has minor gaps — study/publication metadata and region searches covered by the skill are absent from the description.

4 / 5

Completeness

The "what" is clear ("Query NHGRI-EBI GWAS Catalog... retrieve p-values and summary statistics") but there is no explicit "Use when..." clause; the trailing "for genetic epidemiology and polygenic risk scores" only weakly implies when. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms users would say include "SNP-trait associations", "rs ID", "p-values", "summary statistics", "polygenic risk scores". A few common variations are missing (e.g., "variant", "genome-wide association", "trait", "GWAS hit"), so it falls just short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

"NHGRI-EBI GWAS Catalog" names a specific, one-of-a-kind resource, and "SNP-trait associations" with rs IDs pins a clear niche; minimal overlap with any other skill's triggers.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

aipoch/medical-research-skills

Path

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