vimalinx/bio-agent / .claude/skills/esl-compalign
esl-compalign
UnverifiedUse when comparing a test multiple sequence alignment against a trusted reference alignment to compute accuracy. Requires Stockholm format files with
esl-compalign
Quick Start
- Command:
esl-compalign [-options] <trusted file> <test file> - Local executable:
/home/vimalinx/miniforge3/envs/bio/bin/esl-compalign - Full reference: See
references/help.md
When To Use This Tool
- Use
esl-compalignwhen evaluating a test alignment against a trusted reference alignment. - It is appropriate for benchmark or method-comparison workflows where both alignments are in Stockholm format with RF annotation.
- Use
-cwhen you want per-column statistics and-pwhen comparing alignment accuracy against posterior probability information. - Reach for it when you need an explicit quantitative comparison of alignment quality rather than just visual inspection.
Common Patterns
# Compare a test alignment against a trusted alignment
esl-compalign trusted.sto test.sto
# Emit per-column statistics instead of per-sequence statistics
esl-compalign -c trusted.sto test.sto
# Compare accuracy as a function of posterior probability
esl-compalign -p trusted.sto test.sto
# Write column-wise stats in ssdraw-compatible format
esl-compalign -c --c2dfile compalign.dfile trusted.sto test.sto
Recommended Workflow
- Prepare trusted and test alignments in Stockholm format with #=GC RF markup
- Verify sequences appear in identical order in both files
- Confirm #=GC RF markup has identical number of non-gap characters in both files
- Run
esl-compalign <trusted file> <test file>to compute accuracy
Guardrails
- Both files must be in Stockholm format with #=GC RF markup
- Sequences must occur in the same order in the two files
- Number of non-gap characters in #=GC RF markup must be identical between files
-ponly makes sense when posterior probability annotation exists in the tested alignment context
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |