plugins/ngs-analysis/skills/ngs-atacseq-peaks-qc/SKILL.md
Run or plan ATAC-seq QC, alignment, TSS enrichment, fragment-size, blacklist, peak-calling, consensus peak, and differential accessibility workflows.
npx skillsauth add openai/plugins ngs-atacseq-peaks-qcInstall 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 for ATAC-seq accessibility analysis from FASTQ or BAM. If the assay is ChIP-seq, CUT&RUN, CUT&Tag, or antibody-targeted enrichment, use ngs-chip-cutrun-peaks-qc.
Confirm:
Prefer nf-core/atacseq for full reproducible processing. Use direct MACS2 only when BAMs are already aligned, duplicate/blacklist handling is known, and the user wants focused peak calling.
Preflight command:
python plugins/ngs-analysis/scripts/ngs_preflight.py --pipeline atacseq_peaks_qc --emit-install-plan
For compact read-level intake/QC, use the shared epigenomics execution package:
python plugins/ngs-analysis/scripts/run_fastq_assay_package.py \
--lane epigenomics_peaks \
--sample-sheet atac_samples.csv \
--execute
For local-light ATAC alignment, peaks, FRiP, TSS, bigWig tracks, and consensus peaks from FASTQ or prepared BAMs, use the dedicated ATAC runner:
python plugins/ngs-analysis/scripts/run_atacseq_peaks_qc.py \
--sample-sheet atac_samples.csv \
--bowtie2-index /refs/GRCh38/bowtie2/genome \
--genome-size hs \
--blacklist-bed /refs/GRCh38/blacklists/encode_blacklist.bed \
--tss-bed /refs/GRCh38/tss.bed \
--execute
This runner emits qc/atacseq_qc_summary.{tsv,json}, qc/atacseq_qc_dashboard.html, native SVG FRiP/peak and insert-size plots, browser-track handoff files under tracks/, and TSS profile/heatmap commands when --tss-bed is supplied. Add --run-motifs --motif-genome <genome> when HOMER motif enrichment should be part of the backend run.
It also emits resources/resource_plan.json, resource_manifest.tsv, resource_env.sh, and resource_readiness.md. The resource check is advisory by default for local-light runs; add --genome-build, --bundle-root <bundle>=<path>, and --require-resource-plan when missing registered reference bundles should block readiness.
For nf-core execution, use plugins/ngs-analysis/scripts/run_nfcore_pipeline.py --pipeline atacseq.
Review before biological interpretation:
Do not proceed to differential accessibility if replicate quality or metadata is insufficient.
Produce:
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.