Bio Chipseq Cut And Run Tag logo

Bio Chipseq Cut And Run Tag

Organization
PKU-YuanGroup
bio-chipseq-cut-and-run-tag

Analyzes CUT&RUN (Skene Henikoff 2017) and CUT&Tag (Kaya-Okur 2019) chromatin profiling data. Handles SEACR vs MACS2 peak calling (with the btaf375 2025 benchmark guidance), pA-MNase vs pA-Tn5 vs pAG-Tn5 chimera differences, E. coli spike-in carryover normalization, IgG-only control logic (no input), characteristic fragment-size signatures (25-75 bp for CUT&Tag), and lower depth requirements (5M reads typical vs 25M for ChIP). Use when calling peaks from CUT&RUN/CUT&Tag, scaling by E. coli spike-in carryover, choosing SEACR norm mode, or comparing CUT&RUN/Tag results to traditional ChIP.

Overview

PublisherPKU-YuanGroup
RepositoryOpenAI4S
Skill namebio-chipseq-cut-and-run-tag
Stars
622
Forks
72
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by PKU-YuanGroup on GitHub. Read the source before you install it.

Installation

Install the Bio Chipseq Cut And Run Tag AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/PKU-YuanGroup/OpenAI4S/tree/main/skills/bioskills/bio-chip-seq-cut-and-run-tag
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/PKU-YuanGroup/OpenAI4S.git /tmp/OpenAI4S
mkdir -p .claude/skills
cp -r /tmp/OpenAI4S/skills/bioskills/bio-chip-seq-cut-and-run-tag .claude/skills/bio-chipseq-cut-and-run-tag
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bio Chipseq Cut And Run Tag in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bio Chipseq Cut And Run Tag on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bio Chipseq Cut And Run Tag is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Version Compatibility

Reference examples tested with: SEACR 1.3+, MACS2 2.2.9+, MACS3 3.0.4+, samtools 1.19+, bowtie2 2.5+, bedtools 2.31+, deepTools 3.5+, GoPeaks 1.0+, LanceOtron (pip).

CUT&RUN / CUT&Tag

"Analyze CUT&RUN or CUT&Tag chromatin profiling data" -> Use the lower-background, lower-input alternatives to traditional ChIP. CUT&RUN tethers MNase to an antibody via Protein A; CUT&Tag tethers Tn5 via Protein A/G. Both bypass cross-linking, fragmentation, and IP washes — producing 10-100× lower background, allowing 100-1000× lower cell input, and shifting the peak-calling problem from "find signal in noise" to "find signal in near-zero background."

  • Aligner: bowtie2 (CUT&RUN/Tag standard) or bwa-mem; chromap optional
  • Peak calling (CUT&RUN/Tag): SEACR (Meers 2019), MACS2 with -f BAMPE --keep-dup all, or both for consensus
  • Spike-in: E. coli carryover from bacterially-produced pA-MNase/Tn5 (automatic, variable)
  • Control: IgG-only (no input control; native chromatin has no meaningful "input")

CUT&RUN/CUT&Tag has different QC thresholds, different peak calling defaults, different spike-in protocols, and different antibody requirements than traditional ChIP. Treating it as ChIP fails silently.

Protocol Variant Taxonomy

VariantChimeraYearUse caseFailure mode
CUT&RUN (Skene Henikoff)pA-MNase2017Native chromatin profiling; broad antibody compatibilityNative (no fixation) — gentler; MNase digest needs careful Ca²⁺ control
CUT&Tag (Kaya-Okur Henikoff)pA-Tn5 (rabbit only)2019Lower cell input (~5000); faster; library-ready outputRabbit-only antibody; PCR cycles can over-amplify
CUT&Tag-IT (Active Motif)pA-Tn5 commercial2020Standardized lots; reproducibleCost; vendor-locked
pAG-Tn5 CUT&TagpAG-Tn52020Binds both rabbit AND mouse IgGMore versatile; identical performance otherwise
AutoCut&TagpAG-Tn5 plate-based2021High-throughput (96-well)Throughput at the cost of per-sample optimization
CUTAC (CUT&Tag-then-ATAC)pAG-Tn5 + protocol modification2020Chromatin accessibility variant of CUT&TagLess common; not standard CUT&Tag
scCUT&TagpAG-Tn5 in droplets2021Single-cell histone mark profilingVery sparse (~1000-5000 reads/cell)

Algorithmic Taxonomy

ToolModelStrengthFails when
SEACR (Meers 2019)Empirical threshold on signal block totals; IgG-aware "stringent" modeDesigned for sparse CUT&RUN data; "stringent + norm + IgG" is the recommended defaultWrong mode (top-X% without IgG; "non" mode if no upstream spike-in normalization); broad mark with very flat signal landscape
MACS2 -f BAMPE --keep-dup allLocal PoissonFamiliar; integrates well with downstream tools (DiffBind)Default -q 0.05 may be too lenient for low-background CUT&Tag; consider -q 0.01
GoPeaks (Yashar 2022)Sliding-window thresholdingBroad-mark-oriented; faster than SEACR on broad dataNewer; smaller user base
LanceOtron (Hentges 2022)CNN trained on ENCODE peaksParameter-free; handles both narrow and broadLess validated for CUT&RUN/Tag specifically; web-only or pip
MACS2 + SEACR consensusIntersectionHighest confidence; conservative two-caller intersectionMost conservative; may miss true peaks at marginal regions

2025 benchmark (Bioinformatics 41:btaf375, Nooranikhojasteh et al): benchmarked MACS2, SEACR, GoPeaks and LanceOtron on CUT&RUN.

  • MACS2 better for sharp peaks (H3K4me3, TFs)
  • SEACR gave the highest signal-to-noise across marks
  • No single caller is universally optimal; the study favors careful parameter tuning or ensemble/consensus approaches over any single tool

SEACR Workflow (Canonical CUT&RUN/Tag Caller)

Goal: Call CUT&RUN/CUT&Tag peaks from aligned BAMs using SEACR with IgG-aware threshold.

Approach: Align with Henikoff parameters, convert BAM to fragment bedGraph via bamtobed-bedpe, then invoke SEACR with norm stringent mode and IgG control.

bash
# 1. Align with bowtie2 (Henikoff lab standard parameters)
bowtie2 --local --very-sensitive --no-mixed --no-discordant \
    --phred33 -I 10 -X 700 \
    -x hg38 -1 reads_R1.fq -2 reads_R2.fq \
    -S aln.sam

# 2. Convert SAM to BAM, sort, index
samtools view -bS aln.sam | samtools sort -o aln.bam
samtools index aln.bam

# 3. Generate bedGraph for SEACR (paired-end fragments)
samtools view -bS -F 0x04 aln.bam | bedtools bamtobed -bedpe -i - > aln.bedpe
awk '$1==$4 && $6-$2 < 1000 {print $0}' aln.bedpe > aln.clean.bedpe
cut -f 1,2,6 aln.clean.bedpe | sort -k1,1 -k2,2n -k3,3n > aln.fragments.bed
bedtools genomecov -bg -i aln.fragments.bed -g hg38.chrom.sizes > aln.bedgraph

# 4. Same for IgG control
# (... produce igg.bedgraph similarly ...)

# 5. SEACR with stringent + norm + IgG control (recommended default).
# Final argument is the OUTPUT PREFIX; SEACR appends ".stringent.bed" / ".relaxed.bed".
bash SEACR_1.3.sh aln.bedgraph igg.bedgraph norm stringent target_peaks
# Output file: target_peaks.stringent.bed

# Alternative: no IgG control, use top 1% of peaks
# bash SEACR_1.3.sh aln.bedgraph 0.01 non stringent target_peaks

SEACR mode selection:

  • norm (recommended): scales target to IgG distribution
  • non: use ONLY if upstream spike-in normalization was applied; otherwise use norm
  • stringent: top-half of signal blocks (recommended default)
  • relaxed: full distribution (use only for very sparse signal)
  • IgG control: bash SEACR_1.3.sh target.bg igg.bg norm stringent out_prefix -> writes out_prefix.stringent.bed
  • Top-X% without IgG: bash SEACR_1.3.sh target.bg 0.01 non stringent out_prefix -> writes out_prefix.stringent.bed

E. coli Spike-In Carryover (Automatic Spike-In)

CUT&RUN/CUT&Tag spike-in is "free" because the pA-MNase or pA-Tn5 carries E. coli DNA from bacterial production. Carryover is variable across batches but stable within a batch.

bash
# Align reads to combined hg38 + E. coli genome (or sequential)
bowtie2 -x hg38_ecoli_combined -1 R1.fq -2 R2.fq -S aln.sam

# Count E. coli reads per sample
ECOLI_READS=$(samtools view -c -F 4 aln.bam ecoli_chr1)

# Scaling factor: smallest E. coli read count / per-sample E. coli reads
# Apply BEFORE peak calling for cross-condition comparison

Expected E. coli alignment fractions:

  • Target ChIP samples: 0.5-2% of total reads
  • IgG control: 2-5% (higher because no target chromatin to dilute)
  • Below 0.1% E. coli: spike-in carryover lost; cross-condition normalization unreliable
  • Above 10%: target ChIP failed (mostly E. coli)

The carryover is variable between batches of bacterial production; single-experiment carryover spike-in is noisier than deliberate Drosophila spike-in (ChIP-Rx). For high-stakes cross-condition claims, add deliberate Drosophila spike-in despite the E. coli carryover. See chip-seq/spike-in-normalization.

QC Differences from Traditional ChIP

MetricTraditional ChIPCUT&RUN/CUT&Tag
FRiP (TF)> 0.05> 0.10 (often > 0.25)
FRiP (histone)> 0.10> 0.25
Library size requirement20-50M3-10M (often sufficient)
Input controlRequiredIgG only (no input meaningful)
Fragment size (CUT&Tag)Sub-nucleosomal or mono-nucleosomalSharp peak at 25-75 bp (Tn5 staggered cuts)
Fragment size (CUT&RUN)VariableMono- + di-nucleosomal pattern
DuplicatesRemove (MarkDuplicates)Keep for CUT&Tag (low PCR cycles, dups have biology)
Spike-in alignmentDeliberate (Drosophila); 0.5-5%Automatic E. coli; 0.5-5%
Cell input1-10M5,000-100,000

Critical: --keep-dup all in MACS for CUT&Tag. PCR cycles are 12-15 (vs 5-8 for ChIP); duplicates at high-coverage TF binding sites contain biology. The MACS default --keep-dup 1 (keeps one read per position) will over-deduplicate CUT&Tag data.

Fragment Size as Diagnostic (Critical for CUT&Tag)

bash
samtools view -f 0x2 sample.bam | awk '{print $9}' | awk '$1>0' \
    | sort -n | uniq -c | awk '{print $2, $1}' > frag_sizes.tsv

Expected for CUT&Tag:

  • Sharp peak at 25-75 bp (Tn5 staggered insertion = ~9 bp + protein-DNA-protein interaction)
  • Secondary peak at ~150-200 bp (mono-nucleosomal CUT&Tag from H3K4me3 etc)
  • < 25 bp: Tn5 self-tagmentation noise; high abundance indicates over-tagmentation
  • Flat distribution above 200 bp: poor enzyme activity or over-amplification

Expected for CUT&RUN:

  • Mono-nucleosomal (~150 bp) for histone marks
  • Sub-nucleosomal (~50-100 bp) for TFs (rare; CUT&RUN better for histones)
  • Di-nucleosomal (~300 bp) secondary peak common

Per-Tool Failure Modes

SEACR -- Wrong mode for context

Trigger: Using non mode without prior spike-in normalization; using relaxed mode on standard CUT&Tag.

Mechanism: non assumes target is already scaled to IgG (typical for ChIP-Rx-style spike-in); on raw counts, it inflates false positives. relaxed includes the full distribution; appropriate only for sparse signal.

Fix: Default to norm stringent with IgG control. Use non only when upstream spike-in scaling has been applied.

CUT&Tag MACS2 -- Default --keep-dup 1 removes biology

Trigger: Using MACS2 default dedup settings on CUT&Tag.

Mechanism: Low PCR cycles (12-15) in CUT&Tag mean PCR duplicates contain real biology at high-coverage sites; auto-dedup over-filters.

Symptom: Peak counts much lower than published for same antibody / cell line.

Fix: macs2 callpeak --keep-dup all -f BAMPE for CUT&Tag. For CUT&RUN, dedup behavior depends on PCR cycles — verify with library complexity (NRF).

pA-Tn5 vs pAG-Tn5 -- Antibody species mismatch

Trigger: Using pA-Tn5 (Henikoff original) with mouse primary antibody.

Mechanism: Protein A binds rabbit IgG much better than mouse IgG; mouse antibodies give weak signal with pA-Tn5.

Fix: Use pAG-Tn5 (binds both); or switch to a rabbit primary antibody for the same target.

Digitonin permeabilization -- Wrong concentration

Trigger: Default 0.05% digitonin on all cell lines.

Mechanism: Optimal digitonin varies by cell type (some need 0.02%, some 0.1%); over-permeabilization releases chromatin into supernatant; under-permeabilization prevents antibody access.

Symptom: Inconsistent signal across cell lines; high IgG signal (under-permeabilized) or low target signal (over-permeabilized).

Fix: Titrate digitonin per cell line using a known-positive H3K4me3 antibody as control.

ConA bead vs sepharose -- Volume / sample mismatch

Trigger: Switching bead type between protocols without adjusting volume.

Mechanism: ConA magnetic beads (e.g., Bangs) and sepharose ConA have different binding capacities; protocols designed for one give wrong cell loading for the other.

Fix: Follow Henikoff lab protocol exactly for the chosen bead; or titrate cell number per bead volume.

Adapter readthrough in short fragments

Trigger: 100-150 bp reads on 25-75 bp CUT&Tag fragments.

Mechanism: Reads longer than fragments read through both adapters; downstream alignment loses the fragment.

Symptom: Many reads with adapter sequence at 3' end; alignment rate drops.

Fix: Aggressive adapter trimming with cutadapt: -e 0.1 -O 5 --minimum-length 25. Use 50 bp paired-end sequencing for CUT&Tag instead of 150 bp.

MACS2 fragment-size modeling failure on CUT&Tag

Trigger: Running MACS2 without -f BAMPE on CUT&Tag PE data.

Mechanism: MACS2 in -f BAM mode tries to model fragment size from cross-correlation; CUT&Tag fragments are 25-75 bp, not the 200 bp ChIP expects; modeling fails or produces wrong estimate.

Fix: Always use -f BAMPE for CUT&Tag; MACS uses actual fragment spans from mate pairs.

Reconciliation: When CUT&RUN/Tag Disagrees with ChIP

PatternLikely causeAction
Peak count much lower in CUT&Tag vs ChIPLower background reveals signal vs noise; CUT&Tag often has FEWER but cleaner peaksBoth correct; CUT&Tag specificity > sensitivity
Peak count much higher in CUT&Tag vs ChIP--keep-dup all retained PCR duplicates as peaksVerify NRF; if low, consider deduplicating with caution
Same antibody, different signalNative chromatin vs cross-linked accessibility differsNative CUT&RUN may miss DSG-dependent cofactors (BRD4); add brief fixation
FRiP very high (>50%)Likely real for CUT&Tag (low background); confirm with motif enrichmentVerify motif enrichment at peaks; if missing, suspect technical artifact
H3K4me3 CUT&Tag peak count differs from ChIPExpected; CUT&Tag has higher specificityTrust CUT&Tag for sharp marks
H3K27me3 CUT&RUN/Tag misses regionsBroad domains require deeper sequencing; CUT&Tag was designed for sharp marksUse CUT&RUN or traditional ChIP for very broad marks

Common Errors

Error / symptomCauseSolution
SEACR "input file not bedgraph"Wrong file formatUse bedtools genomecov -bg; not bedGraphToBigWig output
MACS2 modeling fails on CUT&TagDefault -f BAM on PE-f BAMPE
Peak count for mouse antibodyUsed pA-Tn5 not pAG-Tn5Switch to pAG-Tn5 OR use rabbit primary
Very high adapter content in FASTQRead length > fragment lengthTrim aggressively; consider 50 bp PE for CUT&Tag
Sample-to-sample carryover variability >5xE. coli carryover variable between bacterial production batchesAdd deliberate Drosophila spike-in for cross-condition
IgG signal as strong as targetFailed antibody / over-permeabilizationValidate antibody on positive control; titrate digitonin

References

  • Skene PJ & Henikoff S 2017 eLife 6:e21856 (CUT&RUN)
  • Skene PJ Henikoff JG & Henikoff S 2018 Nat Protoc 13:1006 (CUT&RUN protocol)
  • Kaya-Okur HS et al 2019 Nat Commun 10:1930 (CUT&Tag)
  • Kaya-Okur HS et al 2020 Nat Protoc 15:3264 (CUT&Tag protocol)
  • Meers MP et al 2019 Epigenetics Chromatin 12:42 (SEACR)
  • Nooranikhojasteh A et al 2025 Bioinformatics 41:btaf375 (CUT&RUN peak-caller benchmark)
  • Yashar WM et al 2022 Genome Biol 23:144 (GoPeaks)
  • Hentges LD et al 2022 Bioinformatics 38:4255 (LanceOtron)
  • Bartosovic M Kabbe M & Castelo-Branco G 2021 Nat Biotechnol 39:825 (scCUT&Tag)
  • Janssens DH et al 2021 Nat Genet 53:1586 (AutoCUT&Tag)
  • Li Q et al 2024 Nat Methods 21:2044 (scNanoSeq-CUT&Tag, long-read single-cell CUT&Tag)

Related Skills

  • chip-seq/peak-calling - Traditional ChIP peak calling (MACS3 + IDR vs naive overlap)
  • chip-seq/chipseq-qc - QC battery (different thresholds for CUT&RUN/Tag)
  • chip-seq/spike-in-normalization - Deliberate Drosophila spike-in beyond E. coli carryover
  • chip-seq/differential-binding - DiffBind / csaw differential on CUT&RUN/Tag
  • chip-seq/peak-annotation - Annotate CUT&RUN/Tag peaks (same tools as ChIP)
  • chip-seq/super-enhancers - SE calling on CUT&Tag H3K27ac
  • alignment-files/sam-bam-basics - BAM preparation
  • read-qc/adapter-trimming - Aggressive trimming for short fragments

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Bio Chipseq Cut And Run Tag AI skill do?

Analyzes CUT&RUN (Skene Henikoff 2017) and CUT&Tag (Kaya-Okur 2019) chromatin profiling data. Handles SEACR vs MACS2 peak calling (with the btaf375 2025 benchmark guidance), pA-MNase vs pA-Tn5 vs pAG-Tn5 chimera differences, E. coli spike-in carryover normalization, IgG-only control logic (no input), characteristic fragment-size signatures (25-75 bp for CUT&Tag), and lower depth requirements (5M reads typical vs 25M for ChIP). Use when calling peaks from CUT&RUN/CUT&Tag, scaling by E. coli spike-in carryover, choosing SEACR norm mode, or comparing CUT&RUN/Tag results to traditional ChIP.

Why use Bio Chipseq Cut And Run Tag on TypingMind?

Because you install it once and use it with any model. Bio Chipseq Cut And Run Tag is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bio Chipseq Cut And Run Tag in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/PKU-YuanGroup/OpenAI4S/tree/main/skills/bioskills/bio-chip-seq-cut-and-run-tag. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Bio Chipseq Cut And Run Tag?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bio Chipseq Cut And Run Tag?

As many as you like. As long as a model supports skills, you can use Bio Chipseq Cut And Run Tag with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bio Chipseq Cut And Run Tag AI skill free?

Yes. It is published on GitHub by PKU-YuanGroup under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇