Agent skill · Data & Analytics

bio-copy-number-cnvkit-analysis

Detect copy number variants from targeted/exome sequencing using CNVkit. Supports tumor-normal pairs, tumor-only, and germline CNV calling. Use when detecting CNVs from WES or targeted panel sequencing data.

FreedomIntelligencegithub.com/FreedomIntelligenceGitHub ↗
claude-codeships scripts
Install
npx skills add FreedomIntelligence/OpenClaw-Medical-Skills --skill bio-copy-number-cnvkit-analysis --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: yes
Path: skills/bio-copy-number-cnvkit-analysis/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: GATK 4.5+, bedtools 2.31+ Before using code patterns, verify installed versions match. If versions differ: - Python: `pip show <package>` then `help(module.function)` to check signatures - 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. # CNVkit CNV Analysis **"Detect copy number variants from my exome data"** → Run a read-depth-based pipeline that normalizes on/off-target coverage against a reference, segments the log2 ratio profile, and calls gains/losses. - CLI: `cnvkit.py batch tumor.bam --normal normal.bam` ## Basic Workflow **Goal:** Run the complete CNVkit pipeline on a tumor-normal pair to detect copy number variants. **Approach:** Execute the batch command which wraps target/antitarget generation, coverage calculation, reference building, and segmentation into one step. ```bash # Complete pipeline for tumor-normal pair cnvkit.py batch tumor.bam \ --normal normal.bam \ --targets targets.bed \ --fasta reference.fa \ --output-reference my_reference.c

What's inside
Steps it walks through
  1. Version Compatibility
  2. Basic Workflow
  3. Build Reference from Normal Samples
  4. Flat Reference (No Matched Normal)
  5. WGS Mode
  6. bedGraph Input (Privacy-Preserving)
  7. Step-by-Step Pipeline
  8. Segmentation Options
  9. CNV Calling with Ploidy/Purity
  10. Export Results
  11. Visualization
  12. Key Output Files
  13. Python API
  14. Quality Control
Ships with 2 files
  • examples/run_cnvkit.sh
  • usage-guide.md
Commands it runs
Complete pipeline for tumor-normal pair
cnvkit.py batch tumor.bam \
Step 1: Build reference from multiple normals (recommended)
cnvkit.py batch \
Step 2: Run on tumor samples using pre-built reference
cnvkit.py batch tumor1.bam tumor2.bam \
When no matched normal is available
For whole genome sequencing (no targets file)
Generate bedGraph: bedtools genomecov -ibam sample.bam -bg | bgzip > sample.bed.gz && tabix -p bed sample.bed.gz
cnvkit.py coverage sample.bed.gz targets.target.bed -o sample.targetcoverage.cnn
More from OpenClaw-Medical-Skills
All skills →
About this skill
What does the bio-copy-number-cnvkit-analysis skill do?

Detect copy number variants from targeted/exome sequencing using CNVkit. Supports tumor-normal pairs, tumor-only, and germline CNV calling. Use when detecting CNVs from WES or targeted panel sequencing data.

How do I install it?

Run `npx skills add FreedomIntelligence/OpenClaw-Medical-Skills --skill bio-copy-number-cnvkit-analysis --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