plugins/ngs-analysis/skills/ngs-dna-variant-calling/SKILL.md
Dispatch WGS, WES, or targeted DNA variant requests to germline, somatic, or UMI-panel skills, then plan public nf-core/sarek, GATK4, DeepVariant, samtools, or bcftools workflows.
npx skillsauth add openai/plugins ngs-dna-variant-callingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill as the DNA variant-calling dispatcher for WGS, WES, or targeted DNA panel analysis from FASTQ, BAM, or CRAM. Once the sample model is clear, hand off to the narrow subtype skill.
Confirm:
Route by biological/sample model:
ngs-dna-germline-variantsngs-dna-somatic-variantsngs-dna-umi-panel-variantsIf the request is ambiguous, ask only for the missing sample model and assay design needed to choose among these three. Do not run one generic variant workflow when the request needs subtype-specific assumptions.
Prefer nf-core/sarek for an end-to-end public workflow. Use direct GATK4, DeepVariant, samtools, or bcftools commands only for smaller, focused tasks or when the user explicitly wants a custom pipeline.
python plugins/ngs-analysis/scripts/ngs_preflight.py --pipeline dna_variant_calling --emit-install-plan
For a compact BAM/CRAM-to-VCF run with a matching reference FASTA, use the plugin-owned samtools/bcftools runner:
python plugins/ngs-analysis/scripts/run_dna_variant_calling.py \
--sample-sheet dna_samples.tsv \
--reference-fasta reference.fa \
--region chr20:1-100000 \
--filter-min-qual 30 \
--filter-min-site-dp 10 \
--execute
The sample sheet should include sample and bam or cram columns. When --region is provided the runner also emits per-base depth plus a callable-loci summary for that interval, and when filter thresholds are provided it emits a soft-filtered VCF alongside the raw calls. This package is suitable for focused local checks and run-envelope generation; subtype skills still own germline, somatic, UMI, reference-resource, cohort, annotation, and workflow assumptions.
This compact runner now writes advisory resources/resource_plan.json, resource_manifest.tsv, resource_env.sh, and resource_readiness.md artifacts for the selected genome bundle. Use --require-resource-plan when missing registered reference resources should block readiness; otherwise the explicit --reference-fasta remains enough for focused local checks.
Preflight-first nf-core pattern:
nextflow run nf-core/sarek \
-profile test,docker \
--outdir results/sarek_test
Real run skeleton:
nextflow run nf-core/sarek \
-profile docker \
--input samplesheet.csv \
--outdir results/sarek \
--genome GRCh38 \
--tools haplotypecaller,vep
For WES/panel data, include the target BED. For tumor-normal data, verify pair metadata before execution. For UMI panels, preserve barcode handling and molecule-level QC.
development
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
data-ai
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
tools
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
development
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.