track-generation

Convert filtered BAM files into RPM-normalized BigWig tracks.

12|3|Updated Nov 4, 2025
One-click install
npx skills add https://github.com/BIsnake2001/ChromSkills --skill track-generation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: track-generation
Source: https://github.com/BIsnake2001/ChromSkills/tree/main/6.track-generation
Command: npx skills add https://github.com/BIsnake2001/ChromSkills --skill track-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts filtered BAM files into browser-ready genome tracks (BigWig), enabling fast visualization and comparison across experiments.

Core Features & Use Cases

  • RPM-normalized tracks: generate tracks scaled to 1M mapped reads for cross-sample comparability.
  • ATAC-seq and ChIP-seq support: automatically apply Tn5 offset for ATAC-seq and omit for ChIP-seq.
  • Interactive visualization: optionally visualize signal around TSS or user-defined regions.
  • Example use: A data analyst wants to QC ATAC-seq samples by generating track visuals for quick inspection in a genome browser.

Quick Start

Provide a filtered BAM file and let the tool generate RPM-normalized BigWig tracks for visualization.

Frequently Asked Questions about track-generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a BAM file to a normalized BigWig track for visualization?

You can generate RPM-normalized BigWig tracks directly from filtered BAM files. The process scales mapped reads to 1 million, applies chromosome size generation, and outputs browser-ready BigWig files for cross-sample comparison.

Does track generation apply Tn5 offset correction automatically for ATAC-seq?

Yes, the workflow detects ATAC-seq inputs and automatically applies Tn5 offset correction during track creation. This adjustment is omitted for ChIP-seq, ensuring accurate signal representation for each assay type.

Can I visualize signal around transcription start sites after generating genome tracks?

Yes, you can optionally visualize signal profiles around transcription start sites or user-defined target regions. This allows immediate QC inspection of the RPM-normalized BigWig tracks within your analysis environment.

What is RPM normalization and why do I need it for ATAC-seq or ChIP-seq tracks?

RPM normalization scales mapped reads to reads per million, standardizing signal intensity across experiments. This allows fair cross-sample comparability when visualizing ATAC-seq or ChIP-seq genome tracks in a browser.

Do I need to manually specify the genome assembly when creating BigWig tracks?

No, the track generation workflow automatically detects the genome assembly from your input data. It handles chromosome size generation internally, requiring only a filtered BAM file to produce the final BigWig output.

Why are my ChIP-seq BAM files not showing the same offset correction as ATAC-seq?

ChIP-seq tracks intentionally omit Tn5 offset correction, which is specific to ATAC-seq data. The workflow differentiates between the two assays, applying correction only when ATAC-seq is detected to ensure correct signal shifts.