CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

phylogenetics-builder

End-to-end ML phylogenetic tree inference — MSA, trimming, ModelFinder, IQ-TREE2/RAxML-NG.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/phylogenetics-builder/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.

A strong operational skill body: concrete commands, a precise flag surface, real tool gotchas, validation checkpoints, and a graceful offline fallback make it highly actionable. The weaknesses are token efficiency (redundant 12-command CLI block duplicating the flags table) and no use of bundle files to split reference material out of SKILL.md.

Suggestions

Collapse the twelve near-identical CLI examples into one canonical invocation plus the existing "All flags" table (or 2–3 example combinations), saving ~50 lines.

Move the Citations list, Dependencies table, and MSA benchmark table into a references/ file (e.g., references/tools.md) linked from the body, and ship the referenced phylogenetics_builder.py / examples/demo_tree.nwk inside the bundle.

Add an explicit error-recovery loop after tree inference (e.g., "if result.json workflow_state != completed, read contract_alerts, fix input/flags, re-run") to reach the top workflow-clarity anchor.

DimensionReasoningScore

Conciseness

The body is dense with tool-specific knowledge Claude cannot be assumed to know (prank's ".best.fas" suffix, stripping "+F" for RAxML-NG, UFBoot ≥ 95 threshold) and avoids basic-concept padding. However, the CLI Reference repeats twelve near-identical full invocations (~50 lines) that duplicate the "All flags" table directly below it — a sizable tightening opportunity, not a minor trim, so it sits at anchor 3 rather than 4.

3 / 5

Actionability

Fully executable throughout: exact engine commands ("iqtree2 -s aln.fa -m MODEL --prefix prefix [-bb 1000]"), a complete flag table with defaults, a demo-mode command, the ETE3 midpoint snippet, and concrete log-parsing targets like "Best-fit model according to BIC:". Copy-paste-ready guidance covers the common cases.

5 / 5

Workflow Clarity

The 8-step workflow is clearly numbered with per-step skip conditions ("--aligned", "--no-trim", "--model"), upfront input validation (≥3 sequences, equal-length check for aligned input), RAxML-NG "--check" pre-validation, a "workflow_state == completed" checkpoint, and a mandatory demo fallback. It falls short of anchor 5 only because explicit validate→fix→retry error-recovery loops are not spelled out.

4 / 5

Progressive Disclosure

Sections are clearly headed and navigable, but everything is inline in a single ~300-line file — the 12-entry Citations list, the dependency table, and the MSA benchmark table are reference material that could live in separate files. Body-referenced files ("phylogenetics_builder.py", "examples/demo_tree.nwk") are not present in the bundle's reference directories either.

3 / 5

Total

15

/

20

Passed

Description

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

The description is specific and tool-anchored, clearly communicating the pipeline (MSA → trimming → model selection → tree inference) and the engines involved. Its main weakness is the complete absence of "when to use" trigger guidance, which caps completeness and limits natural trigger-term coverage. Adding a "Use when..." clause with user-facing phrases would lift it substantially.

Suggestions

Append an explicit trigger clause such as: "Use when the user wants to build a phylogenetic or evolutionary tree from DNA/protein sequences, mentions phylogeny, IQ-TREE, RAxML, MSA/bootstrap, or asks which substitution model to use."

Add natural synonyms users say ("phylogeny", "evolutionary tree", "tree from sequences", "bootstrap support") to the description text itself, not just metadata trigger_keywords.

Mention the distinguishing output (Newick tree with support values, offline demo fallback) to further separate it from distance-tree sibling skills.

DimensionReasoningScore

Specificity

Lists several concrete pipeline stages and named tools ("MSA, trimming, ModelFinder, IQ-TREE2/RAxML-NG") rather than vague language. Minor gaps in coverage — rooting, visualisation, and bootstrap support are part of the skill but unmentioned — keep it below the comprehensive anchor 5.

4 / 5

Completeness

The "what" is clear (end-to-end ML phylogenetic tree inference through named stages and engines), but there is no "Use when..." clause or any equivalent explicit trigger guidance, which the rubric caps at 3. It is not a 4 because "when" is entirely absent rather than present-but-vague.

3 / 5

Trigger Term Quality

Includes the central natural phrase "phylogenetic tree" plus tool names users would naturally say ("IQ-TREE2", "ModelFinder"). Common variations like "evolutionary tree", "phylogeny", or "build a tree from sequences" are missing, so it is good-but-not-comprehensive keyword coverage rather than anchor 5.

4 / 5

Distinctiveness Conflict Risk

"ML phylogenetic tree inference" with IQ-TREE2/RAxML-NG carves a distinct niche from generic skills. Minor overlap risk remains with closely related phylogeny skills (e.g., distance/k-mer tree tools), since a user asking only for a "phylogenetic tree" might not intend ML inference.

4 / 5

Total

15

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

ClawBio/ClawBio

Path

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