CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

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 ./plugin/skills/tooluniverse-gwas-snp-interpretation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and domain-accurate but verbose and lacks executable end-to-end examples. It also references a QUICK_START.md file that is absent from the bundle, weakening progressive disclosure.

Suggestions

Replace sample output-payload code blocks with executable tool-call examples (e.g., a complete call to gwas_get_snp_by_id and OpenTargets_get_variant_credible_sets with the rs_id argument) so the guidance is copy-paste ready.

Add explicit validation checkpoints to the workflow (e.g., after association search, confirm genome-wide significance before querying credible sets) to create feedback loops between steps.

Trim generic prose and the sample-payload Output Format section, and either create the referenced QUICK_START.md or remove the dangling reference to it.

DimensionReasoningScore

Conciseness

The ~220-line body restates concepts Claude already knows (e.g., 'a GWAS hit is a REGION, not a single causal variant', 'Associations don't prove causation') and pads with full sample output payloads and generic Best Practices; accurate and useful but could be tightened considerably.

2 / 3

Actionability

Concrete tool names with parameters and decision thresholds are provided (e.g., LDlink_get_proxies(...), P-value and L2G score bands), but the code blocks are sample output payloads rather than complete executable tool calls, leaving guidance incomplete.

2 / 3

Workflow Clarity

A clear 5-step workflow maps each step to a specific tool, but there are no explicit validation checkpoints or feedback loops between steps to verify intermediate results before proceeding.

2 / 3

Progressive Disclosure

Content is organized into sections but is monolithic — all material is inline in SKILL.md with no real bundle files, and the referenced QUICK_START.md does not exist in the bundle, leaving a dangling reference.

2 / 3

Total

8

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and clearly distinguishes the skill's niche. It explicitly covers both what it does and when to use it. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities and databases — 'GWAS Catalog hits, LD/haplotype context, eQTL evidence, regulatory annotation, ClinVar pathogenicity, gnomAD frequency' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (interpret a SNP across multiple databases) and when ('Use for ...') with explicit trigger guidance, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Includes natural phrases users would say such as "'what does this SNP do'" and 'SNP-to-mechanism tracing', giving good coverage of likely trigger terms rather than only technical jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (GWAS SNP interpretation) with distinct triggers unlikely to fire for unrelated skills, rather than a generic overlap-prone description.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mims-harvard/ToolUniverse
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.