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

75%

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 ./plugins/tooluniverse/skills/tooluniverse-gwas-snp-interpretation/SKILL.md

The canonical home for this skill is tooluniverse-gwas-snp-interpretation in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 content has a clear structure, concrete tool inventory, and a well-sequenced workflow, but it stops short of being directly executable: no invocation examples, validation checkpoints are implicit, the referenced QUICK_START.md is missing, and several sections (interpretation guide basics, coverage stats, generic best practices) pad the token budget without adding value.

Suggestions

Add one or two copy-paste-ready invocation examples (e.g. the actual call with rs_id="rs7903146" and expected return) instead of deferring all examples to a nonexistent QUICK_START.md.

Add explicit validation/decision checkpoints to the workflow, e.g. confirm the rsID resolved and handle an empty association list before running fine-mapping.

Trim content Claude already knows (p-value significance ladder, generic best practices, coverage statistics) and move the detailed output-format examples to a reference file to cut tokens and fix the broken QUICK_START.md reference.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes unnecessary explanation Claude already knows, such as the P-value significance ladder ("p < 5e-8: Genome-wide significant"), generic Best Practices advice ("Review Publications: Check original studies for context"), and coverage statistics ("350,000+ publications, 670,000+ associations") that earn no tokens. The Version section's dated info ("Last Updated: 2026-02-13") is time-sensitive content outside any deprecated/old-patterns section.

3 / 5

Actionability

Tool names are concrete and mapped to workflow steps (`gwas_get_snp_by_id`, `OpenTargets_get_variant_credible_sets`), but no actual invocation examples are shown — only `LDlink_get_proxies(variant="rs...", population="EUR")` appears with syntax, and it needs an undocumented LDLINK_TOKEN. The promised executable examples are deferred to `QUICK_START.md`, which does not exist in the bundle, leaving key execution details missing.

3 / 5

Workflow Clarity

The 5-step workflow diagram is clearly sequenced with a tool per step, but it contains no validation or decision checkpoints (e.g. verify the rsID resolved, handle an empty association list before proceeding). The Error Handling section describes the tool's behavior, not agent steps to take, so checkpoints remain implicit. This is a read-only lookup skill, so the destructive/batch cap does not apply.

3 / 5

Progressive Disclosure

Sections are well-organized and there are no nested references, but the body references `QUICK_START.md` for examples and that file does not exist in the bundle — a broken navigation pointer. Additionally, the inline output-format example blocks (SNP info, associations, credible sets) are content that could live in a separate reference file, and no bundle files are provided at all.

3 / 5

Total

12

/

20

Passed

Description

88%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: concrete, domain-specific, third-person, and with an explicit 'Use for' trigger clause containing natural user phrases. Its only weaknesses are a few missing common synonyms ('variant', 'rsID') and minor overlap in scope with general variant-annotation skills.

Suggestions

Add natural synonyms users might say, e.g. 'variant', 'rsID', or 'GWAS hit', to the trigger clause.

Tighten the evidence-source list (e.g. drop or downweight ClinVar/gnomAD) to reduce overlap with general variant-annotation skills and sharpen the GWAS-specific niche.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions across named sources — "GWAS Catalog hits, LD/haplotype context, eQTL evidence, regulatory annotation, ClinVar pathogenicity, gnomAD frequency" — giving comprehensive, specific coverage rather than vague language. It stays in third person ("Interpret", "Always considers"), so no voice penalty applies.

5 / 5

Completeness

It explicitly answers both questions: what ("Interpret a single GWAS SNP across multiple databases" with enumerated evidence types) and when ("Use for 'what does this SNP do', SNP-to-mechanism tracing, and resolving lead-SNP-vs-causal-variant ambiguity") with concrete trigger phrases. This matches the anchor-5 exemplar structure.

5 / 5

Trigger Term Quality

It includes natural phrases a user would actually say, notably "what does this SNP do", plus "SNP-to-mechanism tracing" and "lead-SNP-vs-causal-variant ambiguity". Coverage is good but misses common synonyms users say such as "variant", "rsID"/"rs number", or "GWAS hit", so it falls just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The GWAS SNP interpretation niche is clear and mostly distinct, but the enumerated evidence sources ("ClinVar pathogenicity, gnomAD frequency") overlap with general variant-annotation and variant-effect-prediction skills, creating minor conflict risk with closely related skills rather than minimal risk.

4 / 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

plugins/tooluniverse/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.