alphagenome-atlas-website-links

Generates deep-links and Ref vs. Alt track prediction URLs for the AlphaGenome Atlas website.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/arslan9024/White-Caves --skill alphagenome-atlas-website-links-arslan9024
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: alphagenome-atlas-website-links
Source: https://github.com/arslan9024/White-Caves/tree/main/.agents/skills/alphagenome_atlas_website_links
Command: npx skills add https://github.com/arslan9024/White-Caves --skill alphagenome-atlas-website-links-arslan9024

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires alphagenome, numpy, pandas, pyarrow, python-dotenv, and includes scripts (resource) components.

What problem does it solve? Manually constructing AlphaGenome Atlas URLs is error-prone: variant formats must be 1-based chr:pos:ref>alt, filter groups follow non-obvious AND/OR logic, and track-prediction ScoreId tokens require exact splice junction coordinates and strand rules. This Skill automates correct URL generation for variants, loci, candidate tables, and Ref vs. Alt prediction comparisons. ## Core Features & Use Cases - Variant & Locus Deep-Links: Build single-variant exploration links and genomic interval views with biosample, modality, and transcription factor filters. - Candidate Variant Tables: Format ranked variant records into Markdown tables with embedded clickable Atlas links. - Track Predictions: Generate /atlas/track-predictions URLs comparing Reference vs. Alternate allele predictions, with automatic GENCODE v46 splice junction resolution and mandatory RNA-seq co-plotting. - Use Case: Given a splicing variant like chr15:42387805:C>G in CAPN3, produce a bounded track-predictions link showing splice junctions, RNA-seq, DNase, and ChIP-TF tracks in Muscle_Skeletal tissue. ## Quick Start Ask the assistant to generate an AlphaGenome Atlas deep-link for the variant chr9:128225994:G>A in K562 cells with RNA-seq, DNase, and ChIP-TF tracks.

Frequently Asked Questions about alphagenome-atlas-website-links

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

FAQPage Schema
How do I create an AlphaGenome Atlas link for a genetic variant?▼

Run the CLI with the variant subcommand, passing the variant in 1-based chr:pos:ref>alt format, for example chr9:128225994:G>A. Optionally add --biosample and --modalities flags to filter tracks by cell line and assay type.

How do I compare Reference vs Alternate allele predictions in AlphaGenome?▼

Use the track-predictions subcommand with --variant, --gene, and --biosample options. The script resolves splice junctions from GENCODE v46, looks up tracks from the Atlas catalog, and outputs a bounded /atlas/track-predictions URL.

What variant format does AlphaGenome Atlas accept?▼

Variants must use 1-based chr:pos:ref>alt format, such as chr7:27170000:A>G. Colon-separated alleles like A:G and dbSNP rsIDs are not supported by the Atlas query parameter.

Why are RNA-seq and DNase tracks missing from my Atlas link?▼

If the filter string contains only ASSAY_TRANSCRIPTOR_FACTOR filters, RNA-seq and DNase tracks fail the Assay group evaluation and are hidden. Explicitly include SCORER_MODALITY:RNA-seq and SCORER_MODALITY:DNase, which the script handles automatically.

Does the track-predictions command require an API key?▼

Yes, resolving track metadata requires an ALPHAGENOME_API_KEY set in ~/.env. The key authenticates the Atlas client used to query scorer metadata and track catalogs.

Why does my track-predictions page hang or load slowly?▼

Omitting the scores parameter or leaving the viewport interval unbounded causes the app to query all matching tracks across the locus. Always provide a bounded i= interval, which the script sets automatically to the target gene or requested interval.