CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-gwas-snp-interpretation

Interpret a single GWAS SNP across multiple databases — GWAS Catalog hits, LD/haplotype context, eQTL evidence, regulatory annotation, ClinVar pathogenicity, gnomAD frequency. Use for 'what does this SNP do', SNP-to-mechanism tracing, and resolving lead-SNP-vs-causal-variant ambiguity. Always considers LD structure before claiming a SNP is mechanistically responsible.

Quality

80%

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 ./plugin/skills/tooluniverse-gwas-snp-interpretation/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 delivers a clear five-step workflow with concrete tools, parameters, and realistic output examples, and honest limitations. Its weaknesses are moderate verbosity (textbook p-value thresholds, a redundant Overview, a dated version block), invocation examples for only one of four tools, and a broken QUICK_START.md reference with no other progressive-disclosure structure.

Suggestions

Fix the dangling reference: either ship a QUICK_START.md in references/ or inline the one or two concrete tool-call examples it was meant to hold (e.g., gwas_get_snp_by_id(rs_id='rs7903146')).

Move the output-format JSON schemas and the Interpretation Guide (p-value/L2G thresholds) into a references/ file, keeping SKILL.md as a lean overview with well-signaled one-level-deep links.

Cut content Claude already knows (the 5e-8 genome-wide significance threshold explanation) and remove or relocate time-sensitive version/date details so the main body stays evergreen.

DimensionReasoningScore

Conciseness

Mostly efficient tool-specific content (parameters, output shapes, tool names), but it includes material Claude already knows — the standard 'p < 5e-8 genome-wide significant' thresholds — plus an 'Overview' section that restates the description and a 'Version' block with time-sensitive dates ('Last Updated: 2026-02-13'). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' (3); it is not severely padded (2) nor free of trimmable content (4).

3 / 5

Actionability

Concrete tool names, parameter definitions with defaults, realistic output JSON examples, and one full call signature (`LDlink_get_proxies(variant="rs...", population="EUR")`) make the guidance mostly executable. It falls short of 5 because the main workflow tools (gwas_get_snp_by_id, gwas_get_associations_for_snp, OpenTargets_get_variant_credible_sets) never get an actual invocation example, and 'See QUICK_START.md' points to examples that are not in the bundle.

4 / 5

Workflow Clarity

The five-step workflow diagram sequences each step with its tool, marks step 3 as optional, and an Error Handling section covers invalid rsID, empty results, and API failures — a clear sequence with most checkpoints present. It is not 5 because validation is described declaratively rather than as explicit check-then-branch steps in the workflow (e.g., what to do when OpenTargets needs chr_pos_ref_alt conversion, per Limitation #1).

4 / 5

Progressive Disclosure

The body is well-sectioned but self-contained at ~220 lines with output-format schemas and interpretation guidance inlined that could live in reference files, and its single outward reference — 'See `QUICK_START.md` for platform-specific examples' — points to a file that does not exist in the bundle (no references/, scripts/, or assets/ directories). This matches 'some structure but ... references present but not clearly signaled; content that should be separate is inline' (3).

3 / 5

Total

14

/

20

Passed

Description

87%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 description: it names a precise niche, enumerates six concrete evidence sources, and includes explicit natural-language trigger phrases plus a distinctive LD-caution framing. The only gaps are a single generic action verb where multiple concrete actions could be listed, and a few missing common trigger synonyms (rsID, variant, pathogenic).

DimensionReasoningScore

Specificity

Enumerates concrete evidence domains — 'GWAS Catalog hits, LD/haplotype context, eQTL evidence, regulatory annotation, ClinVar pathogenicity, gnomAD frequency' — giving broad, specific coverage, but the action verb is a single generic one ('Interpret') with no distinct retrieval/prioritization actions, so it sits between the 'several specific actions' (4) and 'multiple concrete actions; comprehensive' (5) anchors.

4 / 5

Completeness

Both questions are answered explicitly: the 'what' is the interpretation of a SNP across six named database evidence types, and the 'when' is an explicit 'Use for ...' clause with concrete trigger phrases. This matches the score-5 anchor exactly; score 4 would require the 'when' to be less explicit or specific, which it is not.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — "Use for 'what does this SNP do', SNP-to-mechanism tracing, and resolving lead-SNP-vs-causal-variant ambiguity" — which map well to how users phrase SNP questions, but common variations like 'rsID', 'variant', or 'pathogenic' are missing, matching the 'good keyword coverage; a few natural terms missing' (4) anchor rather than the fully comprehensive one.

4 / 5

Distinctiveness Conflict Risk

The GWAS-SNP-interpretation niche with named databases (GWAS Catalog, ClinVar, gnomAD) and a distinctive concern ('Always considers LD structure before claiming a SNP is mechanistically responsible') gives it a clear, well-bounded trigger surface with minimal overlap risk against adjacent genetics skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-gwas-snp-interpretation/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.