alphagenome-atlas-website-links

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

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

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, strand rules, and track catalog names. This Skill automates correct URL synthesis for variants, loci, candidate tables, and Ref vs. Alt 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, automatically enforcing the Assay-group rule so RNA-seq and DNase tracks stay visible. - Candidate Summary Tables: Format ranked variant records into Markdown tables with embedded clickable Atlas links. - Track Predictions (Ref vs. Alt): Generate /atlas/track-predictions URLs that resolve GENCODE v46 splice junctions, query the Atlas track catalog, and co-plot RNA-seq with splicing tracks. - Use Case: Given a splice variant like chr15:42387805:C>G in CAPN3, produce a bounded track-predictions link comparing reference and alternate allele predictions across splice junctions, RNA-seq, DNase, and ChIP-TF in Muscle_Skeletal. ## 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 alphagenome_atlas_links.py variant subcommand with a 1-based chr:pos:ref>alt string, optionally adding --biosample and --modalities flags. It outputs a validated URL with correct filter and layout parameters.

How to compare reference vs alternate allele predictions in AlphaGenome Atlas?▼

Use the track-predictions subcommand with --variant, --gene or --interval, --biosample, and --modalities. The script resolves splice junctions from GENCODE v46, queries the Atlas track catalog, and builds a bounded comparison 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 do RNA-seq and DNase tracks disappear when filtering by transcription factor?▼

RNA-seq and DNase tracks have no transcription factor code, so a filter containing only ASSAY_TRANSCRIPTOR_FACTOR hides them under the Assay group's OR logic. Explicitly add SCORER_MODALITY:RNA-seq and SCORER_MODALITY:DNase to the filter string.

Does generating track prediction links require an API key?▼

Yes, the track-predictions subcommand needs an ALPHAGENOME_API_KEY set in ~/.env to query the Atlas scorer metadata catalog. Simple variant and locus link generation works without authentication.