bio-atac-seq-single-cell-atac
Process and analyze single-cell ATAC-seq data with Signac, ArchR, SnapATAC2, or Cell Ranger ATAC. Use when handling 10X scATAC or 10X Multiome (paired RNA+ATAC) data, performing per-cell QC, choosing between ArchR/Signac/SnapATAC2 ecosystems, building per-cluster consensus peaksets, integrating with paired scRNA-seq, doublet detection (AMULET vs ArchR vs scDblFinder), or running pseudobulk differential accessibility per cluster.
npx skills add BioTender-max/awesome-bio-agent-skills --skill single-cell-atac --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
It instructs an AI agent to process and analyze 10X scATAC-seq data (and paired scRNA-seq for Multiome) by building per-cell fragment matrices, performing per-cell QC, and choosing among Signac, ArchR, SnapATAC2 ecosystems for downstream analyses. It covers steps for per-cluster pseudobulk peak calling, integrating with RNA data, and various doublet-detection strategies, plus guidance on per-cluster differential accessibility and cell-type annotation.
How it works
The skill enumerates multiple concrete workflows across ecosystems:
- R/Signac path: CreateChromatinAssay, Seurat-based pipeline with TF-IDF, SVD, UMAP, Leiden, and a gene-activity assay for annotation.
- R/ArchR path: createArrowFiles, doublet scoring, ArchRProject, iterative LSI, UMAP, clustering, then per-cluster reproducible peak sets.
- Python/SnapATAC2 path: import_fragments, QC metrics, tile matrix, spectral embedding, UMAP, Leiden, and per-cluster MACS3 peaks, plus gene activity.
- CLI/Cell Ranger ATAC path: preprocessing via cellranger-atac count or chromap at the preprocessing layer.
- Reconciliation rules across tools to compare UMAP shapes, doublet rates, and cluster boundaries, plus an operational rule to require cross-ecosystem agreement for cell-type annotation.
- Per-cluster pseudobulk peak calling via MACS3 with guidance on cluster size.
- Per-tool failure modes with fixes for known pitfalls (depth-related first component in Signac, TileMatrix vs PeakMatrix, memory quirks in SnapATAC2, ATAC-specific empty droplets in Cell Ranger ATAC, WNN weighting in Multiome).
When to use it
Use when processing 10X scATAC data from cellranger output or Multiome, needing per-cell QC, ecosystem choice guidance, cluster-level peak calling, scRNA-seq integration, or doublet detection. Triggered by workflows that require per-cell QC, cross-ecosystem comparisons, or differential accessibility analyses per cluster.
What it can touch
It mentions tools and commands such as:
- R: Signac, Seurat, ArchR, and associated functions like CreateChromatinAssay, RunTFIDF, RunSVD, RunUMAP, FindNeighbors, FindClusters, GeneActivity, CallPeaks, etc.
- Python: snapatac2 with functions like import_fragments, add_tile_matrix, spectral, UMAP, Leiden, macs3, make_gene_matrix.
- CLI: cellranger-atac and chromap.
- External tools: MACS3, AMULET, scDblFinder, scater, MOFA+, SCENIC.
Caveats
Lists known limitations and failure modes for different tools, including depth confounding in Signac components, TileMatrix vs PeakMatrix usage, memory layout requirements in SnapATAC2, and specific caveats for Multiome WNN weighting. Also notes to verify chemistry type (10X Multiome vs single-modality scATAC) before analysis and to standardize clustering parameters when reconciling across tools.
## Version Compatibility Reference examples tested with: Cell Ranger ATAC 2.1+, Signac 1.13+, Seurat 5.0+, ArchR 1.0.2+, SnapATAC2 2.8+, AMULET 1.1+, scDblFinder 1.16+, scater 1.30+, scvi-tools 1.1+, GenomicRanges 1.54+, JASPAR2024 0.99+, BSgenome.Hsapiens.UCSC.hg38 1.4+, EnsDb.Hsapiens.v86 2.99+, MACS3 3.0+. SnapATAC2 2.8+ uses `pp.import_fragments`; older 2.5-2.7 used `pp.import_data` (renamed/removed in 2.9). Verify before use: - Python: `pip show <package>` then `help(module.function)` to check signatures - R: `packageVersion('<pkg>')` then `?function_name` to verify parameters - CLI: `<tool> --version` then `<tool> --help` to confirm flags If code throws unexpected errors, introspect the installed package and adapt rather than retrying. # Single-Cell ATAC-seq **"Process my 10X scATAC data from cellranger output"** -> Build a per-cell fragment matrix, compute per-cell QC, dimensionality reduction (TF-IDF + LSI / spectral / autoencoder), cluster, call cluster-level pseudobulk peaks, annotate cell types via gene-activity scores, and integrate with paired scRNA-seq if Multiome. - R: `Signac::CreateChromatinAssay()` -> `Seurat` workflow (TF-IDF + SVD + UMAP + Leiden) - R: `ArchR::c
- Version Compatibility
- Ecosystem Choice (The Most Important Decision)
- 10X Multiome Caveat (Paired RNA + ATAC)
- Per-Cell QC Thresholds
- Doublet Detection: Three Approaches
- Per-Tool Failure Modes
- Signac TF-IDF + SVD -- First component is depth
- ArchR -- TileMatrix vs PeakMatrix confusion
- SnapATAC2 -- Memory layout assumes integer counts
- Cell Ranger ATAC -- Empty droplet detection
- Multiome WNN -- ATAC weighting
- Per-cluster pseudobulk peak calling -- Empty clusters
- Decision Tree by Goal
- Standard Signac Workflow
What does the bio-atac-seq-single-cell-atac skill do?
Process and analyze single-cell ATAC-seq data with Signac, ArchR, SnapATAC2, or Cell Ranger ATAC. Use when handling 10X scATAC or 10X Multiome (paired RNA+ATAC) data, performing per-cell QC, choosing between ArchR/Signac/SnapATAC2 ecosystems, building per-cluster consensus peaksets, integrating with paired scRNA-seq, doublet detection (AMULET vs ArchR vs scDblFinder), or running pseudobulk differential accessibility per cluster.
How do I install it?
Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill single-cell-atac --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.
