Beautify phylogenetic trees with taxonomy color blocks, bootstrap values, and timelines. Accepts Newick format and outputs PNG, PDF, or SVG.
78
Quality
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Data analysis/phylogenetic-tree-styler/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, domain-specific description with excellent specificity and distinctive terminology that clearly identifies its niche in phylogenetic tree visualization. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user mentions phylogenetic trees, tree visualization, Newick files, or evolutionary tree diagrams.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Beautify phylogenetic trees with taxonomy color blocks, bootstrap values, and timelines' plus specifies input format (Newick) and output formats (PNG, PDF, SVG). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities and formats, but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes natural domain-specific terms users would say: 'phylogenetic trees', 'taxonomy', 'bootstrap values', 'timelines', 'Newick format', and common file extensions (PNG, PDF, SVG). | 3 / 3 |
Distinctiveness Conflict Risk | Highly specialized niche (phylogenetic tree visualization) with distinct domain terminology (Newick, bootstrap values, taxonomy) that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong actionable guidance with complete executable examples and a comprehensive parameter reference. However, it suffers from generic boilerplate sections (Workflow, Output Requirements, Response Template) that don't add value specific to phylogenetic tree styling and inflate token usage. The fallback behavior section is well-designed with specific recovery steps.
Suggestions
Remove or significantly condense the generic 'Workflow', 'Output Requirements', and 'Response Template' sections - these describe general Claude behavior rather than tree-styling specifics
Add an explicit validation step between loading the Newick file and rendering (e.g., 'Verify tree loaded correctly: check node count matches expected species')
Consolidate the error handling and fallback behavior sections to reduce redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some redundancy - the workflow section is generic and duplicates concepts covered elsewhere, the output requirements and response template sections add boilerplate that Claude already knows. However, the core technical content (parameters, examples, formats) is reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable commands with concrete examples for each feature (basic, bootstrap, taxonomy, timeline). The parameter table is complete, input format examples are copy-paste ready, and the quick check section gives immediate validation commands. | 3 / 3 |
Workflow Clarity | The generic 'Workflow' section is abstract and not specific to tree styling. However, the fallback behavior section provides good error recovery steps with specific commands. Missing explicit validation checkpoint between input validation and rendering for a multi-step visualization process. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is in one file when some content (like the detailed response template, generic workflow steps) could be separated or removed. The composability note is good but the document is somewhat long for a single skill file. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
ca9aaa4
Table of Contents
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.