ngs-epigenomics-peaks

Routes ATAC-seq, ChIP-seq, CUT&RUN, and CUT&Tag data to assay-specific peak-calling workflows.

5.3k|765|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/openai/plugins --skill ngs-epigenomics-peaks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ngs-epigenomics-peaks
Source: https://github.com/openai/plugins/tree/main/plugins/ngs-analysis/skills/ngs-epigenomics-peaks
Command: npx skills add https://github.com/openai/plugins --skill ngs-epigenomics-peaks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Epigenomics experiments span multiple assay types (ATAC-seq, ChIP-seq, CUT&RUN, CUT&Tag), each requiring different pipelines, controls, and peak-calling strategies. This Skill removes the guesswork of choosing the right workflow by classifying the assay and dispatching to the correct nf-core pipeline.

Core Features & Use Cases

  • Assay Dispatch: Classifies incoming requests and routes ATAC-seq to nf-core/atacseq, ChIP-seq to nf-core/chipseq, and CUT&RUN/CUT&Tag to nf-core/cutandrun.
  • Preflight Validation: Runs a preflight script that checks inputs and emits an install plan before any compute is launched.
  • FASTQ Intake and QC: Validates sample sheets, checks read structure, and runs seqkit stats plus FastQC/MultiQC, producing a peak_calling_readiness.json report.
  • Use Case: A researcher receives CUT&Tag FASTQ files with IgG controls and needs QC, alignment, and narrow peak calls. The Skill confirms replicates and controls, runs preflight, and hands off to the nf-core/cutandrun workflow.

Quick Start

Ask the assistant to classify your epigenomics assay, verify controls and replicates, and prepare a preflight-first peak-calling plan for your FASTQ files.

Frequently Asked Questions about ngs-epigenomics-peaks

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

FAQPage Schema
How do I choose between nf-core/atacseq, nf-core/chipseq, and nf-core/cutandrun?

Choose the pipeline by assay type: ATAC-seq data routes to nf-core/atacseq, ChIP-seq data routes to nf-core/chipseq, and CUT&RUN or CUT&Tag data routes to nf-core/cutandrun. The Skill classifies the assay first, then dispatches to the matching workflow.

How do I run QC on ATAC-seq or ChIP-seq FASTQ files before peak calling?

Run the shared FASTQ assay package with the epigenomics_peaks lane and a sample sheet. It validates paths and read structure, runs seqkit stats and FastQC/MultiQC when available, and writes a peak_calling_readiness.json report.

What inputs are required for epigenomics peak calling?

You need the assay type, FASTQ or BAM input, organism and genome build, and optionally a blacklist file. Control samples such as input DNA, IgG, or spike-in, plus biological replicates and the desired peak type, should also be confirmed.

Can I use MACS2 directly instead of a full nf-core pipeline?

Direct MACS2 is supported only for focused peak-calling tasks from prepared BAM files. Full intake, QC, alignment, signal tracks, consensus peaks, and differential analysis still route through the assay-specific nf-core workflow.

What outputs do the ATAC and ChIP/CUT&RUN runners produce?

The runners emit TSV/JSON summaries plus native review files: QC dashboard HTML, FRiP and peak SVG plots, insert-size SVG plots, browser-track preview HTML, UCSC track lines, and IGV session files.