busco-phylogeny

Generate phylogenies from genome assemblies using BUSCO/compleasm-based single-copy orthologs with scheduler-aware workflow generation

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./phylo_from_buscos/SKILL.md

Quality

Content

73%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 delivers strong, actionable, well-sequenced guidance with robust validation feedback loops and good progressive-disclosure structure. Its weaknesses are redundancy across the closing sections and the missing templates/ bundle directory referenced throughout.

Suggestions

Consolidate the redundant 'Important Notes', 'Communication Guidelines', and 'Workflow Entry Point' sections, which restate earlier content, to reduce token cost.

Provide the templates/ directory referenced throughout the body (or correct the references), since the absence of these files undermines the template-based workflow.

Remove padding annotations like '(new!)' and '(important!)' that add tokens without guidance value.

Dimension	Reasoning	Score
Conciseness	Mostly efficient per section but the ~820-line body has notable redundancy — 'Important Notes', 'Communication Guidelines', and 'Workflow Entry Point' restate earlier instructions, and '(new!)'/'(important!)' annotations are padding.	3 / 5
Actionability	Provides concrete, copy-paste-ready bash/python commands, template placeholders to replace, and references to real scripts, with minor gaps (the referenced templates/ directory is not present in the bundle).	4 / 5
Workflow Clarity	Steps 0–9 are clearly sequenced with an explicit validation section containing verify→fix→retry feedback loops and 'Only proceed when validation passes' checkpoints for batch/destructive operations.	5 / 5
Progressive Disclosure	Content is well-signaled and points one level deep to a real references/REFERENCE.md, but the heavily-referenced templates/ directory is absent from the bundle and some inline sections (e.g., full STEP 0A NCBI guidance) could be split out.	4 / 5
	Total	16 / 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.

The description is specific and distinctive, naming the domain, core tools, and the scheduler-aware angle clearly. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which limits completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when the user wants to build a phylogenetic tree or species tree from genome assemblies, or mentions BUSCO, compleasm, or single-copy orthologs').

Include common synonyms and file/extension hints (e.g., 'phylogenetic tree', 'species tree', '.fasta', '.fna genome assemblies') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete specifics ('genome assemblies', 'BUSCO/compleasm-based single-copy orthologs', 'scheduler-aware workflow generation'), though it centers on one primary action with elaboration rather than a list of distinct actions.	4 / 5
Completeness	Has a clear 'what' but no explicit 'Use when...' trigger clause, and per the rubric guidance a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a phylogenomics user would say ('phylogenies', 'genome assemblies', 'BUSCO', 'compleasm', 'single-copy orthologs'), with good but not exhaustive synonym coverage (missing 'phylogenetic tree'/'species tree').	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, specific niche (genome-assembly phylogenomics via BUSCO/compleasm orthologs with scheduler-aware generation) with distinct triggers and minimal overlap risk.	5 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (820 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: brunoasm/my_claude_skills
Path: phylo_from_buscos/SKILL.md
Commit: 5bdff99

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.