CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-population-genetics

Population genetics analysis — allele frequencies (gnomAD, 1000 Genomes), Hardy-Weinberg equilibrium testing, Fst between populations, GWAS associations, evolutionary constraint scores. Use for cross-population variant comparison, ancestry-aware allele frequency lookups, and population-level evolutionary analysis.

Quality

79%

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-population-genetics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 tool-facing half of this skill is genuinely strong: exact parameters, verified script invocations, explicit gotchas, and named workflow chains. The weakness is that well over half of the file is a textbook population-genetics and Mendelian-genetics cram sheet re-explaining concepts Claude already knows, all inlined in one monolithic document instead of split into reference files.

Suggestions

Move the Theoretical Reasoning, Mendelian Framework, Hfr Mapping, MCQ Elimination, and Common/Advanced Traps sections into one or two reference files (e.g., references/theory.md, references/traps.md), keeping only the formulas and traps that encode non-obvious field-specific knowledge in SKILL.md.

Cut explanations of concepts Claude already knows (HWE genotype expectations, broad vs narrow heritability, Punnett-square mechanics, non-disjunction basics, duplicate-gene fates) down to one-line reminders of the trap, since the value is in the 'which answer is expected' framing, not the definitions.

Add a minimal concrete example of invoking the ToolUniverse tools (e.g., the PopGen_hwe_test call with its arguments) so the 'Preferred' path is as executable as the fallback script path.

DimensionReasoningScore

Conciseness

Large portions of the ~360-line body re-teach textbook genetics Claude already knows: Hardy-Weinberg genotype expectations (p^2, 2pq, q^2), broad vs narrow heritability definitions, a six-step Punnett-square framework ("fathers pass X to all daughters"), Bridges' non-disjunction mechanics, epistasis ratio collapsing, neofunctionalization vs subfunctionalization definitions, and generic MCQ-answering advice ("evaluate ALL options before choosing"). This matches the 'noticeably verbose; several unnecessary explanations or padded sections' anchor rather than the 'mostly efficient with some unnecessary explanation' level 3 anchor, given how much of the file is concept review rather than skill-specific knowledge.

2 / 5

Actionability

The tool quick-reference table gives exact required parameters and formats ("variant_id format CHR-POS-REF-ALT", "dataset gnomad_r4"), the fallback script has fully specified, verified CLI invocations ("popgen_calculator.py --type hwe --AA N1 --Aa N2 --aa N3", all of which match the actual argparse definitions), and the four workflow chains name concrete tool sequences. Not 5: how to actually invoke the ToolUniverse tools is left as "use ... (via MCP/SDK)" with no example call, and EuropePMC/PubMed tools appear in workflows without any parameter documentation.

4 / 5

Workflow Clarity

Four named workflow chains give clear step sequences, and several explicit checkpoints exist: "May timeout -- retry once", "Handle all three" response formats, "Verify ratios sum to 1.0" as a dedicated Mendelian step, and the LOOK UP DON'T GUESS escalation path (preferred tools, then fallback script, then formulas). Not 5: error-recovery loops stop at those isolated tips — there is no general retry/validation pattern for failed queries or a verification step in the tool-based workflows.

4 / 5

Progressive Disclosure

The bundle is real and correctly linked (the only bundle file, scripts/popgen_calculator.py, exists and its documented modes match its argparse), and the body is broken into well-labeled sections. But the monolithic ~360-line body inlines substantial material that reads like separate reference topics (theoretical formulas, Mendelian framework, Hfr mapping, MCQ strategy), with no reference files to offload them into — matching 'some structure but could be better organized; content that should be separate is inline'. Not 4: there are no offloaded reference files at all, so content that clearly belongs in separate topics is all inlined.

3 / 5

Total

13

/

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 well-formed description: concrete, third-person, with named data sources and an explicit Use-for clause covering the domain's natural trigger phrases. Its only weakness is that the trigger list omits a few sub-topics the body covers (inbreeding, population structure, LD, selection), which slightly narrows discoverability.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions with named data sources: "allele frequencies (gnomAD, 1000 Genomes)", "Hardy-Weinberg equilibrium testing", "Fst between populations", "GWAS associations", and "evolutionary constraint scores" — comprehensive coverage of the skill's advertised capabilities. Not 4: unlike the 'minor gaps in coverage' anchor, every listed action names the operation and (where relevant) the exact database or statistic.

5 / 5

Completeness

Clearly answers both what (the enumerated analysis operations) and when with an explicit "Use for cross-population variant comparison, ancestry-aware allele frequency lookups, and population-level evolutionary analysis" clause containing concrete trigger phrases. Not 4: the 'when' clause is explicit and specific rather than merely improvable.

5 / 5

Trigger Term Quality

Strong natural keyword coverage including named sources users would actually say: "gnomAD", "1000 Genomes", "GWAS", "Hardy-Weinberg", "Fst", "allele frequency", "ancestry". Not 5: a few natural phrases the skill supports are absent from the description (e.g., "inbreeding", "population structure", "linkage disequilibrium", "selection"), which appear only in the body's When-to-Use list.

4 / 5

Distinctiveness Conflict Risk

A clear population-genetics niche with distinct triggers (cross-population comparison, ancestry-aware lookups, Fst, HWE, named frequency databases) that would rarely fire a clinical-interpretation or general-genomics skill. Not 4: the when-clause qualifiers ("cross-population", "population-level") disambiguate the GWAS/constraint terms that could otherwise overlap with a variant-annotation 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-population-genetics/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.