Skip to content

vimalinx/bio-agent / .claude/skills/blastdbcheck

blastdbcheck

Unverified

Use when verifying integrity and validity of BLAST databases before using them in search pipelines or troubleshooting database corruption issues.

blastdbcheck

Quick Start

  • Command: blastdbcheck -db <dbname> -dbtype <prot|nucl> [options]
  • Local executable: /home/vimalinx/miniforge3/envs/bio/bin/blastdbcheck
  • Full reference: See references/help.md

When To Use This Tool

  • Validate a BLAST database before running expensive searches.
  • Diagnose corruption, missing files, or inconsistent volumes in an existing BLAST DB.
  • Audit a whole directory tree of databases with -dir and -recursive.
  • Enforce metadata expectations such as taxonomy IDs with -must_have_taxids.

Common Patterns

# 1) Quick integrity check of one protein database
blastdbcheck \
  -db swissprot \
  -dbtype prot \
  -verbosity 2
# 2) Exhaustive validation of a critical nucleotide database
blastdbcheck \
  -db nt \
  -dbtype nucl \
  -full \
  -verbosity 3
# 3) Sweep a directory of databases recursively
blastdbcheck \
  -dir /data/blastdb \
  -recursive \
  -verbosity 1

Recommended Workflow

  1. Decide whether you are checking one database (-db) or scanning a directory (-dir).
  2. Set -dbtype explicitly when the database name is ambiguous instead of relying on guess.
  3. Start with the default summary mode, then escalate to -full, -random, -stride, or -ends depending on how much confidence you need.
  4. Treat any failures as a database maintenance problem and repair or re-download the BLAST DB before running downstream searches.

Guardrails

  • Use BLAST+ style flags such as -help and -version; the common GNU-style --help pattern is wrong here.
  • -db is incompatible with -dir and -recursive.
  • -full is incompatible with sampling modes such as -stride, -random, and -ends.
  • -must_have_taxids is a policy check, not a repair step; older or custom databases may fail it legitimately.
  • -cdd_delta is only meaningful for CDD / DELTA-BLAST related databases.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall