variant-calling
Skill62 starsChanged 5 months agoMIT-0View on GitHub
Germline and somatic short-variant calling pipeline for Illumina short-read data. Use when the user mentions BWA, BWA-MEM2, GATK, HaplotypeCaller, Mutect2, VCF, GVCF, VQSR, variant calling, germline, somatic, SNV, or indel calling from FASTQ/BAM.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kreid415/claude-science-skillstheir own version, first seen Oct 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kreid415/claude-science-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- aws-genai-ml-architectSkill
- bioinformatics-on-healthomicsSkill
- biomarker-discoverySkill
- cdisc-complianceSkill
- cell-type-annotationSkill
- cheminformaticsSkill
- claims-analyticsSkill
- claims-billing-rulesSkill
- clinical-data-standardsSkill
- coordination-of-benefitsSkill
- dicom-processingSkill
- digital-pathologySkill
- drug-repurposingSkill
- edc-data-validationSkill
- ehr-data-parsingSkill
- genomic-variant-interpretationSkill
- hedis-measure-specificationSkill
- imaging-study-designSkill
- medical-device-software-complianceSkill
- ml-researcherSkill
- molecular-dockingSkill
- multi-omics-integrationSkill
- multi-omics-pipelineSkill
- ngs-quality-controlSkill
- pa-clinical-policySkill
- pa-decision-automationSkill
- pharmacoepidemiologySkill
- protein-structure-analysisSkill
- provider-denial-workupSkill
- quality-measuresSkill
- quantitative-proteomicsSkill
- radiology-preprocessingSkill
- risk-adjustmentSkill
- risk-adjustment-strategySkill
- risk-stratification-indicesSkill
- rna-seq-analysisSkill
- rwd-cohort-analysisSkill
- scrna-seq-pipelineSkill
- structure-based-drug-designSkill
- trajectory-analysisSkill
- translational-researchSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 80
Right: Always specify at alignment: -R '@RG\tID:x\tSM:x\tPL:ILLUMINA\tLB:x'
- Distinctive: line 84
Right: Always produce GVCFs when joint genotyping will be performed
- Very specific: line 88
Right: Use FS > 200 for indels, FS > 60 for SNPs
- Distinctive: line 92
Right: Use hard filters for small cohorts
- Very specific: line 96
Right: Use genome-wide known-sites.
- Distinctive: line 104
Right: Ensure ref.dict, ref.fa.fai, BWA index, and all VCFs match the same build
- Very specific: line 108
Right: Always provide --panel-of-normals for tumor-only calling
- Distinctive: line 116
Keep code comments minimal and functional (what, not why-it-exists)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Variant Calling (GATK4) — Pipeline Skill (Thin Scaffold)
Overview
Adds decision logic for VQSR vs hard filters, WES vs WGS parameter differences, and GATK4-specific gotchas that LLMs frequently get wrong (filter thresholds, GVCF requirements, reference consistency).
Usage
- Activate when choosing between VQSR and hard filters for a given cohort size
- Activate when setting up WES vs WGS pipeline parameters
- Activate when running Mutect2 tumor/normal or tumor-only somatic calling
Core Concepts
Decision Logic
Germline calling strategy:
├── Single sample, no future joint calling → HaplotypeCaller direct VCF
└── Cohort (≥2 samples) → HaplotypeCaller -ERC GVCF → GenomicsDBImport → GenotypeGVCFs
Filtering strategy:
├── ≥30 WGS samples OR ≥30 WES exomes → VQSR
└── <30 samples OR single sample → Hard filters
Somatic calling:
├── Tumor + matched normal → Mutect2 with both BAMs
└── Tumor-only → Mutect2 + PoN (MANDATORY) + gnomAD germline resourceWES vs WGS parameter differences:
| Step | WGS | WES |
| BQSR / HaplotypeCaller | No -L | -L capture.bed -ip 100 |
| Known sites for BQSR | Genome-wide | Genome-wide (do NOT subset) |
| Filtering | VQSR (≥30 samples) | Hard filters unless ≥30 exomes |
| Joint genotyping intervals | Per-chromosome | -L capture.bed |
Critical Parameters
Hard filter thresholds (GATK Best Practices):
| Filter | SNP threshold | Indel threshold |
| QD | < 2.0 | < 2.0 |
| FS | > 60.0 | > 200.0 |
| MQ | < 40.0 | — |
| MQRankSum | < -12.5 | — |
| ReadPosRankSum | < -8.0 | < -20.0 |
| SOR | > 3.0 | > 10.0 |
VQSR truth sensitivity levels:
- SNPs: 99.7
- Indels: 99.0
- Indel
--max-gaussians 4(fewer training variants than SNPs)
VQSR annotations: -an QD -an FS -an MQ -an MQRankSum -an ReadPosRankSum -an SOR
Mutect2 essentials:
--germline-resource af-only-gnomad.hg38.vcf.gz--panel-of-normals pon.vcf.gz(essential for tumor-only)--f1r2-tar-gz→LearnReadOrientationModel(FFPE/OxoG artifacts)GetPileupSummaries+CalculateContaminationbeforeFilterMutectCalls
Common Mistakes
- Wrong: Aligning without proper
@RGheaders (missing ID, SM, PL, LB) Right: Always specify at alignment:-R '@RG\tID:x\tSM:x\tPL:ILLUMINA\tLB:x'Why: GATK refuses to run or silently merges samples when SM tags are wrong - Wrong: Running HaplotypeCaller without
-ERC GVCFfor cohort analysis Right: Always produce GVCFs when joint genotyping will be performed Why: Regular VCFs cannot be joint-genotyped; must re-call from BAM - Wrong: Reusing SNP hard-filter thresholds for indels (e.g.,
FS > 60for indels) Right: UseFS > 200for indels,FS > 60for SNPs Why: Indels tolerate higher strand bias; SNP thresholds over-filter real indels - Wrong: Applying VQSR to <30 samples Right: Use hard filters for small cohorts Why: VQSR needs many variants to train its Gaussian mixture model
- Wrong: Subsetting
--known-sitesVCFs to WES capture BED for BQSR Right: Use genome-wide known-sites; only restrict analysis intervals via-LWhy: BQSR needs genome-wide known sites to model base quality errors - Wrong: Skipping
samtools indexbetween GATK steps Right: Index after every BAM-producing step Why: GATK requires BAM indices; missing them causes immediate failure - Wrong: Mixing reference files from different genome builds Right: Ensure ref.dict, ref.fa.fai, BWA index, and all VCFs match the same build Why: Mismatched dictionaries cause silent failures or cryptic errors
- Wrong: Running Mutect2 tumor-only without a panel of normals
Right: Always provide
--panel-of-normalsfor tumor-only calling Why: Without PoN, recurrent sequencing artifacts are called as somatic mutations
Response Format
- Lead with the command or code the user needs — explain after
- Structure as: confirm inputs → working code → key parameters explained → gotchas
- One complete working example per task; do not show every alternative
- Keep code comments minimal and functional (what, not why-it-exists)
- Target: 50-100 lines of code with brief surrounding explanation
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

