sequence-analysis

name	sequence-analysis
description	Use when routing DNA, RNA, or protein sequence tasks to the core sequence-analysis commands that are actually installed in this workspace.
allowed-tools	["Read","Bash(blast*:*)","Bash(hmmer*:*)","Bash(mafft:*)","Bash(bowtie2:*)","Bash(bwa:*)","Write"]

sequence-analysis

Workspace gateway for day-to-day sequence work. The current bio environment has real local executables for blastn, blastp, makeblastdb, bowtie2, bwa, samtools, hmmscan, hmmbuild, mafft, muscle, hisat2, featureCounts, prodigal, RNAfold, seqkit, and Biopython.

Quick Start

• Activate environment: conda activate bio
• Verified local tools: blastn, blastp, makeblastdb, bowtie2, bwa, samtools, hmmscan, hmmbuild, mafft, muscle, hisat2, featureCounts, prodigal, RNAfold, seqkit
• Verified Python library: Bio (Biopython)

When To Use This Tool

• Choosing the right installed tool for DNA/RNA/protein sequence analysis
• Running alignment, homology search, ORF prediction, or basic format/statistics work
• Building a small ad hoc sequence workflow without committing to a bigger pipeline
• Verifying what is truly available in the workspace before proposing a method

Common Patterns

# Local BLAST search
blastn -query input.fa -db nt -outfmt 6 -out results.tsv

# Multiple-sequence alignment
mafft input.fa > aligned.fa

# ORF prediction for a microbial genome
prodigal -i genome.fa -a proteins.faa -d genes.fna -f gff -o genes.gff

# Basic Biopython parsing
from Bio import SeqIO
records = list(SeqIO.parse("input.fa", "fasta"))
print(len(records))

Recommended Workflow

1. Activate the bio environment and confirm the exact tool you need is present.
2. Validate the input format before launching expensive searches or alignments.
3. Prefer the simplest installed CLI that matches the task: BLAST for homology search, MAFFT/MUSCLE for MSA, HMMER for domain search, Prodigal for microbial ORFs, and Samtools/Hisat2/FeatureCounts for RNA-seq-style alignment/counting.
4. Escalate to more specialized project skills only when the plain CLI workflow is clearly insufficient.

Guardrails

• Keep claims limited to tools verified on PATH in this workspace.
• The old autogenerated skill suggested direct Biomni tool imports as a ready path, but local Biomni tool imports currently fail because langchain_core is missing.
• Use CLI-first workflows here; treat Biomni/Evo2 as separate repo-backed projects with extra dependency requirements.
• Validate input formats explicitly. Many of these tools assume FASTA/FASTQ/SAM/BAM conventions and will fail noisily or misleadingly on malformed input.