CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

etetoolkit

Analyzes, manipulates, compares, annotates, and visualizes phylogenetic or other hierarchical trees with ETE 4. Supports Newick/Nexus tree I/O, topology edits and pattern matching, Robinson-Foulds comparisons, gene-tree evolutionary events and reconciliation, NCBI/GTDB taxonomy, SmartView exploration, and publication rendering. Applies to existing trees after alignment and phylogenetic inference, rather than inferring trees from raw sequences.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 excellent, highly actionable reference skill: pinned, runnable commands and code for every workflow, honest interpretation caveats, a pre-reporting validation checklist, and clean one-level-deep progressive disclosure into six real reference files. The only notable gaps are unspecific validation-feedback loops in a couple of workflows and minor trim candidates (dates, repeated uv invocations, the citation block).

DimensionReasoningScore

Conciseness

The body is largely lean: tight code blocks with pointed, high-value caveats (parser mismatches, normalized RF being 'undefined (None), not evidence of agreement') and no explanation of concepts Claude already knows. Minor trim candidates keep it below anchor 5: time-sensitive details in the 'Current Target' section ('released September 3, 2025 and verified ... on September 30, 2026'), six near-identical `uv run --no-project --isolated --with` invocations, and the extended citation block at the end.

4 / 5

Actionability

Fully executable throughout: pinned install commands ('uv pip install "ete4==4.4.0"'), a copy-paste Quick Start, complete runnable Python snippets for every workflow (inspect/transform, RF comparison, evol events, taxonomy, visualize), and exact CLI invocations with flags ('--parser support --mode circular --show-support --color-by-support --support-scale percent'). It also covers the common cases and their concrete failure modes ('A value of 1 means 1% in the former and full support in the latter').

5 / 5

Workflow Clarity

Each workflow section is clearly sequenced with concrete inputs/outputs, and the 'Quality and Interpretation Checks' numbered checklist provides explicit pre-reporting validation (confirm parser, check duplicates, state rooting, record versions). It falls short of anchor 5 because validate→fix→retry feedback loops are not spelled out — e.g. 'A parser mismatch is the most common cause of NewickError' diagnoses but does not describe the correction loop, and taxonomy ambiguity handling raises an error without a recovery path.

4 / 5

Progressive Disclosure

The body is a well-organized overview with 'Load only the reference needed for the task' and a Reference Map giving one-line descriptions of six reference files, all of which exist in references/ and are exactly one level deep (reference files link only to external upstream URLs, not to each other). Detailed material (API reference, full workflows, taxonomy setup, visualization, migration) is correctly split out of SKILL.md, matching the clear-overview anchor 5.

5 / 5

Total

18

/

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, distinctive description with excellent capability coverage and strong natural domain keywords. Its main weakness is the absence of an explicit 'Use when...' trigger clause; the scope sentence partially compensates but does not provide user-facing trigger phrases, capping completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions phylogenetic trees, Newick or Nexus files, tree rooting/pruning, topology comparison, or tree visualization for publication.'

Include common synonyms and file extensions users would naturally say — 'evolutionary tree', 'dendrogram', '.nw', '.tree', '.newick' — to round out trigger term coverage.

Consider naming common analysis phrases such as 'root a tree', 'prune tips', or 'compare tree topologies' as triggers, since these are frequent user requests the skill handles.

DimensionReasoningScore

Specificity

The description lists many concrete, distinct capabilities — 'Newick/Nexus tree I/O, topology edits and pattern matching, Robinson-Foulds comparisons, gene-tree evolutionary events and reconciliation, NCBI/GTDB taxonomy, SmartView exploration, and publication rendering' — going well beyond the anchor-4 example in breadth while remaining domain-specific. No vague filler or over-claims; it matches the comprehensive multiple-concrete-actions anchor.

5 / 5

Completeness

The 'what' is clearly and concretely answered, but there is no 'Use when...' clause or equivalent explicit trigger guidance; the closing sentence 'Applies to existing trees after alignment and phylogenetic inference, rather than inferring trees from raw sequences' is a scope/boundary statement, not user-facing trigger phrases. Per the judging guideline, a missing 'Use when' clause caps completeness at 3; the boundary sentence keeps it from being merely implied but does not reach anchor 4's explicit 'when'.

3 / 5

Trigger Term Quality

Good natural keywords users would actually say: 'phylogenetic', 'hierarchical trees', 'Newick/Nexus', 'Robinson-Foulds', 'tree visualization'. A few common natural terms are missing — synonyms like 'evolutionary tree', 'dendrogram', 'tree of life', and file extensions like '.nw' or '.tree' — so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (ETE 4 phylogenetics) with highly distinctive triggers — 'Robinson-Foulds', 'Newick/Nexus', 'NCBI/GTDB taxonomy', 'SmartView' — that virtually no other skill would claim. The explicit non-goal ('rather than inferring trees from raw sequences') further reduces mis-triggering against alignment/inference tools, matching the minimal-conflict anchor 5.

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

K-Dense-AI/scientific-agent-skills

Path

skills/etetoolkit/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.