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.
76
66%
Does it follow best practices?
Impact
96%
1.09xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/gwas-database/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, domain-specific skill description with excellent specificity and trigger term coverage for genetic research users. The main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The technical terminology is appropriate for the target audience but the description would benefit from explicit trigger guidance.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about genetic variants, SNP associations, GWAS data, or needs to look up rs IDs and their trait associations.'
Consider adding common user phrasings like 'look up a variant', 'find associations for a gene', or 'check if SNP is associated with disease' to capture natural query patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Query NHGRI-EBI GWAS Catalog', 'Search variants by rs ID, disease/trait, gene', 'retrieve p-values and summary statistics'. Also mentions specific use cases like 'genetic epidemiology and polygenic risk scores'. | 3 / 3 |
Completeness | Clearly answers 'what' (query GWAS Catalog, search variants, retrieve statistics) but lacks an explicit 'Use when...' clause. The use cases are implied through domain terms but not explicitly stated as triggers. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users in this domain would use: 'GWAS', 'SNP', 'rs ID', 'disease/trait', 'gene', 'p-values', 'summary statistics', 'polygenic risk scores', 'genetic epidemiology'. These are the exact terms researchers would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific database name (NHGRI-EBI GWAS Catalog) and domain-specific terminology (SNP, rs ID, GWAS, polygenic risk scores). Very unlikely to conflict with other skills due to its narrow, specialized focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable guidance for querying the GWAS Catalog with excellent executable code examples. However, it is severely bloated with unnecessary explanations of concepts Claude already knows (what GWAS is, what APIs are, basic Python patterns) and lacks the validation checkpoints needed for robust API workflows. The content would benefit from aggressive trimming and better file organization.
Suggestions
Reduce the Overview and 'When to Use This Skill' sections to 2-3 sentences each - Claude understands genomics concepts and can infer appropriate use cases
Add explicit validation steps to workflows: check response.status_code, validate expected fields exist, handle rate limiting errors with retry logic
Move the five detailed workflows and the 'Python Integration Example' to a separate workflows.md file, keeping only a quick-start example in the main skill
Remove explanatory text like 'The GWAS Catalog is a comprehensive repository...' and 'PDF (Portable Document Format)'-style explanations throughout
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Includes extensive explanations Claude already knows (what GWAS is, what EFO ontology is, basic Python requests patterns). The overview section alone could be reduced by 80%. Many sections repeat similar information. | 1 / 3 |
Actionability | Provides fully executable Python code examples with proper imports, error handling patterns, and copy-paste ready snippets. API endpoints are concrete with real URLs and parameters. Examples cover common use cases comprehensively. | 3 / 3 |
Workflow Clarity | Five detailed workflows are provided with clear sequences, but they lack explicit validation checkpoints. No verification steps for API responses (checking status codes consistently), no error recovery patterns, and no feedback loops for failed queries. | 2 / 3 |
Progressive Disclosure | References an external 'references/api_reference.md' file appropriately, but the main skill file is monolithic with ~500 lines of content that should be split. The 'When to Use This Skill' section and extensive workflow details could be separate files. | 2 / 3 |
Total | 8 / 12 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (607 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 9 / 11 Passed | |
71add64
Table of Contents
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.