alphagenome-single-variant-analysis

Analyzes genetic variant effects on gene expression, splicing, and chromatin using the AlphaGenome API.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/xlinh2301/EditCTC --skill alphagenome-single-variant-analysis-xlinh2301
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: alphagenome-single-variant-analysis
Source: https://github.com/xlinh2301/EditCTC/tree/main/.agents/skills/alphagenome-single-variant-analysis
Command: npx skills add https://github.com/xlinh2301/EditCTC --skill alphagenome-single-variant-analysis-xlinh2301

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires alphagenome, absl-py, python-dotenv, matplotlib, numpy, pandas, pyarrow, scipy, seaborn, and includes scripts (resource) and references (resource) components.

What problem does it solve? Determining whether a non-coding genetic variant affects gene regulation, splicing, or chromatin accessibility normally requires wet-lab experiments; this Skill predicts those molecular effects in silico using the AlphaGenome API and produces a structured, evidence-grounded analysis report. ## Core Features & Use Cases - Variant Effect Scoring: Runs broad discovery scans across differential scorers (RNA_SEQ, DNASE, CHIP_TF, SPLICE_JUNCTIONS, and more) to find significant tissue-specific effects of a variant in chr:pos:ref>alt format. - Mechanism Analysis: Generates REF/ALT comparison plots, ISM SeqLogo motif analysis, and quantitative splicing junction analysis to explain why a regulatory or splice site was disrupted. - Ontology & Gene Resolution: Maps biological terms to UBERON/CL/EFO ontology IDs and looks up genes and transcripts from local GENCODE GTF data without external APIs. - Use Case: A clinician asks whether variant chr21:46126238:G>C in COL6A2 is pathogenic; the Skill scores the variant across tissues, visualizes splicing changes in the relevant cell type, interprets the results against an interpretation guide, and writes a report.md with embedded plots. ## Quick Start Ask the assistant to analyze the functional effect of variant chr17:7675148:G>A on gene expression and splicing using the AlphaGenome variant analysis skill.

Frequently Asked Questions about alphagenome-single-variant-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a genetic variant's effect with AlphaGenome?▼

Provide the variant in chr:pos:ref>alt format and the relevant tissue or disease context. The skill scores the variant with dna_model.score_variant across recommended differential scorers, filters significant hits by quantile score, then visualizes REF/ALT track differences and writes a report.

What API key do I need for AlphaGenome variant analysis?▼

You need an ALPHAGENOME_API_KEY, which you can register for at the DeepMind AlphaGenome page. Store it in a .env file in your home directory; scripts load it automatically via dotenv before creating the dna_client.

Can AlphaGenome predict splicing disruption from a variant?▼

Yes, it supports SPLICE_SITES, SPLICE_SITE_USAGE, and SPLICE_JUNCTIONS output types. The interpret_splicing.py script quantifies junction-level changes to detect exon skipping or cryptic splice sites, while analyze_ism.py identifies disrupted motifs.

What are the limitations of AlphaGenome variant effect prediction?▼

AlphaGenome does not model protein-coding effects like missense or frameshift consequences, miRNA processing, RNA secondary structure, or developmental and stimulus-specific contexts. High quantile scores with low raw scores in low-expression genes are statistical artifacts indicating no real effect.

Why does score_variant fail when I pass ontology_terms?▼

score_variant does not accept an ontology_terms argument; you must filter the returned AnnData objects manually by inspecting adata.var columns such as ontology_curie. In contrast, predict_variant does accept ontology_terms directly.

How do I map a tissue name like liver to an ontology ID?▼

Run resolve_ontology_terms.py with your query term to search the local tissue_ontology_mapping.json file. It returns ranked UBERON, CL, or EFO candidates with fuzzy matching, and you select the most specific match for your disease context.