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.

56

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/databases/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.

A highly actionable body with executable, copy-paste-ready API examples and clearly sequenced workflows, but it is noticeably verbose — query patterns are duplicated across four sections and much endpoint/field detail duplicates the existing reference file. Consolidating duplicated examples and pushing endpoint documentation into references/api_reference.md would substantially improve token efficiency and structure.

Suggestions

Deduplicate the efoTraits associations query, which appears in 'REST API Access', 'Example 1', 'Workflow 1', and the 'Python Integration Example' — keep one canonical version and reference it elsewhere.

Move the 'Response Formats and Data Fields' section and per-endpoint examples into references/api_reference.md, keeping only one or two quick-start queries in SKILL.md.

Trim generic domain knowledge ('Be aware of winner's curse', 'Consider sample size when assessing evidence strength') that Claude already knows, retaining only GWAS Catalog-specific guidance.

DimensionReasoningScore

Conciseness

The same efoTraits associations query is repeated across section 3, Example 1, Workflow 1, and the Python Integration example, and the Resources section restates the reference file's contents. Generic statistics advice ('Consider sample size when assessing evidence strength', 'Be aware of winner's curse') explains concepts Claude already knows, matching the 'noticeably verbose' anchor rather than the 'mostly efficient' one.

2 / 5

Actionability

All examples are fully executable Python with real base URLs, parameters, response parsing, pagination with a status-code check, and p-value thresholds — copy-paste ready and covering the common cases (variant, trait, gene, region, summary statistics).

5 / 5

Workflow Clarity

The five workflows are clearly sequenced with numbered steps, and the pagination example includes an explicit status-code/empty-page checkpoint. However, validation in the workflows themselves is mostly implicit (e.g., 'Quality assessment' steps lack explicit verify checkpoints), so it does not reach the explicit feedback-loop anchor.

4 / 5

Progressive Disclosure

references/api_reference.md is real, one level deep, and clearly signaled with a 'Consult this reference when' section, but the body inlines roughly 200 lines of endpoint documentation, response-field lists, and query examples that duplicate that file. Content that should live in the reference is inline, matching anchor 3 rather than the 'minor organization gaps' of anchor 4.

3 / 5

Total

14

/

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 specific, distinctive description with concrete actions and good domain keywords, weakened by the absence of an explicit 'Use when...' trigger clause and incomplete synonym coverage. Adding trigger guidance and common phrasings would raise it to the top band.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions GWAS, genome-wide association studies, SNP-trait associations, or asks for variant-trait lookups or p-values.'

Include common user phrasings and synonyms such as 'genome-wide association study', 'variant', 'genetic association', and 'risk score' to broaden natural trigger coverage.

Mention chromosomal-region search and study metadata retrieval to close the remaining capability gaps in the 'what' statement.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Search variants by rs ID, disease/trait, gene', 'retrieve p-values and summary statistics' — but omits capabilities covered in the body such as chromosomal-region searches and study metadata retrieval, so it falls short of the comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clear (query, search, retrieve), but there is no explicit 'Use when...' clause; the trailing 'for genetic epidemiology and polygenic risk scores' only weakly implies when to use the skill, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural domain keywords are well covered ('GWAS Catalog', 'SNP', 'rs ID', 'p-values', 'polygenic risk scores'), but common user phrasings like 'genome-wide association study', 'variant', and 'risk score' are missing, placing it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Naming the unique resource 'NHGRI-EBI GWAS Catalog' with 'SNP-trait associations' gives a clear niche with distinct triggers and minimal overlap risk with other database skills.

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 (614 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

synthetic-sciences/openscience

Path

backend/cli/skills/databases/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.