LLMs-Universal-Life-Science-and-Clinical-Skills- genomics-vcf-operations
install
source · Clone the upstream repo
git clone https://github.com/mdbabumiamssm/LLMs-Universal-Life-Science-and-Clinical-Skills-
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/mdbabumiamssm/LLMs-Universal-Life-Science-and-Clinical-Skills- "$T" && mkdir -p ~/.claude/skills && cp -r "$T/Skills/Genomics/genomics-vcf-operations" ~/.claude/skills/mdbabumiamssm-llms-universal-life-science-and-clinical-skills-genomics-vcf-opera && rm -rf "$T"
manifest:
Skills/Genomics/genomics-vcf-operations/SKILL.mdsource content
📋 VCF Operations
VCF manipulation, filtering, merging, and summary statistics. Wraps bcftools and GATK SelectVariants.
CLI Reference
python omicsclaw.py run genomics-vcf-operations --demo python omicsclaw.py run genomics-vcf-operations --input <data.vcf> --output <dir>
Why This Exists
- Without it: Massive cohort VCF files are intractable to manipulate or filter manually
- With it: Fast algebraic operations stream variants safely and precisely
- Why OmicsClaw: Translates complex bcftools syntax into plain intuitive language prompts
Workflow
- Calculate: Map sequence ranges or filter criteria strings.
- Execute: Perform stream-based querying over compressed index.
- Assess: Ensure output satisfies the boundary limits dynamically.
- Generate: Output sub-sampled VCF representations.
- Report: Tabulate variant extraction statistics.
Example Queries
- "Filter this vcf file keeping only PASS variants"
- "Merge these sample vcfs using bcftools"
Output Structure
output_directory/ ├── report.md ├── result.json ├── processed.vcf.gz ├── figures/ │ └── filter_stats.png ├── tables/ │ └── cohort_summary.csv └── reproducibility/ ├── commands.sh ├── environment.yml └── checksums.sha256
Safety
- Local-first: Strict offline processing without external upload.
- Disclaimer: Requires OmicsClaw reporting structures and disclaimers.
- Audit trail: Hyperparameters and operational flow states are logged fully.
Integration with Orchestrator
Trigger conditions:
- Automatically invoked dynamically based on tool metadata and user intent matching.
Chaining partners:
— Upstream VCF sourcevariant-call
— Downstream downstream impact modelingannotation