plugins/ngs-analysis/skills/ngs-epigenomics-peaks/SKILL.md
Dispatch ATAC-seq, ChIP-seq, CUT&RUN, or CUT&Tag requests to assay-specific QC, alignment, signal-track, peak-calling, consensus, and differential peak workflows.
npx skillsauth add openai/plugins ngs-epigenomics-peaksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill as the epigenomics dispatcher for ATAC-seq, ChIP-seq, CUT&RUN, or CUT&Tag analysis. Hand off to the assay-specific deep skill once the assay type is known.
Confirm:
Choose the workflow by assay:
ngs-atacseq-peaks-qc using nf-core/atacseq by defaultngs-chip-cutrun-peaks-qc using nf-core/chipseq by defaultngs-chip-cutrun-peaks-qc using nf-core/cutandrun by defaultUse direct MACS2 only for focused peak-calling tasks from prepared BAMs.
python plugins/ngs-analysis/scripts/ngs_preflight.py --pipeline epigenomics_peaks --emit-install-plan
For FASTQ intake/QC over ATAC-seq, ChIP-seq, CUT&RUN, or CUT&Tag data, use the shared FASTQ assay package:
python plugins/ngs-analysis/scripts/run_fastq_assay_package.py \
--lane epigenomics_peaks \
--sample-sheet assay_samples.csv \
--execute
This validates sample-sheet paths and read structure, runs seqkit stats and FastQC/MultiQC when available, and writes peak_calling_readiness.json. Full alignment, signal tracks, TSS/FRiP, consensus peaks, and differential analyses still route through the assay-specific workflow.
Assay-specific ATAC and ChIP/CUT&RUN runners now also emit native review files alongside TSV/JSON summaries: qc/*_dashboard.html, FRiP/peak SVG plots, insert-size SVG plots, browser-track preview HTML, UCSC track lines, and IGV session files.
ATAC-seq preflight run:
nextflow run nf-core/atacseq \
-profile test,docker \
--outdir results/atacseq_test
ChIP-seq preflight run:
nextflow run nf-core/chipseq \
-profile test,docker \
--outdir results/chipseq_test
CUT&RUN/CUT&Tag preflight run:
nextflow run nf-core/cutandrun \
-profile test,docker \
--outdir results/cutandrun_test
Carry replicate and control metadata through the sample sheet before running real analysis.
development
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
data-ai
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
tools
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
development
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.