Agent skill

Bio Workflows Chipseq Pipeline

by GPTomics in GPTomics/bioSkills

Orchestrates the end-to-end ChIP-seq pipeline from FASTQ to blacklist-filtered, annotated peaks, chaining fastp QC, Bowtie2 alignment, pre-dedup library-complexity QC (NRF/PBC), duplicate removal…

MITAuto-check passedResearch & Science

Install Bio Workflows Chipseq Pipeline

skills CLI
$ npx skills add GPTomics/bioSkills --skill bio-workflows-chipseq-pipeline -a claude-code

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

GitHub CLI
$ gh skill install GPTomics/bioSkills bio-workflows-chipseq-pipeline --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/workflows/chipseq-pipeline .claude/skills/bio-workflows-chipseq-pipeline && 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-workflows-chipseq-pipeline
GitHub stars
1.2k
Used in
1 other repo
Token cost
~4k tokens
SKILL.md length
1,290 words
Files
4
Skills in repo
559
Repo updated
First seen
Licence
MIT

At a glance

Orchestrates the end-to-end ChIP-seq pipeline from FASTQ to blacklist-filtered, annotated peaks, chaining fastp QC, Bowtie2 alignment, pre-dedup library-complexity QC (NRF/PBC), duplicate removal…

  • Works in 4 steps: The reference build + blacklist version… → An IP is only interpretable against its… → Library-complexity QC (NRF/PBC1/PBC2) is… → …
  • Committing the reference build + blacklist version + effective genome size once
  • SKILL.md covers Version Compatibility, The governing principle, Pipeline map and Made-once commitments, plus 9 more sections
  • Runs Shell and R scripts from its folder

What it does

Bio Workflows Chipseq Pipeline is an agent skill from GPTomics/bioSkills. Orchestrates the end-to-end ChIP-seq pipeline from FASTQ to blacklist-filtered, annotated peaks, chaining fastp QC, Bowtie2 alignment, pre-dedup library-complexity QC (NRF/PBC), duplicate removal, chrM + ENCODE-blacklist filtering, MACS3 peak calling against a matched input, IDR/consensus reproducibility, deepTools signal tracks, and ChIPseeker annotation. Use when committing the reference build + blacklist version + effective genome size once, pairing each IP with its matched control, computing complexity…

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

It sits in Research & Science, covering Bioinformatics, Reproducible research and Database schema design. 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

  • Committing the reference build + blacklist version + effective genome size once
  • Pairing each IP with its matched control
  • Computing complexity metrics BEFORE dedup
  • Choosing narrow vs broad and MACS3 vs SEACR/Genrich

Example prompts

  • “Use the bio-workflows-chipseq-pipeline skill to orchestrate the end-to-end ChIP-seq pipeline from FASTQ to blacklist-filtered, annotated peaks…”
  • “/bio-workflows-chipseq-pipeline”

Requirements

  • A Bash shell

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. The reference build + blacklist version + effective genome size is one coordinate commitment made once and inherited by everything…
  2. An IP is only interpretable against its matched control — the control IS the enrichment background. Calling peaks without the right…
  3. Library-complexity QC (NRF/PBC1/PBC2) is computed on the PRE-dedup BAM. After markdup -r the duplicates are gone, so computing complexity…
  4. Normalization must not silently undo the experiment. deepTools RPKM/CPM rescales every library to the same depth, which ERASES a spike-in…

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 and R), which the agent can run.

    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 Workflows Chipseq Pipeline loads about 4k tokens when it runs. Until then it costs about 202 tokens; SKILL.md has 1,290 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~202
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,290 words, ~4,049 tokens.

Download SKILL.mdSave it as .claude/skills/bio-workflows-chipseq-pipeline/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
bio-workflows-chipseq-pipeline
description
Orchestrates the end-to-end ChIP-seq pipeline from FASTQ to blacklist-filtered, annotated peaks, chaining fastp QC, Bowtie2 alignment, pre-dedup library-complexity QC (NRF/PBC), duplicate removal, chrM + ENCODE-blacklist filtering, MACS3 peak calling against a matched input, IDR/consensus reproducibility, deepTools signal tracks, and ChIPseeker annotation. Use when committing the reference build + blacklist version + effective genome size once, pairing each IP with its matched control, computing complexity metrics BEFORE dedup, choosing narrow vs broad and MACS3 vs SEACR/Genrich, keeping per-replicate peaks for IDR, or avoiding depth-normalization that erases a spike-in global shift. Hands mechanism to the chip-seq component skills; not a re-teach of any single step.
tool_type
mixed
primary_tool
MACS3
workflow
true
depends_on
read-qc/fastp-workflow, read-alignment/bowtie2-alignment, alignment-files/duplicate-handling, chip-seq/chipseq-qc, chip-seq/peak-calling…

Version Compatibility

Reference examples tested with: Bowtie2 2.5.3+, MACS3 3.0+, HOMER 4.11+, bedtools 2.31+, deepTools 3.5+, fastp 0.23+, samtools 1.19+, ChIPseeker 1.38+

Before using code patterns, verify installed versions match. If versions differ:

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

Note: macs3 callpeak -f BAMPE uses real fragment lengths and IGNORES --shift/--extsize/--nomodel (those apply to single-end -f BAM); the -g shortcut (hs/mm) sets the effective genome size and must match the build/read length. Confirm in-tool before quoting.

ChIP-seq Pipeline

"Process my ChIP-seq data from FASTQ to annotated peaks" -> Chain QC/trim, alignment, pre-dedup complexity QC, dedup + blacklist filtering, control-matched peak calling, reproducibility, signal tracks, and annotation.

  • CLI + R: fastp -> bowtie2 -> (NRF/PBC pre-dedup) -> samtools markdup -> chrM/blacklist filter -> macs3 callpeak (IP vs input) -> IDR -> bamCoverage -> ChIPseeker

This is a workflow skill: it owns the chaining decisions and hand-offs, not the internals of any one step. Every step below cross-references the component skill that teaches its mechanism.

The governing principle

A ChIP-seq peakset is decided at four seams, not inside the caller.

  1. The reference build + blacklist version + effective genome size is one coordinate commitment made once and inherited by everything downstream — peak coordinates, signal-track scaling, and every overlap. Blacklist filtering is a committed pipeline step, not optional cleanup: ENCODE-blacklisted regions (satellite/rDNA/high-signal artifacts) produce reproducible false peaks in every dataset regardless of biology, so they are removed before calling (Amemiya 2019).
  2. An IP is only interpretable against its matched control — the control IS the enrichment background. Calling peaks without the right input/IgG fabricates peaks at open/accessible and copy-number-amplified regions. Pair each IP with its control at the calling step.
  3. Library-complexity QC (NRF/PBC1/PBC2) is computed on the PRE-dedup BAM. After markdup -r the duplicates are gone, so computing complexity afterward reads ~1.0 and is meaningless. Compute it on the filtered, position-sorted BAM before removing duplicates.
  4. Normalization must not silently undo the experiment. deepTools RPKM/CPM rescales every library to the same depth, which ERASES a spike-in global-shift signal (the whole point of ChIP-Rx). For spike-in experiments use --scaleFactor + --normalizeUsing None; for standard experiments RPKM/CPM is fine (chip-seq/spike-in-normalization).

Reproducibility corollary: pool replicates for a consensus peakset, but keep PER-REPLICATE peaks — IDR needs individual replicates plus pooled pseudo-replicates; running IDR on an already-pooled peakset is not IDR.

Pipeline map

FASTQ (IP + matched Input, replicates)
  | [1] QC & trim -----------------> fastp                (read-qc/fastp-workflow)
  v
  | [2] Align ---------------------> bowtie2 (-q30 unique) (read-alignment/bowtie2-alignment)
  v     ^-- commitment: build + blacklist version + effective genome size
  | [3] Complexity QC (PRE-dedup) -> NRF/PBC1/PBC2         (chip-seq/chipseq-qc)
  v
  | [4] Dedup + filter ------------> markdup -r; drop chrM; SUBTRACT ENCODE blacklist  (alignment-files/duplicate-handling)
  v
  | [5] Peak calling (IP vs input)-> macs3 callpeak (narrow | --broad)  (chip-seq/peak-calling)
  v     ^-- keep PER-REPLICATE peaks for IDR
  | [6] Reproducibility -----------> IDR (per-rep + pooled pseudo-reps)  (chip-seq/peak-calling)
  v
  | [7] Signal tracks -------------> bamCoverage (RPKM | spike-in scaleFactor)  (chip-seq/chipseq-visualization)
  v
  | [8] QC + Annotate -------------> FRiP/NSC/RSC/fingerprint; ChIPseeker  (chip-seq/chipseq-qc, peak-annotation)
  v
Blacklist-filtered, annotated, reproducible peaks

Made-once commitments

CommitmentChoiceConsequence inherited downstream
Build + blacklist + effective genome sizeOne genome build; the matching ENCODE blacklist BED; -g hs/mm/numericMixed builds mis-place peaks; skipping the blacklist plants reproducible false peaks; wrong -g mis-scales p-values
Control pairingEach IP has its input/IgGNo control => peaks at open chromatin / CN-amplified loci
Peak shapeNarrow (TF, H3K4me3, H3K27ac) vs broad (H3K27me3, H3K36me3, H3K9me3)Broad marks called with narrow settings fragment into many small peaks
Fragment modelPE: -f BAMPE (real fragments); SE: -f BAM + --nomodel --extsize from predictd/xcorrBAMPE silently ignores --shift/--extsize

The canonical order and why

  1. QC/trim (fastp) both IP and input.
  2. Align (bowtie2), keep uniquely-mapped (samtools view -q 30), coordinate-sort.
  3. Compute NRF/PBC1/PBC2 on the PRE-dedup BAM — order-trap: after dedup they are meaningless.
  4. Mark/remove duplicates (collate -> fixmate -m -> sort -> markdup -r), then drop chrM and subtract the ENCODE blacklist — order-trap: skipping the blacklist leaves reproducible artifact peaks.
  5. Call peaks against the matched control (narrow or --broad).
  6. IDR on per-replicate peaks (+ pooled pseudo-replicates) — order-trap: IDR on a pooled peakset is not IDR.
  7. Signal tracks — RPKM/CPM for standard; --scaleFactor + --normalizeUsing None for spike-in (order-trap: RPKM erases the spike-in global shift).
  8. QC (FRiP/NSC/RSC/fingerprint) and annotate (ChIPseeker).

Choosing the caller and peak shape

Pipeline-level selection only; mechanism lives in the component skills.

ForkLean towardHand off to
CallerMACS3 (standard IP+input); SEACR (CUT&RUN/CUT&Tag, low background); Genrich (some ChIP/ATAC, built-in blacklist/replicate handling)chip-seq/peak-calling, chip-seq/cut-and-run-tag
Narrow vs broadNarrow: TFs, H3K4me3, H3K27ac. Broad (--broad --broad-cutoff 0.1): H3K27me3, H3K36me3, H3K9me3chip-seq/peak-calling
ReproducibilityENCODE IDR (per-rep + pooled pseudo-reps) for TFs; naive overlap acceptable for exploratory histonechip-seq/peak-calling
Consensus setPool for a union/consensus set AFTER IDR selects the reproducible thresholdchip-seq/differential-binding

Primary path: Bowtie2 + MACS3 + ChIPseeker

Goal: turn IP+input FASTQ into a blacklist-filtered, control-matched, annotated peakset.

Approach: align and keep unique reads, measure complexity before dedup, dedup + drop chrM + subtract the blacklist, call against the control, then annotate. Full runnable script: examples/narrow_peak_workflow.sh; annotation: examples/peak_annotation.R.

bash
bowtie2 -p 8 -x bt2_index/genome -1 trimmed/${s}_R1.fq.gz -2 trimmed/${s}_R2.fq.gz \
    --no-mixed --no-discordant --maxins 1000 2> aligned/${s}.log \
  | samtools view -@4 -bS -q 30 - | samtools sort -@4 -o aligned/${s}.sorted.bam
samtools index aligned/${s}.sorted.bam

# Complexity QC on the PRE-dedup BAM (NRF = distinct positions / total; PBC1 = singletons / distinct).
# Counted per-mate here (close to ENCODE fragment-level values); use `bamtobed -bedpe` for exact parity.
bedtools bamtobed -i aligned/${s}.sorted.bam | awk 'BEGIN{OFS="\t"}{print $1,$2,$3,$6}' | sort | uniq -c \
  | awk '{tot+=$1; dist++; if($1==1) one++} END{printf "NRF=%.3f PBC1=%.3f\n", dist/tot, one/dist}'

# Dedup, drop chrM, then SUBTRACT the ENCODE blacklist (committed step, not optional)
samtools collate -@8 -O -u aligned/${s}.sorted.bam | samtools fixmate -m -u - - \
  | samtools sort -@8 -u - | samtools markdup -r -@8 - aligned/${s}.dedup.bam
samtools index aligned/${s}.dedup.bam
samtools idxstats aligned/${s}.dedup.bam | cut -f1 | grep -v -e '^chrM$' -e '^MT$' \
  | xargs samtools view -b aligned/${s}.dedup.bam > aligned/${s}.nochrM.bam
bedtools intersect -v -a aligned/${s}.nochrM.bam -b ENCODE_blacklist.bed > aligned/${s}.final.bam
samtools index aligned/${s}.final.bam
bash
# Narrow (TFs, sharp marks) vs broad (spreading marks). -f BAMPE uses real fragment sizes.
macs3 callpeak -t aligned/IP_rep1.final.bam aligned/IP_rep2.final.bam \
    -c aligned/Input_rep1.final.bam aligned/Input_rep2.final.bam \
    -f BAMPE -g hs -n experiment --outdir peaks -q 0.01 --keep-dup all   # dedup done upstream (markdup -r); tell MACS3 to keep all
# Broad marks: add  --broad --broad-cutoff 0.1  (do NOT call H3K27me3 with narrow settings)

For IDR, call peaks PER REPLICATE (and on pooled pseudo-replicates) with a relaxed -q, then run idr across them (chip-seq/peak-calling). For higher confidence, intersect a second caller (HOMER -style histone for all histone marks).

Show full SKILL.md (524 more words)Show less

Signal tracks and annotation

bash
# Standard experiment: RPKM/CPM is fine. SPIKE-IN experiment: this would ERASE the global shift.
bamCoverage -b aligned/IP_rep1.final.bam -o bigwig/IP_rep1.bw --normalizeUsing RPKM -p 8
# Spike-in (ChIP-Rx): bamCoverage --scaleFactor <spike-in factor> --normalizeUsing None  (chip-seq/spike-in-normalization)

Annotation uses a project GTF via makeTxDbFromGFF() when provided, else a pre-built TxDb. overlap='all' couples gene assignment with feature overlap (host-gene convention); default overlap='TSS' assigns the nearest-TSS gene independently. Full code: examples/peak_annotation.R.

QC checkpoints between steps

AfterGateInterpretation
QC/trimQ30 >85%, adapter <5%DNA higher quality than RNA
AlignmentMapping >80%, unique >70%Low unique = repeats/contamination/wrong build
PRE-dedupNRF >0.8, PBC1 >0.8Low complexity = over-amplification/low input; MUST be computed before dedup
PeaksFRiP >1% (TF) / >5% (sharp histone; broad marks run lower); NSC >1.05; RSC >0.8; fingerprint separates IP/inputLow FRiP/flat fingerprint = weak antibody or failed enrichment (chip-seq/chipseq-qc)
IDRrescue ratio and self-consistency ratio both <=2Poor replicate consistency; run IDR on PER-replicate peaks

Common Errors

SymptomCauseFix
Reproducible peaks over satellite/rDNA/high-signal regionsENCODE blacklist never subtractedbedtools intersect -v the blacklist BED before calling (committed step)
NRF/PBC ~1.0 and uninformativeComputed after markdup -rCompute complexity on the PRE-dedup, filtered BAM
Peaks at open chromatin / CN-amplified lociCalled without a matched controlPair each IP with its input/IgG in callpeak -c
H3K27me3/H3K9me3 fragmented into many tiny peaksBroad mark called with narrow settingsAdd --broad --broad-cutoff 0.1
--shift/--extsize had no effectUsed with -f BAMPE (ignored for PE)Use -f BAM + --nomodel for SE; BAMPE derives fragments
Spike-in global shift disappears in tracksbamCoverage RPKM/CPM re-equalized depth--scaleFactor + --normalizeUsing None (chip-seq/spike-in-normalization)
"IDR" numbers look too goodIDR run on a pooled peaksetRun IDR on per-replicate peaks + pooled pseudo-replicates

Pipeline map (hand-offs)

  • read-qc/fastp-workflow - adapter/quality trimming
  • read-alignment/bowtie2-alignment - the standard ChIP-seq aligner, build/index
  • alignment-files/duplicate-handling - collate/fixmate/sort/markdup order
  • chip-seq/chipseq-qc - NRF/PBC, FRiP, NSC/RSC, fingerprint, hyper-ChIPable detection
  • chip-seq/peak-calling - MACS3/SEACR/Genrich/HOMER, IDR vs naive overlap
  • chip-seq/peak-annotation - ChIPseeker/HOMER/GREAT
  • chip-seq/differential-binding - DiffBind/csaw and the normalization-problem framing
  • chip-seq/chipseq-visualization - deepTools tracks and normalization choices
  • chip-seq/spike-in-normalization - ChIP-Rx global-shift experiments
  • chip-seq/motif-analysis - HOMER/MEME-ChIP/monaLisa

The complete runnable scripts are in this skill's examples/ (narrow_peak_workflow.sh, peak_annotation.R).

  • database-access/sra-data - Pull ChIP-seq FASTQ from SRA / ENA for re-analysis
  • database-access/geo-data - Resolve ENCODE / Roadmap GSE accessions to SRA
  • read-qc/fastp-workflow - Upstream adapter trimming and quality filtering
  • read-alignment/bowtie2-alignment - Standard ChIP-seq aligner
  • alignment-files/duplicate-handling - MarkDuplicates pre-peak-calling
  • chip-seq/chipseq-qc - FRiP, NSC/RSC, library complexity, antibody validation
  • chip-seq/peak-calling - MACS3/MACS2/HOMER/SPP, IDR vs naive overlap, per-tool failure modes
  • chip-seq/peak-annotation - ChIPseeker, HOMER, ENCODE cCRE classification, GREAT regulatory domains
  • chip-seq/differential-binding - DiffBind, DESeq2, csaw with the three-normalization-problems framing
  • chip-seq/chipseq-visualization - deepTools, pyGenomeTracks, heatmaps with bigWig normalization choices
  • chip-seq/motif-analysis - HOMER, MEME-ChIP (STREME), monaLisa with background-selection theory
  • chip-seq/super-enhancers - ROSE/ROSE2/LILY for SE calling (H3K27ac vs MED1 vs BRD4)
  • chip-seq/cut-and-run-tag - SEACR + MACS2 consensus for CUT&RUN/CUT&Tag (different protocol)
  • chip-seq/spike-in-normalization - ChIP-Rx Drosophila spike-in for global-shift experiments
  • chip-seq/chromatin-state-segmentation - ChromHMM multi-mark integration into chromatin states
  • chip-seq/chip-deep-learning - BPNet/chromBPNet/Enformer for variant-effect prediction
  • chip-seq/allele-specific-binding - WASP/BaalChIP/RASQUAL for allele-specific TF binding

References

  • Zhang Y, Liu T, Meyer CA, et al (2008) Model-based analysis of ChIP-Seq (MACS). Genome Biology 9:R137. DOI 10.1186/gb-2008-9-9-r137.
  • Landt SG, Marinov GK, Kundaje A, et al (2012) ChIP-seq guidelines and practices of the ENCODE and modENCODE consortia. Genome Research 22:1813-1831. DOI 10.1101/gr.136184.111. (NSC/RSC, FRiP, IDR practice.)
  • Li Q, Brown JB, Huang H, Bickel PJ (2011) Measuring reproducibility of high-throughput experiments. Annals of Applied Statistics 5:1752-1779. DOI 10.1214/11-AOAS466. (the IDR framework.)
  • Amemiya HM, Kundaje A, Boyle AP (2019) The ENCODE blacklist: identification of problematic regions of the genome. Scientific Reports 9:9354. DOI 10.1038/s41598-019-45839-z.

© 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 3 other files in workflows/chipseq-pipeline of GPTomics/bioSkills.

  • SKILL.md
  • examples/narrow_peak_workflow.sh
  • examples/peak_annotation.R
  • usage-guide.md

Open the folder on GitHubat commit d91ed3d

Used in 1 other repository

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

Compare with similar skills

Bio Workflows Chipseq Pipeline 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 Workflows Chipseq Pipeline compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bio Workflows Chipseq Pipeline this skillGPTomics/bioSkills1.2k1 repos~4kAutomated safety check: PassMIT
LaminDB Biological Data Managementdavila7/claude-code-templates32k12 repos~3.6kAutomated safety check: PassMIT
AI Scientist EvaluatorBioTender-max/awesome-bio-agent-skills199—~2.4kAutomated safety check: PassCustom licence
Latchbio Integrationdavila7/claude-code-templates32k11 repos~2.4kAutomated safety check: PassMIT
Remote Compute Sshaipoch/open-science5.5k—~5.7kAutomated safety check: PassApache-2.0
Bio OrchestratorClawBio/ClawBio1.2k3 repos~2.5kAutomated safety check: PassMIT

Similar skills

  • LaminDB Biological Data Management

    davila7/claude-code-templates

    Manages biological datasets with LaminDB: versioned artifacts, run lineage, ontology-based annotation, schema validation and links to workflow managers and ML tools.

    32k GitHub starsUsed in 12 repos~3.6k tokens
    Research & ScienceAuto-check passed
  • AI Scientist Evaluator

    BioTender-max/awesome-bio-agent-skills

    Critically review, score, compare, and rank one or more AI scientist outputs for biology, bioinformatics, computational life science, or adjacent research tasks.

    199 GitHub stars~2.4k tokensUpdated 3 mo ago
    Research & ScienceAuto-check passed
  • Latchbio Integration

    davila7/claude-code-templates

    Latch platform for bioinformatics workflows. An agent skill from davila7/claude-code-templates.

    32k GitHub starsUsed in 11 repos~2.4k tokens
    Research & ScienceAuto-check passed
  • Remote Compute Ssh

    aipoch/open-science

    Evaluate and use SSH Remote Compute before choosing where to run GPU, high-memory, parallel, batch, model-inference, bioinformatics, or other long-running scientific work; supports short remote…

    5.5k GitHub stars~5.7k tokensUpdated today
    Research & ScienceAuto-check passed
  • Bio Orchestrator

    ClawBio/ClawBio

    Meta-agent that routes bioinformatics requests to specialised sub-skills.

    1.2k GitHub starsUsed in 3 repos~2.5k tokens
    Research & ScienceAuto-check passed
  • Latchbio Integration

    K-Dense-AI/scientific-agent-skills

    Builds, registers, debugs, and operates bioinformatics workflows on Latch using the Python SDK, CLI, Latch Data and Registry, Nextflow, Snakemake, programmatic execution, and Latch MCP.

    48k GitHub starsUsed in 1 repo~2.5k tokens
    Research & ScienceAuto-check: notes

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 Workflows Chipseq Pipeline

What does Bio Workflows Chipseq Pipeline do?

Orchestrates the end-to-end ChIP-seq pipeline from FASTQ to blacklist-filtered, annotated peaks, chaining fastp QC, Bowtie2 alignment, pre-dedup library-complexity QC (NRF/PBC), duplicate removal…. Bio Workflows Chipseq Pipeline is an agent skill from GPTomics/bioSkills. Orchestrates the end-to-end ChIP-seq pipeline from FASTQ to blacklist-filtered, annotated peaks, chaining fastp QC, Bowtie2 alignment, pre-dedup library-complexity QC (NRF/PBC), duplicate removal, chrM + ENCODE-blacklist filtering, MACS3 peak calling against a matched input, IDR/consensus reproducibility, deepTools signal tracks, and ChIPseeker annotation.

When should I use Bio Workflows Chipseq Pipeline?

Bio Workflows Chipseq Pipeline fits situations like: committing the reference build + blacklist version + effective genome size once; pairing each IP with its matched control; computing complexity metrics BEFORE dedup; choosing narrow vs broad and MACS3 vs SEACR/Genrich.

How do I install Bio Workflows Chipseq Pipeline in Claude Code?

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

How do I install Bio Workflows Chipseq Pipeline in Codex?

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

Can I use Bio Workflows Chipseq Pipeline 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-workflows-chipseq-pipeline -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-workflows-chipseq-pipeline, .gemini/skills/bio-workflows-chipseq-pipeline, .github/skills/bio-workflows-chipseq-pipeline and .opencode/skills/bio-workflows-chipseq-pipeline in your project.

What does Bio Workflows Chipseq Pipeline need to run?

Going by SKILL.md and its folder, Bio Workflows Chipseq Pipeline needs a shell and R for the scripts in its folder. Our summary lists: A Bash shell.

Does Bio Workflows Chipseq Pipeline 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 Workflows Chipseq Pipeline 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 Workflows Chipseq Pipeline use?

Bio Workflows Chipseq Pipeline 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 Workflows Chipseq Pipeline 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 Workflows Chipseq Pipeline?

Skills that share tags, products or a category with Bio Workflows Chipseq Pipeline: LaminDB Biological Data Management (davila7/claude-code-templates, 32k stars), AI Scientist Evaluator (BioTender-max/awesome-bio-agent-skills, 199 stars), Latchbio Integration (davila7/claude-code-templates, 32k stars) and Remote Compute Ssh (aipoch/open-science, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bio Workflows Chipseq Pipeline?

GPTomics (a GitHub organization) maintains it in GPTomics/bioSkills, which has 1,217 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.