CtrlK
BlogDocsLog inGet started
Tessl Logo

tooluniverse-population-genetics-1000genomes

Population genetics using the 1000 Genomes Project (IGSR) — superpopulation/population search, sample metadata, variant frequencies across AFR/AMR/EAS/EUR/SAS, ancestry-specific analyses. Use for ancestry comparison, population-aware allele frequency lookups, and 1000-Genomes-cohort-specific analyses (distinct from gnomAD which has different sample composition).

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is highly actionable with concrete tool-call examples and clear phase organization, but loses some conciseness to background genetics explanations and lacks explicit validation checkpoints in its multi-step workflow.

Suggestions

Trim the Reasoning Framework's explanatory passages on Fst/LD/population-diversity basics to a concise reference of thresholds only, since Claude already knows these concepts.

Add an explicit validation step to the Population Stratification workflow (e.g., check that returned sample counts and population codes are non-empty before proceeding, and what to do if a query returns zero results).

Make the workflow's final step concrete by showing the cross-referencing action (e.g., a Python snippet joining GWAS SNP rsIDs against per-population allele frequencies) rather than the abstract 'Cross-reference with population data for stratification analysis.'

DimensionReasoningScore

Conciseness

The tool reference tables and code examples are efficient, but the Reasoning Framework section explains population-genetics concepts (Fst thresholds, LD patterns, diversity of AFR populations) that Claude already knows, adding length that doesn't earn its place.

2 / 3

Actionability

Provides executable JSON tool-call examples for every tool, concrete parameter values, response schemas, and copy-paste-ready snippets like {"superpopulation": "AFR", "limit": 10}.

3 / 3

Workflow Clarity

The 'Workflow: Population Stratification in GWAS' section sequences four numbered steps, but there are no explicit validation checkpoints or error-recovery loops, and Step 4 ('Cross-reference... for stratification analysis') is left abstract.

2 / 3

Progressive Disclosure

Content is well organized into clear phases with a consolidated Tool Parameter Quick Reference table; no bundle files exist so everything is appropriately inline at one level, satisfying the simple-skill carve-out.

3 / 3

Total

10

/

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 complete, covering both what the skill does and when to use it while explicitly distinguishing it from neighboring skills. It uses appropriate third-person voice and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'superpopulation/population search, sample metadata, variant frequencies across AFR/AMR/EAS/EUR/SAS, ancestry-specific analyses' — matching the anchor for naming several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what it does and when to use it via the 'Use for ancestry comparison, population-aware allele frequency lookups, and 1000-Genomes-cohort-specific analyses' clause, meeting the explicit-trigger bar.

3 / 3

Trigger Term Quality

Includes natural terms users would say ('1000 Genomes', 'IGSR', 'population', 'ancestry', 'allele frequency', 'population stratification') plus codes like AFR/AMR/EAS/EUR/SAS, giving good coverage of natural language.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche and even disambiguates from gnomAD ('distinct from gnomAD which has different sample composition'), making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.