replicates-incorporation

Merges BAMs and generates pseudo-replicates for reproducible peak analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures reproducible peak analyses by systematically merging BAM files and, when needed, creating pseudo-replicates to enable stable downstream peak calling and consensus formation.

Core Features & Use Cases

  • Supports pre-peak calling (BAM mode) by pooling BAMs and optionally splitting into two balanced pseudo-replicates.
  • Supports post-peak calling (Peak mode) by performing IDR analysis to derive a conservative or optimal consensus peak set.
  • Ideal for experiments with multiple replicates who require deterministic, reproducible peak lists and clear output structure.

Quick Start

Run the replicates-incorporation workflow to merge BAMs and, if requested, generate two pseudo-replicates for peak calling.

Frequently Asked Questions about replicates-incorporation

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

FAQPage Schema
How do I merge biological replicates for IDR-based consensus peak calling?

To merge biological replicates for IDR-based consensus peak calling, you pool BAM files from chromatin assays and optionally split them into two balanced pseudo-replicates. This ensures reproducible peak analysis across more than two replicates.

What is the best way to generate pseudo-replicates from pooled BAM files for ATAC-seq?

Generating pseudo-replicates from pooled BAM files for ATAC-seq involves merging the biological replicates and then deterministically splitting the pooled reads into two balanced sets. This enables stable downstream peak calling and IDR analysis.

Can I use IDR analysis on existing peak lists instead of raw BAM files?

Yes, you can use IDR analysis on existing peak lists by operating in Peak mode. This mode skips BAM pooling and directly derives a conservative or optimal consensus peak set from the provided peak files.

How many biological replicates do I need for consensus peak analysis?

You need more than two biological replicates for IDR-based consensus peak analysis when starting from BAM files. If you already have peak lists, two replicates are sufficient for merging into a consensus peak set.

How does the workflow choose between merging BAMs and performing IDR analysis?

The workflow selects its mode deterministically based on the provided data: it enters BAM mode for pre-peak calling pooling when raw BAMs are supplied, and switches to Peak mode for IDR analysis when pre-existing peak files are detected.

How do I ensure reproducibility when merging BAM files for ChIP-seq?

To ensure reproducibility when merging BAM files for ChIP-seq, the workflow enforces deterministic inputs and mode selection, outputting a structured project layout with merged and consensus peak sets for stable downstream analysis.