CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-phylogenetics

Phylogenetic analysis — de novo multiple sequence alignment (Clustal Omega/MUSCLE/MAFFT via EBI_msa_align) and neighbour-joining/UPGMA tree building (EBI_build_phylogenetic_tree) from your own sequences, plus tree analysis, treeness, saturation (PhyKIT), parsimony-informative sites, alignment gap analysis, DVMC, long-branch detection, BUSCO orthologs. Uses PhyKIT, Biopython, DendroPy. Use to align a set of sequences, build a tree from sequences or an alignment, or for phylogenetic tree QC, multi-gene phylogenomics, evolutionary-rate analysis, and comparative-genomics studies.

Quality

82%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 is exceptionally actionable — every trap comes with an exact command, output format, or decision table — but it is a ~650-line monolith that repeats its key rules multiple times and even contradicts itself on which alignment to use for treeness_over_rcv. Consolidating the duplicated guidance into single canonical sections and moving detail into the existing (partially orphaned) reference files would substantially improve it.

Suggestions

Consolidate the three separate saturation-column discussions (trap 1, 'PhyKIT column conventions', 'column-position cheat sheet') and the duplicated gap-percentage and batch-vs-loop warnings into one canonical section each.

Resolve the direct contradiction on the `treeness_over_rcv` alignment input: 'Which alignment goes with which metric' says untrimmed `.faa.mafft` while 'Treeness/RCV: use the right input file' says trimmed `.faa.mafft.clipkit` — state one verified rule with the numbers that justify it.

Move the long worked examples and per-metric tables into the existing reference files (`sequence_alignment.md`, `tree_building.md`, `parsimony_analysis.md`) with inline 'See X for Y' pointers, and link the currently orphaned `references/troubleshooting.md`.

DimensionReasoningScore

Conciseness

The body is ~650 lines with material duplication: the saturation-column convention is explained three times (trap 1, 'PhyKIT column conventions', 'column-position cheat sheet'), the gap-percentage definition twice, and the batch-vs-loop warning four times, alongside concept explanations Claude already knows (what an internal branch is). Most of the trap data is genuinely non-obvious and earns its place, keeping this above the 'noticeably padded' anchor but below 'efficient'.

3 / 5

Actionability

Guidance is fully executable throughout: exact `tu run phykit_batch_analysis '{...}'` payloads, bundled script invocations with flags and expected output blocks (`# SUMMARY group=animals: n=... median=...`), per-metric column tables, and a phrasing-to-statistic mapping table. Copy-paste ready commands cover the common cases.

5 / 5

Workflow Clarity

RULE ZERO gives an explicit check-first sequence and there are validation checkpoints (sanity targets, 'count files first', wrong-column tells), so the batch-operation cap is not triggered. However, the same rules are restated across scattered sections and directly contradict each other — 'Which alignment goes with which metric' mandates the untrimmed `.faa.mafft` for `treeness_over_rcv`/`rcv` while 'Treeness/RCV: use the right input file' mandates the trimmed `.faa.mafft.clipkit` — leaving the reader without a single canonical procedure per metric.

3 / 5

Progressive Disclosure

Reference and script files exist and the paths cited in the body are real, but the References section is a single flat line at the very bottom rather than inline signposts, the bulk of per-metric detail is inlined in SKILL.md instead of split across the available reference files, and `references/troubleshooting.md` and `scripts/format_alignment.py` are never referenced anywhere.

3 / 5

Total

14

/

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: it names concrete capabilities with specific tools and closes with an explicit, well-phrased 'Use to...' trigger clause covering the main use cases. Its only weakness is that some triggers are insider jargon and common file extensions (.fasta, Newick) are absent.

DimensionReasoningScore

Specificity

Lists many concrete named actions — "de novo multiple sequence alignment (Clustal Omega/MUSCLE/MAFFT via EBI_msa_align)", "neighbour-joining/UPGMA tree building", "treeness, saturation (PhyKIT), parsimony-informative sites, alignment gap analysis, DVMC, long-branch detection, BUSCO orthologs" — giving comprehensive coverage of the domain's actions, matching the top anchor rather than leaving minor gaps.

5 / 5

Completeness

Explicitly answers both: the what (alignment, tree building, tree analysis, QC metrics) and the when ("Use to align a set of sequences, build a tree from sequences or an alignment, or for phylogenetic tree QC, multi-gene phylogenomics, evolutionary-rate analysis") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "align a set of sequences", "build a tree from sequences or an alignment", "phylogenetic tree QC", "comparative-genomics studies" — but leans on domain jargon (treeness, DVMC) and omits common file-extension triggers like .fasta or Newick, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear phylogenetics niche with tool-specific triggers (PhyKIT, Biopython, DendroPy, BUSCO orthologs, phylogenetic tree QC) that would not naturally fire for unrelated skills; conflict risk is minimal.

5 / 5

Total

19

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (650 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

mims-harvard/ToolUniverse

Path

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