CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-gwas-finemapping

Statistical fine-mapping of GWAS loci using credible sets (SuSiE, FINEMAP) and locus-to-gene scoring (Open Targets L2G). Identifies likely causal variants and target genes — distinct from positional 'nearest gene' which is often wrong. Use for prioritizing causal variants at GWAS hits, comparing fine-mapping methods, and converting lead SNPs to target genes.

Quality

81%

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

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 strong domain-specific reasoning frameworks and decision thresholds that are hard to reconstruct from general knowledge, but suffers from redundancy (two overlapping reasoning chains, a Key Concepts section teaching basics Claude already knows), a long time-sensitive dead-API digression, and a fully inlined structure with no progressive disclosure into reference files. The one broken internal cross-reference ("Limitations section above") adds minor confusion.

Suggestions

Merge the "REASONING STRATEGY — Start Here" chain into the "Fine-Mapping Reasoning Framework" (they cover the same LD-first → functional-tiebreak → eQTL-bridge logic) and delete the "Key Concepts" section, which defines credible sets and posterior probability Claude already knows.

Move the dead GWASSumStats_* tool narrative into a short 'Deprecated tools' callout (one sentence plus the deprecation link), and fix the incorrect cross-reference that calls the Limitations section "above" when it appears below the DIY tools section.

Split the tool catalog, DIY calculator details, and PP/L2G interpretation tables into reference files (e.g. references/tools.md, references/interpretation.md) referenced one level deep from SKILL.md, keeping the main file a lean overview and reasoning framework.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious domain guidance (r² thresholds, PP and L2G interpretation bands, tiebreaker ordering), but it is padded: the "Key Concepts" section defines credible sets and posterior probability Claude already knows, the "REASONING STRATEGY — Start Here" chain duplicates the "Fine-Mapping Reasoning Framework" Steps 1–5 (LD first → functional tiebreak → eQTL bridge), and the dead-API paragraph is long and time-sensitive ("as of this writing") without being framed as a deprecated section. Mostly efficient with some clearly trimmable material — fits anchor 3 better than anchor 2, since the padding is a minority of the file.

3 / 5

Actionability

Concrete, executable guidance throughout: named tool calls with explicit actions ("Always call OpenTargets_get_variant_credible_sets... If the posterior probability is < 0.5..."), calculator tools with full parameter signatures, and verified live outputs. This is an instruction/tool-orchestration skill, so the absence of runnable code is acceptable per the rubric's scoring notes; the minor gap is that the calculator signatures (beta=[...], se=[...]) are placeholders rather than copy-paste ready, and no worked Python example is shown despite the "COMPUTE, DON'T DESCRIBE" directive.

4 / 5

Workflow Clarity

A clear 5-step sequence (lead SNP vs causal → LD structure → credible set analysis → colocalization → tiebreakers) with explicit decision checkpoints at each step ("If the posterior probability is < 0.5, the lead SNP is likely NOT causal", L2G thresholds of 0.7/0.5/0.3). This is not a destructive or batch operation, so no validation cap applies; what keeps it at 4 rather than 5 is the absence of any validate/fallback loop for the anticipated failure path where a locus has no precomputed credible set — the branch is described but not sequenced.

4 / 5

Progressive Disclosure

No bundle files exist and the ~185-line body is monolithic: well-organized section headers aid navigation, but everything — the tool catalog, DIY calculator details, interpretation bands, FAQ, and references — is inlined in SKILL.md with no one-level-deep reference files. Content that clearly belongs in separate files (tool reference, interpretation guide) is inline, matching anchor 3; there is also an incorrect cross-reference ("This skill's 'Limitations' section above" at the DIY section — Limitations appears below it).

3 / 5

Total

14

/

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, comprehensive capabilities with named methods, an explicit "Use for..." trigger clause, and a deliberate differentiator from the nearest-gene heuristic. Its only notable gap is the omission of natural trigger terms (colocalization, eQTL) that its own body tools cover, and slight overlap with a sibling skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with named methods: "Statistical fine-mapping of GWAS loci using credible sets (SuSiE, FINEMAP)", "locus-to-gene scoring (Open Targets L2G)", "identifies likely causal variants and target genes", plus "prioritizing", "comparing fine-mapping methods", and "converting lead SNPs to target genes". Coverage of the skill's capabilities is comprehensive with no gaps.

5 / 5

Completeness

Explicitly answers "what" (fine-mapping of GWAS loci via credible sets, L2G scoring, identifying causal variants and target genes) and "when" ("Use for prioritizing causal variants at GWAS hits, comparing fine-mapping methods, and converting lead SNPs to target genes") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural domain phrases users would say: "fine-mapping", "GWAS", "credible sets", "causal variants", "lead SNPs", "GWAS hits", "target genes". However, "colocalization" and "eQTL" — natural entry points the skill's own tooling covers (Coloc_abf_test, S-PrediXcan) — are absent, so a few common terms are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (GWAS fine-mapping / causal variant prioritization) with an explicit differentiator ("distinct from positional 'nearest gene'"), but "comparing fine-mapping methods" and the skill's colocalization/TWAS tooling overlap with the sibling tooluniverse-eqtl-colocalization skill, creating minor overlap risk with a closely related skill.

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

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