CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

etetoolkit

Phylogenetic tree toolkit (ETE). Tree manipulation (Newick/NHX), evolutionary event detection, orthology/paralogy, NCBI taxonomy, visualization (PDF/SVG), for phylogenomics.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/etetoolkit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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, highly actionable body with executable examples for every capability and a sound SKILL.md-to-references split. Weaknesses are duplicated install/troubleshooting content and a promotional section that pad the token budget, undefined/cross-snippet variables in a few examples, and missing validation checkpoints in the batch and destructive workflows.

Suggestions

Add validation steps to the batch/destructive workflows (e.g. verify leaf count or tree validity after pruning/node deletion in Use Case 4, and check output files after batch CLI conversion) — this is what currently caps workflow clarity.

Deduplicate the Qt/pyqt5 dependency instructions (keep them in one place, cross-reference from Troubleshooting) and remove the K-Dense Web promotional section to cut padded tokens.

Make code snippets self-contained: define 'extract_species_from_name' and restate or inline the 'events'/'query' variables in the ortholog-detection example.

DimensionReasoningScore

Conciseness

The code examples are dense and mostly earn their tokens, but there is real padding: the Qt/pyqt5 system-dependency install instructions appear verbatim in both 'Installation and Setup' and 'Troubleshooting', the 'Load these references' block is a redundant comment-style restatement, and the closing K-Dense Web promotional section is unrelated to the task. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the minor-trimmings anchor of 4.

3 / 5

Actionability

Extensive concrete, executable guidance: copy-paste-ready Python for Tree/PhyloTree/NCBITaxa/ClusterTree workflows, real CLI invocations for scripts/tree_operations.py and scripts/quick_visualize.py. Minor gaps keep it from 5: 'extract_species_from_name' is used but never defined, and the ortholog/paralog snippet depends on 'events' and 'query' defined only in a prior snippet, so not every block is self-contained.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (e.g. Use Case 1's numbered 1-6 pipeline, Use Case 4's standardize/filter/save loop), but workflows involving batch and destructive operations — batch node deletion across many trees in Use Case 4, batch CLI preprocessing in Use Case 2 — include no validation or verification steps. Per the judging guideline, missing validation in batch/destructive workflows caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Good structure against the actual bundle: three real one-level-deep references (api_reference.md, workflows.md, visualization.md) and two scripts, each described in a 'Reference Documentation' section stating what it contains. Not 5 because the reference pointers use Python comments instead of clean markdown links (weaker navigation signaling) and some inline material (the Newick format table, Best Practices list) could live in a reference file; not 3 because the split is appropriate and references are clearly signaled, not buried.

4 / 5

Total

14

/

20

Passed

Description

70%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 specific, distinctive description with good domain keywords and concrete capability names. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness, and minor coverage gaps (clustering, tree comparison).

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with phylogenetic trees, Newick/NHX files, orthology analysis, or NCBI taxonomy queries.'

Mention the remaining capabilities (tree comparison/Robinson-Foulds, clustering analysis) so the description's coverage matches the body.

Include a couple of natural synonyms users might type, such as 'phylogeny' or 'dendrogram', to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Names concrete capabilities with formats ('Tree manipulation (Newick/NHX), evolutionary event detection, orthology/paralogy, NCBI taxonomy, visualization (PDF/SVG)'), but they are noun-features rather than action verbs and clustering/tree comparison coverage is missing, so it falls between the 'comprehensive' (5) and 'several specific actions' (4) anchors — closer to 4 given the coverage gaps.

4 / 5

Completeness

The 'what' is clear and multi-part, but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'for phylogenomics' only weakly implies when to invoke it. Per the judging guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural domain keywords a phylogenetics user would say: 'phylogenetic tree', 'ETE', 'Newick', 'NHX', 'orthology/paralogy', 'NCBI taxonomy', 'phylogenomics'. A few natural variations are missing ('phylogeny', 'dendrogram', 'tree comparison', file extensions like .newick), so it does not reach the comprehensive-synonym anchor of 5 but sits noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers: 'Phylogenetic tree toolkit (ETE)' with terms like Newick/NHX, orthology/paralogy, and NCBI taxonomy is highly unlikely to fire for any other skill. This matches the 'clear niche with distinct triggers; minimal conflict risk' anchor exactly.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

googolme/run0204

Path

scientific-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.