sequence-alignment
Trigger when user needs to align DNA/protein sequences, compare biological sequences, search for similar sequences in databases, or perform BLAST-based similarity analysis. Use for bioinformatics sequence comparison tasks.
Install with Tessl CLI
npx tessl i github:aipoch/medical-research-skills --skill sequence-alignment84
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
89%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 solid skill description with excellent trigger terms and completeness. The description clearly identifies when to use the skill and includes domain-specific keywords that users would naturally use. The main weakness is that the specific capabilities could be more detailed - listing concrete actions like 'generate alignment scores', 'produce phylogenetic comparisons', or 'export FASTA format results' would strengthen specificity.
Suggestions
Add more concrete action verbs describing specific outputs or capabilities (e.g., 'generate pairwise alignments', 'calculate sequence identity percentages', 'produce alignment visualizations')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (bioinformatics) and some actions like 'align DNA/protein sequences', 'compare biological sequences', 'search for similar sequences', but doesn't list comprehensive concrete actions like specific alignment algorithms, output formats, or detailed capabilities. | 2 / 3 |
Completeness | Explicitly answers both what ('align DNA/protein sequences, compare biological sequences, search for similar sequences in databases, perform BLAST-based similarity analysis') and when ('Trigger when user needs to...'). Has clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'DNA', 'protein sequences', 'biological sequences', 'BLAST', 'similarity analysis', 'sequence comparison', 'bioinformatics'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with distinct bioinformatics-specific triggers like 'BLAST', 'DNA/protein sequences', 'biological sequences'. Unlikely to conflict with general data analysis or other skills due to specialized terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid actionable guidance with executable BLAST commands and clear parameter documentation. However, it's bloated with boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add no instructional value. The workflow could be improved with explicit steps for handling API polling, timeouts, and result validation.
Suggestions
Remove boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) - these are template artifacts, not actionable guidance
Add a workflow showing the full BLAST process: submit query → poll for completion → handle timeout/retry → validate results → parse output
Include example output showing what a successful BLAST result looks like, so Claude knows what to expect and can validate
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains significant boilerplate that doesn't add value (Risk Assessment table, Security Checklist, Evaluation Criteria, Lifecycle Status sections). The core BLAST content is reasonably efficient, but nearly half the document is template filler that Claude doesn't need. | 2 / 3 |
Actionability | Provides fully executable bash commands with concrete examples for both DNA and protein sequences. Parameter table is clear and complete. Commands are copy-paste ready with realistic sequence examples. | 3 / 3 |
Workflow Clarity | Shows individual commands but lacks multi-step workflow guidance. No validation steps for checking if BLAST job completed, no error handling workflow for API timeouts/failures, no guidance on interpreting results before proceeding. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections. References to external documentation (blast_docs.md, ncbi_api_guide.md) are one level deep and clearly signaled. Quick examples up front with reference tables for deeper detail. | 3 / 3 |
Total | 10 / 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 | |
- 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.