Agent skill · Data & Analytics

bio-atac-seq-nucleosome-positioning

Extract nucleosome positions from ATAC-seq data using NucleoATAC, ATACseqQC, and fragment analysis. Use when analyzing chromatin organization, identifying nucleosome-free regions at promoters, or characterizing nucleosome occupancy patterns from ATAC-seq fragment size distributions.

FreedomIntelligencegithub.com/FreedomIntelligenceGitHub ↗
claude-code
Install
npx skills add FreedomIntelligence/OpenClaw-Medical-Skills --skill bio-atac-seq-nucleosome-positioning --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/bio-atac-seq-nucleosome-positioning/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,909
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Version Compatibility Reference examples tested with: Rsamtools 2.18+, matplotlib 3.8+, numpy 1.26+, pyBigWig 0.3+, pysam 0.22+, samtools 1.19+ Before using code patterns, verify installed versions match. If versions differ: - 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 ImportError, AttributeError, or TypeError, introspect the installed package and adapt the example to match the actual API rather than retrying. # Nucleosome Positioning **"Map nucleosome positions from ATAC-seq"** → Separate nucleosome-free and mono-nucleosome fragments by size, then call nucleosome center positions and occupancy scores. - CLI: `nucleoatac run --bed peaks.bed --bam atac.bam --fasta ref.fa` - R: `ATACseqQC::splitGAlignmentsByCut()` for fragment separation Extract nucleosome positions and occupancy from ATAC-seq fragment size patterns. ## Background ATAC-seq fragments reflect chromatin structure: - **< 100 bp**: Nucleosome-free regions (NFR) - **180-247 bp**: Mono-nucleosome - **315-473 bp**: Di-nucleosome - **558-

What's inside
Steps it walks through
  1. Version Compatibility
  2. Background
  3. ATACseqQC (R)
  4. Installation
  5. Fragment Size Distribution
  6. Nucleosome Positioning
  7. V-Plot (Fragment Size vs Position)
  8. Footprinting
  9. NucleoATAC (Python)
  10. Run NucleoATAC
  11. Output Files
  12. Visualize Output
  13. Fragment Analysis (Custom)
  14. Extract Fragment Sizes
Ships with 2 files
  • examples/nucleosome_analysis.R
  • usage-guide.md
Commands it runs
pip install nucleoatac
Call nucleosomes
nucleoatac run --bed regions.bed --bam sample.bam --fasta reference.fa \
Convert to bigWig for visualization
bedGraphToBigWig nucleoatac_output.occ.bedgraph chrom.sizes nucleosome_occ.bw
Extract nucleosome-free reads
samtools view -h sample.bam | \
awk '$9 > -100 && $9 < 100 || $1 ~ /^@/' | \
samtools view -b > nfr.bam
Extract mono-nucleosome reads
More from OpenClaw-Medical-Skills
All skills →
About this skill
What does the bio-atac-seq-nucleosome-positioning skill do?

Extract nucleosome positions from ATAC-seq data using NucleoATAC, ATACseqQC, and fragment analysis. Use when analyzing chromatin organization, identifying nucleosome-free regions at promoters, or characterizing nucleosome occupancy patterns from ATAC-seq fragment size distributions.

How do I install it?

Run `npx skills add FreedomIntelligence/OpenClaw-Medical-Skills --skill bio-atac-seq-nucleosome-positioning --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 FreedomIntelligence/OpenClaw-Medical-Skills, a repository with 2,909 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.

Keep going