busco-phylogeny
Generate phylogenies from genome assemblies using BUSCO/compleasm-based single-copy orthologs with scheduler-aware workflow generation
Install with Tessl CLI
npx tessl i github:brunoasm/my_claude_skills --skill busco-phylogenyOverall
score
80%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 technically precise description that clearly identifies a specialized bioinformatics capability for phylogenetic analysis. Its main weakness is the absence of explicit trigger guidance ('Use when...') and limited coverage of alternative phrasings users might employ. The description excels at distinctiveness but could improve discoverability for users who don't know the exact technical terminology.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when building evolutionary trees, comparing species relationships, or running phylogenomic pipelines'
Include common alternative terms users might say: 'phylogenetic tree', 'evolutionary tree', 'species tree', 'comparative genomics', 'tree building'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate phylogenies', 'genome assemblies', 'BUSCO/compleasm-based single-copy orthologs', 'scheduler-aware workflow generation'. These are precise, technical actions in the bioinformatics domain. | 3 / 3 |
Completeness | Clearly answers 'what' (generate phylogenies using specific methods with workflow generation), but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes domain-specific terms like 'phylogenies', 'BUSCO', 'compleasm', 'orthologs', 'genome assemblies' that experts would use, but missing common variations like 'phylogenetic tree', 'evolutionary tree', 'species tree', or simpler terms non-experts might use. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining phylogenetics, BUSCO/compleasm tools, and scheduler-aware workflows. Very unlikely to conflict with other skills due to the specific bioinformatics pipeline focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, comprehensive phylogenomics skill with excellent actionability and workflow clarity. The content provides concrete, executable guidance with proper validation checkpoints and clear references to supporting materials. Minor verbosity in some sections (repeated reminders, some explanatory text) slightly reduces token efficiency but doesn't significantly detract from the skill's utility.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeated mentions of 'unified conda environment', multiple reminders about mandatory steps). Some sections could be tightened, though most content is necessary for the complex workflow. | 2 / 3 |
Actionability | Provides fully executable commands throughout (bash scripts, Python invocations, conda commands). Each step includes concrete, copy-paste ready code examples with specific flags and parameters. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (Steps 0-9), explicit validation section, input/output mapping between steps, and quality control checkpoints. The 'Script Validation' section provides explicit feedback loops for error recovery. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview pointing to one-level-deep references (templates/, scripts/, references/REFERENCE.md). Content is appropriately split between the main skill file and supporting resources with clear navigation signals. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (758 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 12 / 16 Passed | |
- 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.