CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

etetoolkit

ETE (Environment for Tree Exploration) toolkit for phylogenetic and hierarchical tree analysis; use it when you need to parse/manipulate Newick/NHX trees, detect duplication/speciation events, integrate NCBI taxonomy, and render publication-quality figures.

Quality

81%

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

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.

The body is well-structured, lean, and largely actionable, with ETE-specific details that genuinely add value. Its critical flaw is progressive disclosure: five bundle files exist but are completely unreferenced, so the detailed inlined material both duplicates them and leaves them undiscoverable.

Suggestions

Add a short 'References & Scripts' section linking references/workflows.md, references/api_reference.md, references/visualization.md, and the scripts/tree_operations.py and scripts/quick_visualize.py CLIs, so the bundle is discoverable from SKILL.md.

Move the detailed Implementation Details (format-code table, NHX serialization, event-detection steps, RF output explanation) into references/workflows.md and references/api_reference.md, keeping only one-line pointers in SKILL.md to remove the duplication.

In Example Usage, note that scripts/tree_operations.py already provides format conversion, rooting, pruning, and stats as a CLI, instead of re-implementing those steps inline; and add executable code (with method names) for the ortholog/paralog event-detection workflow, which is currently abstract steps.

DimensionReasoningScore

Conciseness

The body is mostly efficient: ETE-specific knowledge (format codes, NHX feature serialization, preserve_branch_length guidance) that Claude would not know, delivered as tight bullets and runnable code. It misses the 5 anchor because "When to Use" and "Key Features" restate the same capability list in two different forms, and the Implementation Details sections duplicate material that already exists in references/, so some tightening is possible.

4 / 5

Actionability

Mostly executable guidance: a complete runnable example with pip install, format-code table, concrete write/features call, and specific method names (get_midpoint_outgroup, prune(preserve_branch_length=True), robinson_foulds). It stops short of the 5 anchor because the evolutionary event detection section gives only abstract numbered steps ("Provide a species naming function", "Run descendant event detection") with no method names or code, unlike the fully copy-paste-ready PDF extraction example.

4 / 5

Workflow Clarity

The Example Usage is a clearly numbered 1–6 sequence with inline output checks (printing leaf/node counts), and event detection has a 4-step sequence. It sits at 4 rather than 5 because checkpoints are implicit (no verify-render-succeeded or error-recovery step) and the event-detection steps lack the concrete commands that would make them fully checkable; it is above the 3 anchor since sequences are explicit and operations are low-risk analysis/rendering, not destructive batch operations.

4 / 5

Progressive Disclosure

The bundle contains references/api_reference.md, references/visualization.md, references/workflows.md, scripts/tree_operations.py, and scripts/quick_visualize.py, yet the body never mentions or links to any of them — no referenced paths exist anywhere in SKILL.md. Meanwhile the inlined Implementation Details (format codes, event detection, RF comparison) and the hand-rolled example duplicate content that clearly belongs in those separate files (workflows.md covers the same operations; tree_operations.py is a ready-made CLI for exactly the conversion/rooting/pruning steps shown), matching the 2 anchor ('content that clearly belongs in separate files is inlined; or references are buried'). It is not a 1 because the body itself is well sectioned and navigable.

2 / 5

Total

14

/

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: third person, concrete, and explicit about both capabilities and triggers, with excellent domain-specific keywords. Its only weakness is incomplete coverage — tree comparison (RF distance), ortholog/paralog extraction, and clustering are prominent skill features absent from the trigger list.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "parse/manipulate Newick/NHX trees", "detect duplication/speciation events", "integrate NCBI taxonomy", and "render publication-quality figures" — within a clearly named domain ("phylogenetic and hierarchical tree analysis"). It falls just short of the 5 anchor because the body's other major capabilities, tree comparison (RF distance) and clustering/dendrograms, are omitted, which is exactly the 'minor gaps in coverage' of the 4 anchor.

4 / 5

Completeness

It explicitly answers both questions: the "what" is the concrete capability list (parse/manipulate trees, detect events, integrate taxonomy, render figures), and the "when" is an explicit "use it when you need to..." clause enumerating the same concrete trigger phrases. This matches the 5 anchor ('clearly and explicitly answers both what AND when with concrete trigger phrases'); the 4 anchor's weaker, less-explicit 'when' does not apply.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "phylogenetic", "Newick/NHX trees", "duplication/speciation", "NCBI taxonomy", and "publication-quality figures" are phrases users in this domain would actually say. A few natural terms are missing — "ortholog/paralog" (a very common user phrasing for this skill's event detection), "tree comparison", "RF distance", and "dendrogram" — matching the 4 anchor rather than the comprehensive synonym/extension coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — ETE-specific phylogenetic tree analysis with Newick/NHX, duplication/speciation events, and NCBI taxonomy — so triggers are distinct and conflict risk with other skills is minimal, matching the 5 anchor. It is far more specific than the 4 anchor's 'minor overlap risk with closely related skills'.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/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.