CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-plant-genomics

Plant genomics and biology research — PlantReactome pathways, Ensembl Plants gene structure, POWO species taxonomy, UniProt annotation, KEGG plant pathways. Handles polyploidy (wheat hexaploidy etc.) and homeologous gene copies. Use for crop-gene annotation, plant secondary metabolism queries, and plant-disease/stress-response biology.

Quality

82%

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

The canonical home for this skill is tooluniverse-plant-genomics in mims-harvard/ToolUniverse

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, domain-specific research skill: the reasoning strategy is genuinely useful (polyploidy caveats, evidence grading, don't-guess-code rules), and tool usage is mostly concrete. The main weaknesses are redundancy (duplicated evidence grading, a duplicated pathway ID row, meta-commentary in the tool table) and uneven example coverage across phases.

Suggestions

State the T1–T4 evidence grading once (keep the Phase 4 version) and delete the duplicate in Key principles to recover tokens.

Remove the meta-commentary from the tool table row for BAR_get_rnaseq_expression and fix the duplicated ath04712 entry (listed for both brassinosteroid signaling and circadian rhythm).

Add one concrete invocation example each for Phase 0 (POWO/Ensembl identification) and Phase 3 (EnsemblCompara_get_orthologues) to match the specificity of Phases 1–2.

DimensionReasoningScore

Conciseness

Mostly efficient — the KEGG pathway and organism-code tables earn their tokens by supporting the 'do not assume KEGG organism codes' rule. But the T1–T4 evidence grading is stated twice (Key principles #5 and Phase 4), the pathway table duplicates ath04712 across two different rows, and the tool table carries non-guidance meta-commentary ('the expression-data source this skill was otherwise missing'), fitting anchor 3 ('mostly efficient... could be tightened') rather than anchor 4's near-zero redundancy.

3 / 5

Actionability

Concrete, executable-style calls with real parameters (e.g., 'ensembl_lookup_gene(gene_symbol="CHS", species="arabidopsis_thaliana")', 'KEGG_get_pathway_genes(pathway_id="ath00941")') plus specific ID tables. Phases 0, 3, and 4 have no concrete invocation examples, which are minor gaps — anchor 4 rather than anchor 5's copy-paste-ready coverage of common cases.

4 / 5

Workflow Clarity

A clear five-phase pipeline diagram is followed by sequenced per-phase sections, and the 'LOOK UP DON'T GUESS' rule functions as a verification checkpoint (confirm KEGG codes, use reviewed UniProt evidence). No explicit error-recovery loops, but this is a read-only research workflow with no destructive or batch operations, so the cap does not apply — anchor 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle files (references/, scripts/, assets/) exist, so scoring reflects in-body organization: clean section headers, a tool table, ID tables, a limitations section, and easy navigation — anchor 4. Not anchor 5 because at ~145 lines the KEGG/organism tables and per-phase details are candidates for a one-level-deep reference file that would keep SKILL.md a leaner overview.

4 / 5

Total

15

/

20

Passed

Description

87%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: it names specific databases and capabilities, handles a distinctive technical concern (polyploidy/homeologs), and includes an explicit and concrete 'Use for' clause. Trigger coverage is good but could add a few more natural synonyms (Arabidopsis, major crop names, gene function).

Suggestions

Lead the database list with verb-led actions (e.g., 'Search plant pathways via PlantReactome, look up genes in Ensembl Plants, resolve species taxonomy with POWO') to sharpen the 'what'.

Add one or two natural trigger synonyms users are likely to say, such as 'Arabidopsis', 'gene function annotation', or 'crop stress tolerance'.

DimensionReasoningScore

Specificity

The description names five concrete data sources with their distinct roles ('PlantReactome pathways, Ensembl Plants gene structure, POWO species taxonomy, UniProt annotation, KEGG plant pathways') plus a concrete capability ('Handles polyploidy (wheat hexaploidy etc.) and homeologous gene copies'). These are noun-phrase capabilities rather than verb-led actions and coverage of the domain has minor gaps, matching anchor 4 rather than the comprehensive action coverage of anchor 5.

4 / 5

Completeness

It explicitly answers both questions: the 'what' is concrete (five named databases plus polyploidy/homeolog handling) and the 'when' is an explicit 'Use for crop-gene annotation, plant secondary metabolism queries, and plant-disease/stress-response biology' with concrete trigger cases, matching anchor 5. Not 4 because the when-clause is already explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Good coverage of natural user phrasing: 'plant genomics', 'crop-gene annotation', 'plant secondary metabolism', 'plant-disease/stress-response biology', 'polyploidy', 'wheat hexaploidy'. Some natural terms are missing (e.g., Arabidopsis, gene function, other major crop names), which fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear plant-only niche anchored by plant-specific databases (PlantReactome, POWO, Ensembl Plants) makes it unlikely to trigger for human/animal or general systems-biology skills — a clear niche with distinct triggers, matching anchor 5. Not 4 because no meaningful overlap with a closely related skill is evident from the description itself.

5 / 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

plugins/tooluniverse/skills/tooluniverse-plant-genomics/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.