Agent skill

Bio Chipseq Cut And Run Tag

by GPTomics in GPTomics/bioSkills

Analyzes CUT&RUN (Skene Henikoff 2017) and CUT&Tag (Kaya-Okur 2019) chromatin profiling data.

MITAuto-check passedDatabases

Install Bio Chipseq Cut And Run Tag

skills CLI
$ npx skills add GPTomics/bioSkills --skill bio-chipseq-cut-and-run-tag -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install GPTomics/bioSkills bio-chipseq-cut-and-run-tag --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/GPTomics/bioSkills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/chip-seq/cut-and-run-tag .claude/skills/bio-chipseq-cut-and-run-tag && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bio-chipseq-cut-and-run-tag
GitHub stars
1.2k
Used in
2 other repos
Token cost
~4k tokens
SKILL.md length
1,693 words
Files
3
Skills in repo
559
Repo updated
First seen
Licence
MIT

At a glance

Analyzes CUT&RUN (Skene Henikoff 2017) and CUT&Tag (Kaya-Okur 2019) chromatin profiling data.

  • Calling peaks from CUT&RUN/CUT&Tag
  • SKILL.md covers Version Compatibility, Protocol Variant Taxonomy, Algorithmic Taxonomy and SEACR Workflow (Canonical…, plus 8 more sections
  • Runs Shell scripts from its folder; calls bash
  • Tasks that involve Database schema design

What it does

Bio Chipseq Cut And Run Tag is an agent skill from GPTomics/bioSkills. 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…

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `examples/cutandrun_pipeline.sh` and `usage-guide.md`).

It sits in Databases, covering Database schema design and Bioinformatics. The repository describes itself as: a set of SKILLS.md for doing bioinformatics with agents like claude code. The licence is MIT.

When your agent uses it

  • Calling peaks from CUT&RUN/CUT&Tag
  • Tasks that involve Database schema design
  • Tasks that involve Bioinformatics

Example prompts

  • “Use the bio-chipseq-cut-and-run-tag skill to analyz CUT&RUN (Skene Henikoff 2017) and CUT&Tag (Kaya-Okur 2019) chromatin profiling data”
  • “/bio-chipseq-cut-and-run-tag”

Requirements

  • A Bash shell

What it can do on your machine

Read from SKILL.md and the folder at commit d91ed3d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bio Chipseq Cut And Run Tag loads about 4k tokens when it runs. Until then it costs about 156 tokens; SKILL.md has 1,693 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~156
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from GPTomics/bioSkills at commit d91ed3d, republished under its MIT licence (© GPTomics). 1,693 words, ~3,987 tokens.

Download SKILL.mdSave it as .claude/skills/bio-chipseq-cut-and-run-tag/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
bio-chipseq-cut-and-run-tag
description
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.
tool_type
mixed
primary_tool
SEACR

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).

Show full SKILL.md (700 more words)Show less
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)
  • 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

© GPTomics, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in chip-seq/cut-and-run-tag of GPTomics/bioSkills.

  • SKILL.md
  • examples/cutandrun_pipeline.sh
  • usage-guide.md

Open the folder on GitHubat commit d91ed3d

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in GPTomics/bioSkills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Bio Chipseq Cut And Run Tag next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bio Chipseq Cut And Run Tag compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bio Chipseq Cut And Run Tag this skillGPTomics/bioSkills1.2k2 repos~4kAutomated safety check: PassMIT
Tooluniverse Metabolomics Analysiswu-yc/LabClaw1.1k2 repos~5.9kAutomated safety check: PassNone
Bio Spatial Transcriptomics Spatial PreprocessingFreedomIntelligence/OpenClaw-Medical-Skills3.1k1 repos~2kAutomated safety check: PassNone
Gene Protein Expression Matrix Normalizationaipoch/medical-research-skills1.9k—~1.5kAutomated safety check: PassMIT
Bio Crispr Screens Batch CorrectionFreedomIntelligence/OpenClaw-Medical-Skills3.1k—~2.6kAutomated safety check: PassNone
Tooluniverse Rnaseq Deseq2wu-yc/LabClaw1.1k2 repos~4.5kAutomated safety check: PassNone

Similar skills

  • Analyze metabolomics data including metabolite identification, quantification, pathway analysis, and metabolic flux.

    1.1k GitHub starsUsed in 2 repos~5.9k tokens
    Research & ScienceAuto-check passed
  • Bio Spatial Transcriptomics Spatial Preprocessing

    FreedomIntelligence/OpenClaw-Medical-Skills

    Quality control, filtering, normalization, and feature selection for spatial transcriptomics data.

    3.1k GitHub starsUsed in 1 repo~2k tokens
    Research & ScienceAuto-check passed
  • Gene Protein Expression Matrix Normalization

    aipoch/medical-research-skills

    A skill your agent uses when normalizing bulk gene or protein expression matrices with log2 transform, z-score standardization, or min-max scaling before downstream visualization or exploratory…

    1.9k GitHub stars~1.5k tokensUpdated 24 days ago
    Research & ScienceAuto-check passed
  • Bio Crispr Screens Batch Correction

    FreedomIntelligence/OpenClaw-Medical-Skills

    Batch effect correction for CRISPR screens. An agent skill from FreedomIntelligence/OpenClaw-Medical-Skills.

    3.1k GitHub stars~2.6k tokensUpdated 2 mo ago
    Research & ScienceAuto-check passed
  • Production-ready RNA-seq differential expression analysis using PyDESeq2.

    1.1k GitHub starsUsed in 2 repos~4.5k tokens
    Research & ScienceAuto-check passed
  • Bio Single Cell Preprocessing

    FreedomIntelligence/OpenClaw-Medical-Skills

    Quality control, filtering, and normalization for single-cell RNA-seq using Seurat (R) and Scanpy (Python).

    3.1k GitHub starsUsed in 1 repo~2.4k tokens
    Research & ScienceAuto-check passed

More from GPTomics/bioSkills

All 559 skills in this repo
  • Bio Alignment Io

    GPTomics/bioSkills

    Read, write, and convert multiple sequence alignment files using Biopython Bio.AlignIO.

    1.2k GitHub starsUsed in 3 repos~4.9k tokens
    Auto-check passed
  • bioSkills Installer

    GPTomics/bioSkills

    Installs the bioSkills collection of 425 bioinformatics skills in one step, or only chosen categories, so sequencing, RNA-seq, single-cell and variant tasks get specialized help.

    1.2k GitHub starsUsed in 1 repo~789 tokens
    Auto-check passed
  • Bio Write Sequences

    GPTomics/bioSkills

    Write biological sequences to files (FASTA, FASTQ, GenBank, EMBL) using Biopython Bio.SeqIO.

    1.2k GitHub starsUsed in 3 repos~2.1k tokens
    Auto-check passed
  • Amplicon Primer Clipping

    GPTomics/bioSkills

    Soft- or hard-clips PCR primer footprints from aligned amplicon BAMs so primer bases stop masquerading as confirmed reference sequence.

    1.2k GitHub starsUsed in 2 repos~2.2k tokens
    Auto-check passed
  • Filters BAM alignments by FLAG bits, mapping quality and regions with samtools view or pysam, with recipes for common keep and drop cases.

    1.2k GitHub starsUsed in 2 repos~3.6k tokens
    Auto-check passed
  • Bio Alignment Indexing

    GPTomics/bioSkills

    Create and use BAI/CSI indices for BAM/CRAM files using samtools and pysam.

    1.2k GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check passed

Questions about Bio Chipseq Cut And Run Tag

What does Bio Chipseq Cut And Run Tag do?

Analyzes CUT&RUN (Skene Henikoff 2017) and CUT&Tag (Kaya-Okur 2019) chromatin profiling data. Bio Chipseq Cut And Run Tag is an agent skill from GPTomics/bioSkills. Analyzes CUT&RUN (Skene Henikoff 2017) and CUT&Tag (Kaya-Okur 2019) chromatin profiling data.

When should I use Bio Chipseq Cut And Run Tag?

Bio Chipseq Cut And Run Tag fits situations like: calling peaks from CUT&RUN/CUT&Tag; tasks that involve Database schema design; tasks that involve Bioinformatics.

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

Run `npx skills add GPTomics/bioSkills --skill bio-chipseq-cut-and-run-tag -a claude-code`. Or copy the skill folder (chip-seq/cut-and-run-tag in GPTomics/bioSkills) into .claude/skills/bio-chipseq-cut-and-run-tag in your project. Claude Code loads it when a task matches its description.

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

Run `npx skills add GPTomics/bioSkills --skill bio-chipseq-cut-and-run-tag -a codex`. Or copy the skill folder (chip-seq/cut-and-run-tag in GPTomics/bioSkills) into .agents/skills/bio-chipseq-cut-and-run-tag in your project. Codex loads it when a task matches its description.

Can I use Bio Chipseq Cut And Run Tag in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GPTomics/bioSkills --skill bio-chipseq-cut-and-run-tag -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bio-chipseq-cut-and-run-tag, .gemini/skills/bio-chipseq-cut-and-run-tag, .github/skills/bio-chipseq-cut-and-run-tag and .opencode/skills/bio-chipseq-cut-and-run-tag in your project.

What does Bio Chipseq Cut And Run Tag need to run?

Going by SKILL.md and its folder, Bio Chipseq Cut And Run Tag needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell.

Does Bio Chipseq Cut And Run Tag access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Bio Chipseq Cut And Run Tag safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bio Chipseq Cut And Run Tag use?

Bio Chipseq Cut And Run Tag is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bio Chipseq Cut And Run Tag use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bio Chipseq Cut And Run Tag?

Skills that share tags, products or a category with Bio Chipseq Cut And Run Tag: Tooluniverse Metabolomics Analysis (wu-yc/LabClaw, 1.1k stars), Bio Spatial Transcriptomics Spatial Preprocessing (FreedomIntelligence/OpenClaw-Medical-Skills, 3.1k stars), Gene Protein Expression Matrix Normalization (aipoch/medical-research-skills, 1.9k stars) and Bio Crispr Screens Batch Correction (FreedomIntelligence/OpenClaw-Medical-Skills, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bio Chipseq Cut And Run Tag?

GPTomics (a GitHub organization) maintains it in GPTomics/bioSkills, which has 1,218 GitHub stars. The repository holds 559 skills in this directory. The repository was last updated on August 15, 2026.

Source: GPTomics/bioSkills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.