CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-model-organism-genetics

Cross-species genetic analysis using model organism databases (MGI mouse, IMPC systematic knockout phenotyping, ZFIN zebrafish, FlyBase fruit fly, WormBase worm, SGD budding yeast plus protein-domain/PTM/literature detail, PomBase fission yeast, RGD rat, GeneNetwork systems-genetics/eQTL panels, HumanMine/MouseMine cross-species data-warehouse search, GBIF taxonomy) plus VEuPathDB for eukaryotic pathogens (Plasmodium, Toxoplasma, fungi, vectors). Maps human genes to orthologs, retrieves phenotype/expression/functional data, assesses gene function conservation, and identifies the best animal model for studying a human gene or disease.

Quality

78%

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

Quality

Content

71%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.

An exceptionally actionable body: every phase is driven by concrete tool signatures, live-verified quirks, fallbacks, and error-handling rules, with a strong completeness checklist. Its weaknesses are token weight — a textbook classical-genetics section and long inline worked examples Claude doesn't need verbatim — and a fully monolithic layout with no reference files for a 340-line skill.

Suggestions

Move the 'Bacterial and Classical Genetics Reasoning' section into a reference file (e.g., references/classical-genetics.md) and keep only a one-line pointer plus any genuinely non-obvious heuristics, trimming the textbook lac/trp/three-point-cross explanations.

Split the per-organism deep detail (Phase 2b IMPC worked examples, Phase 3b VEuPathDB access limitation, Phases 4b/5 organism specifics) into references/<organism>.md files with clear pointers from SKILL.md, keeping the pipeline overview and reasoning principles inline.

Renumber phases into a monotonic order (e.g., promote pathogen databases to Phase 5c or an appendix) so the execution sequence reads linearly, and condense worked-example outputs to the fields that demonstrate the tool's behavior.

DimensionReasoningScore

Conciseness

Most of the body earns its tokens — exact tool signatures, parameter values, and live-verified API quirks (e.g., the IMPC empty mp_terms caveat, the MPD ENCODE-proxy warning, the VEuPathDB 401 limitation) that Claude cannot know. But the ~50-line 'Bacterial and Classical Genetics Reasoning' section re-explains textbook concepts (lac operon logic, trp attenuation, three-point cross mechanics) Claude already knows, and worked examples run long with inline p-values and effect sizes. This is 'mostly efficient but includes some unnecessary explanation or could be tightened' — level 3, not level 4, because the textbook section is a substantial block of over-explanation, though far from the level-2 pattern of pervasive padding.

3 / 5

Actionability

Every phase gives copy-paste-ready tool invocations with exact parameter names, accepted values ('drosophila_melanogaster' NOT 'fruitfly'), fallback chains, and error-handling instructions (e.g., 'use the nubKey (not the key)', 'Verify with a cheap call first', the 401 plain-disclosure rule). This matches the level-5 anchor: fully executable guidance whose worked examples cover the common cases.

5 / 5

Workflow Clarity

Phases 0-7 are clearly sequenced with 'ALWAYS FIRST' markers, explicit fallbacks at each step, verification guidance, and a final completeness checklist — approaching the level-5 anchor. What holds it at level 4 is non-monotonic phase numbering (Phase 3b appears after Phase 5b; 2b/2c/2d and 4b are interleaved), which muddies the intended execution order — a minor sequencing gap rather than a validation gap.

4 / 5

Progressive Disclosure

There are no bundle files at all — no references/, scripts/, or assets/ — so all ~340 lines live in SKILL.md under good section headers. Per-organism deep detail (IMPC worked examples, the VEuPathDB access-limitation block, bacterial genetics reasoning) is content that clearly belongs in separate reference files. This fits the level-3 anchor (structure present but content that should be separate is inline); it is above level 2 because the file is well-headed and navigable, and below level 4 because a skill this size should split its reference-grade detail out of the main file.

3 / 5

Total

15

/

20

Passed

Description

75%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 highly specific, well-differentiated description that names concrete actions and databases with excellent distinctiveness. Its main weakness is the absence of an explicit 'Use when...' trigger clause and a somewhat jargon-heavy keyword set, capping completeness and trigger-term quality below the top anchors.

Suggestions

Append an explicit trigger clause, e.g. 'Use when mapping a human gene to mouse/fly/worm/fish/yeast orthologs, comparing knockout phenotypes across species, or choosing the best animal model for a human gene or disease.'

Add a few natural user-side synonyms (e.g., 'which organism to study', 'gene conservation', 'mouse knockout phenotype') to broaden trigger matching beyond technical terms like eQTL and PTM.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Maps human genes to orthologs, retrieves phenotype/expression/functional data, assesses gene function conservation, and identifies the best animal model for studying a human gene or disease' — alongside named databases (MGI, IMPC, ZFIN, FlyBase, WormBase, SGD, PomBase, RGD, GeneNetwork, HumanMine/MouseMine, GBIF, VEuPathDB), giving comprehensive, non-generic coverage. It clearly matches the level-5 anchor rather than level 4, which is reserved for coverage with minor gaps.

5 / 5

Completeness

The 'what' is explicit and detailed (map orthologs, retrieve phenotype/expression/functional data, assess conservation, identify best model), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the 'when' is only weakly implied by 'for studying a human gene or disease'. The rubric guideline caps completeness at 3 for a missing 'Use when...' clause, and the anchor-3 example (clear 'what', weakly implied 'when') is the best fit — not level 4, which requires an explicit 'when'.

3 / 5

Trigger Term Quality

Natural terms a user would say are present — 'model organism', 'knockout', 'phenotype', 'orthologs', 'cross-species', 'animal model', plus organism names like 'zebrafish' and 'fruit fly' — but the phrasing leans technical (eQTL panels, PTM, data-warehouse) and misses common user-side synonyms like 'which organism should I study gene X in' or 'is this gene conserved'. Good coverage with a few natural terms missing fits the level-4 anchor; it falls short of level 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — cross-species model-organism genetics via named organism databases — with little overlap risk against generic skills; the body further delineates sibling skills (variant analysis, drug target validation, infectious disease). This matches the level-5 anchor (clear niche with distinct triggers, minimal conflict risk) rather than level 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

17

/

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-model-organism-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.