agentleFS
Sign inStart free
Scientific-ToolingScientific-Tooling/structured-intelligence/skills/genome-alignment-qc/SKILL.md

genome-alignment-qc

Skill4 starsChanged 12 days agoMITView on GitHub

Assess alignment quality with coverage depth, mapping rates, insert size, and on-target metrics using samtools, mosdepth, and picard.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run samtools stats and samtools flagstat for mapping summary.

    line 28
  2. Very specific:

    Run samtools idxstats for per-chromosome read counts.

    line 29
  3. Very specific:

    Run mosdepth for coverage distribution (genome-wide, or restricted to target BED).

    line 30
  4. Distinctive:

    If target BED provided: compute on-target rate and per-target coverage statistics.

    line 31
  5. Very specific:

    Run picard CollectInsertSizeMetrics for insert size distribution.

    line 32
  6. Very specific:

    Run picard CollectAlignmentSummaryMetrics for detailed alignment statistics.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: genome-alignment-qc

Use When

  • User wants to evaluate BAM quality before variant calling.
  • User needs to assess coverage depth and uniformity across the genome or target regions.
  • User wants to check mapping rate, duplication rate, and insert size distribution.
  • User needs to calculate on-target rate for whole-exome sequencing (WES).
  • User wants to compare QC metrics across samples to detect batch effects.

Inputs

  • Required:
    • BAM file with index (.bam + .bai).
  • Optional:
    • Target BED file (for WES on-target metrics).
    • Reference FASTA (required for picard metrics).
    • Output directory (default: current directory).
    • Per-base coverage flag (enables mosdepth per-base output; default: off).

Workflow

  1. Run samtools stats and samtools flagstat for mapping summary.
  2. Run samtools idxstats for per-chromosome read counts.
  3. Run mosdepth for coverage distribution (genome-wide, or restricted to target BED).
  4. If target BED provided: compute on-target rate and per-target coverage statistics.
  5. Run picard CollectInsertSizeMetrics for insert size distribution.
  6. Run picard CollectAlignmentSummaryMetrics for detailed alignment statistics.
  7. Compile summary: mapping rate, duplicate rate, mean coverage, coverage uniformity (CV), median insert size, on-target rate (if WES).
  8. Flag metrics outside recommended thresholds (see knowledge/sources/genomics/quality-thresholds.md).

Output Contract

  • samtools stats and samtools flagstat output files.
  • mosdepth coverage files (.mosdepth.global.dist.txt, .per-base.bed.gz if enabled).
  • Picard insert size metrics file and histogram.
  • Picard alignment summary metrics file.
  • Compiled QC summary with key metrics and threshold flags.

Limits

  • samtools, mosdepth, and picard must be installed and available on $PATH.
  • mosdepth per-base output can be very large for WGS (~10 GB for 30x human).
  • Picard requires a Java runtime (Java 8+).
  • Reference FASTA is required for picard metrics but not for samtools/mosdepth.
  • This skill reports metrics for a single BAM; multi-sample comparison is out of scope.
  • Common failure cases:
    • BAM index (.bai) missing or out of date relative to the BAM file.
    • Target BED file using different chromosome naming convention than the BAM (e.g., chr1 vs 1).
    • Picard failing due to missing reference FASTA sequence dictionary (.dict).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free