CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

biopython-phylo

Use Bio.Phylo to read/write phylogenetic trees and perform visualization and statistics; use when tree parsing/conversion, pruning/rerooting, distance calculation, or plotting is required.

Quality

79%

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/Data Analysis/biopython-phylo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 highly actionable with complete, runnable code and a clear single-script workflow, but it is let down by verbosity (inline boilerplate and duplicated conventions), absent validation checkpoints for batch tree modifications, and poor bundle utilization — the existing reference file is never linked and the script is not actually shipped as a file.

Suggestions

Move the full phylo_task.py script into an actual scripts/ bundle file and keep only a short usage snippet plus the config schema in SKILL.md, removing the duplicated encoding/JSON conventions from either Example Usage or Implementation Details.

Add validation checkpoints to the workflow: verify the input tree parses, confirm prune/reroot targets were found, and re-read the written output with Phylo.read to confirm the conversion succeeded before reporting completion.

Link the existing references/phylogenetics.md from the body (e.g., an 'Advanced usage' section pointing to it for format details, NeXML/CDAO support, and additional tree operations) instead of leaving it disconnected from the skill.

DimensionReasoningScore

Conciseness

The body inlines a ~120-line script including generic glue code (ensure_parent_dir, load_config) Claude can write unaided, and the "Implementation Details" section restates conventions (utf-8, ensure_ascii=False) already explained in the Example Usage intro, so it is mostly efficient but could be tightened — not anchor 4 given the duplicated and boilerplate content.

3 / 5

Actionability

The body provides a complete config JSON, a fully executable copy-paste-ready script, a run command, and format-specific API calls (Phylo.read/write, root_with_outgroup, draw_ascii, Agg backend), matching the anchor for fully executable guidance covering common cases.

5 / 5

Workflow Clarity

The sequence (read → prune → reroot → write → ascii → stats → plot) is clear via the script's main(), but there are no validation or verification checkpoints (e.g., no output re-parse check or error-recovery guidance beyond the outgroup ValueError). Pruning a list of terminals is a batch tree modification, so per the rubric cap workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

Section headers are well organized, but the full script is inlined even though the doc presents it as living at scripts/phylo_task.py (no such bundle file exists), and the bundled references/phylogenetics.md is never linked from the body — matching the anchor for references present but not clearly signaled and content that should be separate kept inline.

3 / 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: it states concrete capabilities in third person, includes an explicit "use when" clause with natural trigger phrases, and occupies a distinct niche. The only improvement area is adding format synonyms (Newick, NEXUS, .nwk) to the trigger terms.

DimensionReasoningScore

Specificity

Concrete actions are named ("read/write phylogenetic trees", "visualization and statistics"), but pruning, rerooting, and distance calculation appear only as trigger phrases rather than stated capabilities, leaving minor gaps in coverage — matching the 'several specific actions; minor gaps' anchor rather than the comprehensive anchor 5.

4 / 5

Completeness

The description explicitly answers both what ("Use Bio.Phylo to read/write phylogenetic trees and perform visualization and statistics") and when ("use when tree parsing/conversion, pruning/rerooting, distance calculation, or plotting is required") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Triggers like "tree parsing/conversion, pruning/rerooting, distance calculation, or plotting" are natural user phrasings, but common synonyms and file-format terms (Newick, NEXUS, .nwk) are missing, so keyword coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Phylogenetic trees with Bio.Phylo is a clear niche with distinct, domain-specific triggers; only mild genericness in "plotting" and "statistics" exists, and both are anchored to trees, so conflict risk is minimal.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

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