LLMs-Universal-Life-Science-and-Clinical-Skills- genomics-variant-annotation
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-variant-annotation" ~/.claude/skills/mdbabumiamssm-llms-universal-life-science-and-clinical-skills-genomics-variant-a && rm -rf "$T"
manifest:
Skills/Genomics/genomics-variant-annotation/SKILL.mdsource content
📝 Variant Annotation
Variant annotation and functional effect prediction. Supports VEP, snpEff, and ANNOVAR.
CLI Reference
python omicsclaw.py run genomics-variant-annotation --demo python omicsclaw.py run genomics-variant-annotation --input <data.vcf> --output <dir>
Why This Exists
- Without it: Variants lack biological context, remaining as simple coordinate tuples
- With it: Transforms structural variation into biological impact and transcript-level consequences
- Why OmicsClaw: Unified framework for multiple ontology backends like VEP or ANNOVAR without custom parsing
Workflow
- Calculate: Prepare genome indices and transcript boundary maps.
- Execute: Run annotation search across known consequence states.
- Assess: Filter variants by putative pathological score.
- Generate: Save annotated VCFs with strict ontologies.
- Report: Tabulate key functionally relevant variants.
Example Queries
- "Annotate this vcf file using VEP"
- "Run snpEff and summarize high impact variants"
Output Structure
output_directory/ ├── report.md ├── result.json ├── annotated.vcf.gz ├── figures/ │ └── impact_distribution.png ├── tables/ │ └── top_variants.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 raw variationvariant-call
— Upstream filtering stepsvcf-ops