LLMs-Universal-Life-Science-and-Clinical-Skills- genomics-phasing
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-phasing" ~/.claude/skills/mdbabumiamssm-llms-universal-life-science-and-clinical-skills-genomics-phasing && rm -rf "$T"
manifest:
Skills/Genomics/genomics-phasing/SKILL.mdsource content
🔀 Haplotype Phasing
Haplotype phasing for variant data. Wraps WhatsHap, SHAPEIT, and Eagle.
CLI Reference
python omicsclaw.py run genomics-phasing --demo python omicsclaw.py run genomics-phasing --input <data.vcf> --output <dir>
Why This Exists
- Without it: Variants remain independent loci without knowledge of allelic connectivity
- With it: Haplotypes are formed spanning genes, essential for compound heterozygote analysis
- Why OmicsClaw: Standardizes input and output across read-backed and population-backed phasing tools
Workflow
- Calculate: Prepare VCF indices and sequence mappings.
- Execute: Run haplotype graph resolution algorithms.
- Assess: Perform switch error evaluation and quality flagging.
- Generate: Output structured phased VCF representation.
- Report: Synthesize N50 phase block stats into tables.
Example Queries
- "Phase this vcf file using WhatsHap"
- "Use SHAPEIT for population phasing of variants"
Output Structure
output_directory/ ├── report.md ├── result.json ├── phased.vcf.gz ├── figures/ │ └── phase_block_distribution.png ├── tables/ │ └── phasing_metrics.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 generation of raw VCFsvariant-call
— Downstream annotation of phased haplotypesannotation