CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-gwas-study-explorer

Compare GWAS studies, perform meta-analyses across cohorts, and assess signal replication. Uses GWAS Catalog metadata, study-level statistics, and cross-cohort comparison. Use for evaluating GWAS reproducibility for a trait, meta-analysis sample size and effect-size aggregation, and detecting study heterogeneity (population, design, ancestry).

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugin/skills/tooluniverse-gwas-study-explorer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 has good bones — clear use cases, an excellent honesty rule guarding against fabricated meta-analysis results, and a valuable domain-reasoning section — but it is bloated with textbook meta-analysis content Claude already knows, contains no executable code, and cites a script ('python_implementation.py') that is absent from the bundle. Roughly half the file could move to a reference document or be cut outright.

Suggestions

Cut or move to a reference file the textbook sections Claude already knows — the fixed/random-effects explanation, the I² interpretation ladder, 'Sources of Heterogeneity', 'Quality Tiers', and 'Limitations & Caveats' — keeping only skill-specific decision rules (which thresholds to apply, which model to pick when).

Fix the dangling reference: 'python_implementation.py' is cited as the meta-analysis implementation but no scripts/ directory exists in the bundle. Either ship the script or inline a working inverse-variance pooling code example so the honesty rule is actionable.

Convert at least one use-case workflow (e.g., the TCF7L2 meta-analysis) into a numbered, executable sequence with the concrete tool calls and a validation checkpoint (e.g., 'if matched associations lack beta + CI, report descriptive mode and stop').

DimensionReasoningScore

Conciseness

Large stretches of the body are textbook material Claude already knows: fixed vs random-effects models, the I² interpretation ladder ('<25% low... >75% considerable'), 'Sources of Heterogeneity' (ancestry, phenotype, platform, winner's curse), generic quality tiers, and a long 'Limitations & Caveats' section. These padded sections crowd out the genuinely skill-specific guidance (the honesty rule, the domain-reasoning section) — matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor.

2 / 5

Actionability

There is some concrete guidance — named tools like 'gwas_get_associations_for_snp' and 'OpenTargets_get_variant_credible_sets', and a precise honesty rule with concrete output fields — but the workflows are outline bullets ('Search for all T2D studies', 'Filter by sample size and ancestry') with no executable code anywhere in the body. Worse, the honesty rule anchors correctness to 'python_implementation.py parses these from the GWAS Catalog beta/or_value + range fields', yet no scripts/ directory or such file exists in the bundle, so the referenced implementation cannot actually be used.

3 / 5

Workflow Clarity

The four use-case workflows do list a rough sequence (search → filter → extract → assess) with expected outcomes, and the honesty rule supplies one implicit checkpoint (fall back to 'method=descriptive' when effect sizes are unusable). But the sequences are unnumbered bullet sketches with no explicit validation checkpoints for batch operations like cross-study association retrieval or replication-rate calculation, matching the 'steps listed but validation gaps' anchor.

3 / 5

Progressive Disclosure

Section headers and structure are present (Overview, Use Cases, Statistical Methods, Tools Used, Glossary), so it is not unstructured. However, the bundle contains no references/, scripts/, or assets/ directories — everything, including ~150 lines of statistical-methods and quality-tier reference material that belongs in a separate file, is inlined — and the single file the body does cite ('python_implementation.py') does not exist, so the one navigation pointer is broken.

3 / 5

Total

11

/

20

Passed

Description

92%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: third-person voice, explicit and concrete 'what' statements, a clear 'Use for...' trigger clause covering the three main use cases, and a well-defined niche. The only minor gap is a few missing natural synonym phrases like 'genome-wide association' or 'association study'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Compare GWAS studies, perform meta-analyses across cohorts, and assess signal replication' — and grounds them in specific data sources ('GWAS Catalog metadata, study-level statistics, and cross-cohort comparison'), giving comprehensive coverage of the skill's capabilities. It matches the anchor for multiple specific concrete actions, and is not a level-4 case since no meaningful capability gap remains.

5 / 5

Completeness

Both 'what' ('Compare GWAS studies, perform meta-analyses across cohorts, and assess signal replication') and 'when' ('Use for evaluating GWAS reproducibility for a trait, meta-analysis sample size and effect-size aggregation, and detecting study heterogeneity') are explicitly stated with concrete trigger phrases. This matches the top anchor exactly.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: 'GWAS', 'meta-analyses', 'reproducibility', 'effect-size aggregation', 'heterogeneity', 'GWAS Catalog'. Missing a few common variations such as 'genome-wide association', 'pooled analysis', or 'association study', so it falls just below the comprehensive-with-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The GWAS/genetics-analysis niche is highly specific with distinct triggers ('GWAS Catalog', 'cross-cohort comparison', 'signal replication'), making conflict with other skills unlikely. The domain terms would not naturally route users to a different skill.

5 / 5

Total

19

/

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-study-explorer/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.