bio-atac-seq-differential-accessibility
Identify differentially accessible chromatin regions across conditions using DiffBind, csaw, DESeq2, or edgeR. Use when comparing ATAC-seq accessibility between treatment groups, choosing between consensus-peak vs sliding-window approaches, picking the correct normalization (full library vs reads-in-peaks), correcting batch with SVA/RUVseq, or interpreting log2FC and FDR thresholds in a chromatin context.
npx skills add BioTender-max/awesome-bio-agent-skills --skill differential-accessibility --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Identify differentially accessible chromatin regions across conditions using DiffBind, csaw, DESeq2, or edgeR. Use when comparing ATAC-seq accessibility between treatment groups, choosing between consensus-peak vs sliding-window approaches, picking the correct normalization (full library vs reads-in-peaks), correcting batch with SVA/RUVseq, or interpreting log2FC and FDR thresholds in a chromatin context.
How it works
- Provides version compatibility notes and prerequisites for DiffBind, DESeq2, edgeR, csaw, limma, GenomicRanges, ChIPseeker, Subread, sva, RUVSeq.
- Describes multiple workflows: DiffBind on consensus peaks, csaw window-based analysis, or direct use of DESeq2/edgeR on peak-count data.
- Explains normalization and library-size options in DiffBind (normalize and library parameters), including defaults and alternative choices like RiP (reads-in-peaks) and spike-in strategies.
- Recommends peak strategy decisions based on experimental scenario (e.g., stable peaks vs shifting peak structure) and outlines an explicit decision tree for typical designs.
- Details a consensus peak-set strategy (intersection, union, majority, per-condition unions, iterative overlap) and notes the impact on FDR and interpretability.
- Outlines normalization schemes specific to ATAC-seq differential analysis, including DiffBind options (DBA_NORM_LIB, DBA_NORM_NATIVE, DBA_NORM_TMM, etc.), and when to apply each (e.g., background drift, global shifts).
- Provides failure modes and fixes for common tools (DiffBind library-size choices, summits parameter, csaw windowing, apeglm shrinkage, filterByExpr filtering in edgeR).
- Describes reconciliation steps when tools disagree and enables high-confidence reporting only when concordant across methods.
- Covers thresholds for effect size and significance, including FDR cutoffs and abs(log2FC) criteria, with conservative and exploratory guidelines.
- Includes sections on handling hidden batch effects with SVA/RUVseq and spike-in normalization, with R code patterns illustrating usage.
When to use it
- Use when comparing ATAC-seq accessibility between treatment groups or conditions.
- Use when deciding between consensus-peak and sliding-window approaches.
- Use when choosing between normalization strategies (full library vs reads-in-peaks) and when correcting batch effects with SVA/RUVseq.
- Use when interpreting log2FC and FDR thresholds in a chromatin context.
What it can touch
- DiffBind, csaw, DESeq2, edgeR, limma, DESeq2/edgeR backends, and associated normalization and batch-correction tools (sva, RUVSeq).
- Guidance references to spike-in normalization using exogenous chromatin (e.g., dm6 spike-ins) and peak-count matrices derived from Subread featureCounts.
Caveats
- Describes multiple tool-specific failure modes (e.g., DiffBind library-size confounding, summits parameter, csaw window sizing, apeglm shrinkage at low n, filtering with low counts).
- Recommends validating current consensus practices before locking pipelines; results can be sensitive to peak-set strategy and normalization choices.
- No outcomes are promised; instructions are descriptive of workflows, options, and caveats only.
## Version Compatibility Reference examples tested with: DiffBind 3.12+, DESeq2 1.42+, edgeR 4.0+, csaw 1.36+, limma 3.58+, GenomicRanges 1.54+, ChIPseeker 1.38+, Subread 2.0+ (featureCounts), sva 3.50+, RUVSeq 1.36+. Before using code patterns, verify installed versions match: - R: `packageVersion('<pkg>')` then `?function_name` to verify parameters If code throws unexpected errors, introspect the installed package and adapt rather than retrying. # Differential Accessibility **"Find chromatin regions that change accessibility between my conditions"** -> Build a sample-by-region count matrix, normalize for library size and chromatin compaction, fit a generalized linear model (negative-binomial), and extract regions with significant accessibility change. - R (consensus-peak workflow): `DiffBind` -> count -> normalize -> contrast -> analyze - R (window-based, no peak set): `csaw::windowCounts` + `filterWindowsGlobal` + edgeR QL F-test - R (existing peak-count matrix): `DESeq2` or `edgeR` directly on `featureCounts` output DiffBind is a wrapper around DESeq2 / edgeR with ATAC-aware defaults. csaw is the only peak-free option; it tests fixed-width sliding windows. The choice depends on
- Version Compatibility
- Algorithmic Taxonomy
- Decision Tree by Experimental Scenario
- Consensus Peak Set Strategy
- Normalization: The ATAC-Specific Choice
- Per-Tool Failure Modes
- DiffBind -- Library-size choice confounds global change
- DiffBind summits parameter -- Width-driven differential
- csaw -- Window size and filter choice dominates results
- DESeq2 -- Apeglm shrinkage with too few reps
- edgeR QL -- Filter must be aggressive enough
- Reconciliation: When Tools Disagree
- Effect Size and Threshold Selection
- Hidden Batch with SVA / RUVseq
What does the bio-atac-seq-differential-accessibility skill do?
Identify differentially accessible chromatin regions across conditions using DiffBind, csaw, DESeq2, or edgeR. Use when comparing ATAC-seq accessibility between treatment groups, choosing between consensus-peak vs sliding-window approaches, picking the correct normalization (full library vs reads-in-peaks), correcting batch with SVA/RUVseq, or interpreting log2FC and FDR thresholds in a chromatin context.
How do I install it?
Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill differential-accessibility --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
