Generated banner for Alphagenome Single Variant Analysis
Generated logo for Alphagenome Single Variant Analysis

Alphagenome Single Variant Analysis

Google DeepMindOfficialPublished by Google DeepMind

  • Skill
  • Tool integration
  • Science and research
  • Apache-2.0
  • Low risk
  • Has scripts

From the author

Analyzes genetic variant effects on gene expression (RNA-seq), chromatin accessibility (DNASE), histone marks (ChIP), and transcription factors using the AlphaGenome API. Use when the user asks about non-coding variant effects, pathogenicity, clinical significance, disease associations, functional effects, gene expression changes, splicing disruption, or regulatory effects in promoters and enhancers. Also use for resolving biological terms to tissue/cell-type ontologies (UBERON/CL) or analyzing variants in chr:pos:ref>alt format.
— the description by Google DeepMind

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The AlphaGenome Single Variant Analysis skill provides a structured workflow for investigating how specific genetic variants influence biological processes. It leverages the AlphaGenome API to predict effects on RNA-seq expression, chromatin accessibility, histone marks, and transcription factor binding. The skill includes robust procedures for resolving biological ontologies, performing discovery scans for tissue-specific effects, and visualizing variant impacts through detailed genomic tracks and splicing analysis. It emphasizes rigorous interpretation through standardized reporting templates and mandatory adherence to provided interpretation guides.

What it does

  • Performs discovery scans to identify significant variant effects across diverse tissues and modalities.
  • Resolves biological terms and tissue/cell-type names to standard UBERON/CL ontologies.
  • Visualizes variant effects on gene expression, splicing, and regulatory regions.
  • Generates structured, evidence-based analysis reports following predefined templates.
  • Supports in-silico mutagenesis (ISM) and quantitative splicing analysis.
  • Provides tools for local gene and transcript lookup using GTF data.

When to use it

  • When investigating the functional consequences of non-coding genetic variants.
  • When assessing the pathogenicity or clinical significance of a variant in a specific disease context.
  • When analyzing how a variant disrupts regulatory elements like promoters and enhancers.
  • When exploring tissue-specific gene expression changes or splicing disruption caused by a variant.
  • When you need to map biological terms to standardized ontologies for downstream analysis.

Advantages

  • Provides a standardized, reproducible workflow for complex genomic variant interpretation.
  • Integrates multi-omic data types (RNA-seq, DNASE, ChIP) for comprehensive functional insights.
  • Includes specific strategies for handling complex events like splicing skipping and large genes.
  • Enforces rigorous reporting standards to ensure consistency and clarity in findings.
  • Utilizes local GTF data for efficient and offline-capable gene lookups.

Usage examples

“Analyze the functional impact of the variant chr2:1234:A>C in liver tissue.”
The agent will perform a discovery scan, filter for liver-related biosamples, generate visualization plots for the variant, and produce a structured report detailing the predicted regulatory and expression effects.
“What is the effect of chr1:5000:G>T on splicing in neurons?”
The agent will use the interpret_splicing script to quantify delta scores and junction changes, visualize the splicing event with appropriate flanking exons, and summarize the findings in a report.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/google-deepmind/alphagenome-single-variant-analysis/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip alphagenome-single-variant-analysis.zip -d .agents/skills

Documentation by Google DeepMind

Variant Analysis using AlphaGenome

Prerequisites

  1. uv: Read the uv skill and follow its Setup instructions to ensure uv is installed and on PATH.

  2. User Notification: If .licenses/alphagenome_single_variant_analysis_LICENSE.txt does not already exist in the workspace root directory then (1) prominently notify the user to check the terms at https://deepmind.google.com/science/alphagenome/, then (2) create the file recording the notification text and timestamp.

  3. .env file: Make sure the .env file exists in your home directory. Create one if it does not exist.

  4. ALPHAGENOME_API_KEY: This skill requires an API key to function.

    You can register for a key at https://deepmind.google.com/science/alphagenome/. You MUST use the safe credentials protocol in the credentials skill to check for and request this key if this skill looks relevant to the user's request.

  5. ALPHAGENOME_GTF_PATH (Optional): Accelerate gene/transcript lookup by pointing to a local copy of the GTF feather file instead of downloading from GCS:

    echo "ALPHAGENOME_GTF_PATH=/path/to/local/gencode.v46.annotation.gtf.gz.feather" >> ~/.env

Core Rules

  • NEVER run python3 or python3 -c directly. The system Python does not necessarily have pandas, numpy, and other key dependencies. ALWAYS use uv run to run ALL Python code — including scripts, ad-hoc analysis files, and one-liners. Do not attempt to pip install or create new venvs — uv manages an isolated environment automatically.

  • Offline Only: NEVER use external APIs (e.g., MyGene.info, Ensembl REST) for gene/transcript lookup. Use lookup_gene_info.py with the local GTF. If it fails, fix the environment/paths, do not switch to external APIs.

  • API Key is required: ALPHAGENOME_API_KEY must be set before running any script.

  • Notification: If this skill is used, ensure this is mentioned in the output.

  • Report Format: Always use the templates in docs/report-templates.md for generating analysis reports, and ensure to include the table of top hits from the discovery scan.

Environment Setup & Troubleshooting

Python Environment

All scripts must be executed using uv run, which manages an isolated virtual environment with the correct dependencies via uv.

uv run <script_name> [args...]

For ad-hoc scripts (e.g., inline analysis code saved to a temp file), pass the full path instead of a short name:

uv run --project $SKILL_DIR /tmp/my_analysis.py --arg1 val1

[!NOTE] The first invocation resolves and installs dependencies (~10s). Subsequent runs use the cached environment and start instantly. The cache lives in ~/.cache/uv/.

Common Issues
  • Column Names: tidy_scores and metadata often use gene_name (not gene_symbol) and output_type (not modality). Always inspect df.columns before filtering.

  • Large Genes: Genes > 500kb (e.g., USH2A) break the whole_gene view. Use --view detail or manual regional windows instead.

  • Sashimi Strand Error: plot_components.Sashimi does NOT accept a strand argument directly. Filter input tracks instead.

  • KeyError: 'ontology_curie': Not all tracks have ontology_curie. Check track.metadata.columns before filtering.

  • Python Path: If exec: "python": executable file not found occurs, ensure you are using uv run instead of bare python/python3.

  • NotImplementedError (pandas): "iLocation based boolean indexing on an integer type is not available". This occurs when using boolean masks with .iloc on integer-indexed DataFrames in newer pandas versions. Fix: Convert boolean masks to integer indices using np.flatnonzero(mask).

  • GTF Feather Case Sensitivity: The AlphaGenome GTF Feather file uses Capitalized column names (Feature, Start, End, Strand) unlike standard GTF files. Always check df.columns if getting KeyErrors.

  • score_variant ontology filtering: score_variant does NOT accept ontology_terms as an argument. You must filter the returned AnnData objects manually by inspecting adata.var columns. In contrast, predict_variant DOES accept ontology_terms directly.

  • Sashimi Zoom Logic: To ensure "skipping" arcs are visible, expand the zoom to include the flanking exons rather than relying on junction overlap alone.

  • Junction Scores: Raw Junction objects from prediction may be simple Intervals. Use junction_data.get_junctions_to_plot(predictions=..., name=...) to retrieve objects with the .k (abundance/score) attribute.

  • uv Not Found: If exec: uv: not found, follow the installation instructions in Prerequisites.

  • Registry Authentication Error (401): If uv fails with 401 Unauthorized for a private registry, set UV_INDEX_URL=https://pypi.org/simple before running the script.

References


Code Patterns

Broad Discovery Scan

Use score_variant across differential scorers only to discover unexpected tissue effects.

from alphagenome.models import dna_client
from alphagenome.models import variant_scorers
from alphagenome.data import genome
import os
import pandas as pd
import dotenv

# Load environment variables from ~/.env
dotenv.load_dotenv(os.path.expanduser('~/.env'))

# Setup API Key and Client
dna_model = dna_client.create(api_key=os.environ.get('ALPHAGENOME_API_KEY'),
                              address='dns:///gdmscience.googleapis.com:443')

# Define Variant (example)
variant_str = "chr2:1234:A>C"
chrom, pos_str, ref_alt = variant_str.split(':')
ref, alt = ref_alt.split('>')
pos = int(pos_str)

# Use supported sequence length (e.g., 2**20 for optimal performance)
SEQ_LENGTH = 2**20
interval = genome.Interval(chrom, pos - SEQ_LENGTH // 2, pos + SEQ_LENGTH // 2)
variant = genome.Variant(chrom, pos, ref, alt)

scorers = [
    variant_scorers.RECOMMENDED_VARIANT_SCORERS[m]
    for m in variant_scorers.RECOMMENDED_VARIANT_SCORERS
    if "ACTIVE" not in m and "CAGE" not in m and "PROCAP" not in m
]

print(f"Scoring variant {variant_str}...")
scores_list = dna_model.score_variant(interval=interval, variant=variant, variant_scorers=scorers)

# Process and Display Results
all_dfs = []
for score_adata in scores_list:
    df = variant_scorers.tidy_scores([score_adata], match_gene_strand=True)
    if df is not None:
        all_dfs.append(df)

if all_dfs:
    df = pd.concat(all_dfs)
    significant = df[df['quantile_score'].abs() > 0.995]
    ranked = significant.sort_values('raw_score', key=abs, ascending=False)
    print("Top Significant Hits:")
    print(ranked[['biosample_name', 'gene_name', 'output_type', 'quantile_score', 'raw_score']])
Extended Search for Disease-Relevant Tissues
# Define keywords based on disease context
disease_keywords = ["liver", "hepatocyte"]

# Filter for any match
mask = df['biosample_name'].str.contains('|'.join(disease_keywords), case=False, na=False)

relevant_hits = df[mask].sort_values('raw_score', key=abs, ascending=False)
print(f"\n--- Extended Analysis (Keywords: {disease_keywords}) ---")
print(relevant_hits.head(20)[['biosample_name', 'output_type', 'raw_score', 'quantile_score']])

Workflow Checklist

Variant Analysis Progress:
- [ ] Step 0: Review Golden Examples (MANDATORY)
- [ ] Step 1: Create Output Folder and Setup
- [ ] Step 2: Parse User Query & Research
- [ ] Step 3: Resolve Tissues & Modalities
- [ ] Step 4: Visualize & Save Plots
- [ ] Step 5: Analyze Predictions (view plots, no code). MANDATORY: Read [interpretation-guide.md](docs/interpretation-guide.md) before interpreting results.
- [ ] Step 6: Write Report, save it as `report.md` (MANDATORY)
- [ ] Step 7: Self-Critique (view `report.md` to verify links & claims)
- [ ] Step 8: Make artifact out of `report.md`

Multi-Variant Workflow

If multiple variants are specified, spawn sub-agents to run each variant analysis and then synthesize each report.md into a single report.

Script Reference
ScriptPurpose
lookup_gene_infoComprehensive gene and transcript lookup using
: : GTF data :
resolve_ontology_termsBiological terms → UBERON/CL/EFO IDs
visualize_variant_effectsREF/ALT visualization (expression, regulatory,
: : splicing) :
analyze_ismIn-Silico Mutagenesis SeqLogo generation
interpret_splicingQuantitative splicing analysis (delta scores,
: : junctions) :
visualize_genome_tracksGenomic track visualization for a region

Files

docs/interpretation-guide.md

Interpretation Guide

This guide covers biological interpretation, signal patterns, motif analysis, and the pre-report reasoning checklist. Read this before writing any report.


Signal Patterns Reference

Use this table to identify mechanisms from model outputs.

Expression & Regulatory

Some example mechanisms (non-exhaustive, use your reasoning ability):

MechanismLocationKey SignalsISM Check
**TF BindingPromoter/TSS orDNASE loss (narrowDisrupted TF
: Loss** : Enhancer : peak) + RNA-seq : motif (Strong :
: : : loss : REF) :
**TF BindingPromoter/TSS orDNASE gain (narrowCreated TF motif
: Site Creation** : Enhancer : peak) + RNA-seq : (Strong ALT) :
: : : gain : :
**EnhancerDistalDNASE lossDisrupted TF
: Disruption** : : (distal) + RNA-seq : motif (Strong :
: : : loss (linked : REF) :
: : : gene). : :
: : : H3K27ac/p300 loss : :
: : : confirms. : :
**EnhancerDistalDNASE gainCreated TF motif
: Creation** : : (distal) + RNA-seq : (Strong ALT) :
: : : gain (linked : :
: : : gene). : :
: : : H3K27ac/p300 gain : :
: : : confirms. : :
TSS Shift5' UTRRNA-seq shape—
: : : change (5' end) or : :
: : : CAGE peak shift : :
**uORF5' UTRContext-dependent:—
: Creation** : : may show weak : :
: : : Expression score. : :
: : : Verify ATG : :
: : : creation in 5' : :
: : : UTR. : :
**mRNA3' UTR (Note:RNA-seq loss—
: Stability** : Model does not : WITHOUT : :
: : explicitly model : chromatin/splicing : :
: : this, unlikely to : defects. Possible : :
: : reliably pick up) : miRNA binding site : :
: : : alteration. : :
**StatisticalAnyHigh QuantileEmpty/noise
: Artifact** : (low-expression : (>0.999) + Zero : :
: : genes) : Plot Difference. : :
: : : Caused by variance : :
: : : stabilization in : :
: : : low-signal : :
: : : regions. : :
Splicing
MechanismKey SignalsJunction Evidence
Exon SkippingLow Splice Site atJunction connects
: : junction + new junctions : flanking exons, bypassing :
: : spanning skipped exon : variant :
Intron RetentionLow Splice Site + high—
: : RNA-seq in intron : :
: : (read-through) : :
**Cryptic ExonNew Splice Site (highJunction starts/ends near
: (Pseudo-exon)** : score) + new junctions : variant :
: : flanking cryptic exon : :
Exon ExtensionNew donor/acceptor nearJunction shifted by N bp
: : existing site : from canonical :
PolyA Signal Loss3' UTR variant: highAATAAA motif in ISM
: : Splice Junctions : :
: : (read-through) + RNA-seq : :
: : loss : :
Splicing Interpretation Rules
  • Specific mechanisms only: Do NOT write "likely exon skipping or intron retention" if data allows you to distinguish. Use the junction coordinates.

  • Proxy signals: If Expression Loss (-0.999) >>> Splicing Disruption (0.99), the primary mechanism is likely transcriptional (promoter/enhancer loss), not splicing. Exception: clearly aberrant new splice junction.

  • Complex outcome: If multiple new cryptic sites compete with canonical site, describe as "complex outcome of new candidate sites."


Tissue and Location Verification

  • Verify Tissue Lineage: Both top hits and disease-relevant tissues are valuable. Do NOT ignore unexpected top hits (e.g., "Mesenchymal Stem Cell" for an erythroid gene), as they may reveal regulatory potential. However, you MUST also search for and include the expected disease-relevant tissues (e.g., K562/Erythroblast) to ensure the report directly addresses the clinical context.

  • Verify Tissue Relevance:

    • Match Disease to Organ System: If the disease is "Cardiomyopathy", you MUST use "heart", "atrium", "ventricle", or "cardiomyocyte".

    • Avoid Generic Proxies: Do NOT use "Smooth Muscle Cell" for Heart (Cardiac Muscle != Smooth Muscle). Do NOT use "Fibroblast" for Brain.

    • Search Strategy: If a specific cell type query (e.g., "cardiomyocyte") yields 0 hits, search for the organ (e.g., "heart", "cardiac"). While you should report unexpected top hits in other tissues, ensure you also include the relevant organ/tissue to address the clinical context.

  • Verify Location (GTF Overlap): Do NOT guess "Promoter" vs "5' UTR". Check the GTF coordinates. A variant at -30 might be in the 5' UTR if the TSS is upstream. Use lookup_gene_info.py --coord='chr:pos' or bedtools intersect to confirm.


Score Interpretation

Raw Score vs Quantile Score
  • Raw score: Effect magnitude, scorer-specific scale. Use for comparing tissues WITHIN the same scorer only.

  • Quantile score: Percentile rank vs common variants. Use to assess significance. Saturates at ±0.999990.

  • See variant-scoring-info section in alphagenome-api.md for mathematical details.

Magnitude Rules

[!NOTE] Disclaimer: The interpretation of raw scores depends heavily on the specific modality and assay type. The thresholds below are general rules of thumb, primarily derived from RNA-seq data, and should not be treated as absolute rules. Always validate quantitative scores by visually inspecting the plotted tracks.

  • < 0.1: Typically indicates No Significant Effect or background noise, even if the quantile score is high.

  • 0.1 - 0.5: Often represents a subtle or weak effect. Report as a potential subtle change.

  • 0.5 - 1.0: Suggests a moderate effect (roughly corresponding to a 1.4-2x fold change in RNA-seq).

  • > 1.0: Strong effect (generally >2x fold change for RNA-seq).

  • RNA-seq raw_score ≈ log2 fold-change: -4 ≈ 16-fold reduction, -1 ≈ 2-fold reduction, -0.35 ≈ 1.27-fold reduction.

  • NO percentage interpretation: Raw scores are NOT percentages. Do not interpret "0.09" as "9%".

  • Relative Magnitude: Use relative comparisons (e.g., "low magnitude compared to TERT's 1.5") or qualitative terms (e.g., "marginal effect").

  • Always cite the raw score in reports (e.g., "Raw Score -1.89").

High Quantile + Low Raw Score

This is the most common trap. A quantile of 0.99+ with |raw_score| < 0.1 is effectively NO MOLECULAR EFFECT. This occurs in low-expression genes where variance stabilization inflates quantiles. Report as "No Significant Effect" and explain the statistical artifact.

Negative Results & Scientific Integrity

[!CRITICAL] Most variants are Benign. Do not "stretch" to find a mechanism where none exists.

  • Value of Negative Results: Reporting "AlphaGenome predicts NO molecular effect" is a valuable scientific finding.

  • Strict Anti-Speculation: Do not invent mechanisms (e.g., "cryptic splice site", "enhancer disruption") unless explicitly shown by the model. If distinct evidence is missing, use broad terms like "predicted splicing disruption".

  • Occupancy ≠ Disruption: A variant landing in an active enhancer (e.g., H3K27ac peak present) or promoter (e.g. before gene TSS) does not imply disruption. If REF and ALT tracks are identical and scores are near zero, the variant has no predicted effect. Do not claim disruption based on location alone.

  • Model Limitations: AlphaGenome is a DNA-to-molecular phenotype model but has limited scope of modeled molecular phenotypes. For example, it does NOT model:

    • Post-Transcriptional RNA Biology: Beyond splicing (e.g., RNA secondary structure folding, macromolecular assembly, transport).

    • miRNA Processing: Due to low abundance or short length of transcripts.

    • Protein Coding Effects: Missense, nonsense, or frameshift mutations affecting protein structure or function.

    • Developmental Specificity: Effects restricted to specific developmental timeframes not represented in the training data.

    • Environmental or Dynamic Contexts: Effects triggered by specific external stimuli or dynamic cell states not captured by the static biosample profiles.


ISM (In-Silico Mutagenesis) Interpretation

Reading SeqLogo Plots
  • Tall letters at variant position: Mutation directly disrupts an important motif.

  • Positive height = activating when present; Negative = repressive.

  • REF vs ALT: Strong REF letter → ALT disrupts binding site. Strong ALT letter → ALT creates new binding site.

Motif Identification Rules

Use your base knowledge about sequences (semantic knowledge) to identify motifs when available. For well-known canonical sequences, you can identify directly:

MotifSequenceContext Required
TATA BoxTATAAA / TTTATAVerify in Promoter
PolyA SignalAATAAA / TTTATTVerify in 3' UTR
Splice DonorGTVerify at intron boundary
Splice AcceptorAGVerify at intron boundary
E-box (MYC/MAX)CACGTG—
GRE (Glucocorticoid)TGTTCT—

For less obvious sequences: use your knowledge of TF motifs, and if no confident match is found, report the consensus sequence with "resembles" or "potential" qualifier (e.g., "Disrupted motif resembling GATA consensus").

Reverse Complement

ALWAYS check the reverse complement. The model sees double-stranded DNA, so the motif may be on the minus strand (e.g., AATAAA ↔ TTTATT).

Negative ISM

If the ISM plot shows only tiny bars (<0.1 height) or random noise, report "No specific motif disruption identified." Do not force a match.


Model Limitations

AlphaGenome predicts transcription and splicing from DNA sequence. It does NOT model:

  • miRNA processing (low abundance / short length)

  • RNA secondary structure (e.g., 3' UTR selenocysteine insertion sequences, snRNA stem-loops)

  • Protein folding or stability (missense effects)

  • Catalytic activity (variant may produce stable but non-functional RNA)

  • Developmental timing or stress-response contexts

Rules:

  • If the gene is a non-coding RNA (snRNA, tRNA, rRNA) and you see High Quantile + Low Raw Score: report "No Significant Effect" and state the structural limitation.

  • If the known mechanism is protein stability: state that benign regulatory scores do not rule out protein-level pathogenicity.

  • If the known mechanism is enzymatic/catalytic: do not rule out pathogenicity from neutral expression scores.


Ontology Resolution Best Practices

The resolve_ontology_terms script implements smart matching. Key principles:

  1. Specificity first: Prefer "Naive thymus-derived CD4-positive..." over generic "T-cell".

  2. No silent fallbacks: Better to return [NOT FOUND] than silently map "Kupffer cell" → "Liver".

  3. You bridge disease → tissue: The script matches terms, not diseases. You must identify that "Multiple Sclerosis" → Oligodendrocyte, T-cell, Brain, then query those terms.

  4. Abbreviation handling: Common abbreviations (lv → left ventricle, huvec → human umbilical vein endothelial) are built in.

  5. Conservation of specificity: A match is rejected if any substantive query token is missing from the target. Only generic stopwords ("human", "tissue", "sample") can be safely dropped.

  6. Partial match flagging: If a partial match or fallback is necessary, it must be explicitly flagged as [PARTIAL MATCH] in the output.

Tissue selection for reports:

  • Match disease to organ system: "Cardiomyopathy" → heart, atrium, ventricle, cardiomyocyte.

  • Avoid generic proxies: Do NOT use "Smooth Muscle Cell" for heart (cardiac ≠ smooth), "Fibroblast" for brain.

  • Search strategy: If specific query (e.g., "cardiomyocyte") yields 0 hits, search for the organ ("heart", "cardiac").


Pre-Report Reasoning Checklist

Complete this BEFORE writing the report. Ground every interpretation in specific visual observations from the plots.

[!CAUTION] Do not pursue only the "obvious" answer (nearest gene, literature-known tissue). Focus on where the model shows the strongest signal. Ensure you have examined ALL significant scores, not just a convenient "top 5".

1. Cross-Tissue & Cross-Modality Patterns
  • [ ] Analyze tissue specificity: Determine if the effect is universal or tissue-restricted, and explain why.

  • [ ] Check modality agreement: Verify if different modalities agree within each tissue (concordant = strong evidence; discordant = complex regulation or potential model limitation).

  • [ ] Identify largest effect: Pinpoint which tissue shows the largest effect and assess its biological plausibility.

2. Hypothesis Validation
  • [ ] Cite supporting plots: Explicitly state which plots support or refute the proposed molecular mechanism.

  • [ ] Cite supporting scores: Explicitly state which variant scores support or refute the proposed molecular mechanism.

  • [ ] Identify motif disruptions: Detail the motif disruptions evident from REF vs ALT differences.

  • [ ] Check consistency: Determine if disruptions are consistent across tissues or tissue-specific.

  • [ ] Explain magnitude differences: Use ISM plots to explain magnitude differences between tissues.

4. Synthesis
  • [ ] Define primary molecular mechanism: Trace the chain of events: E.g. motif disruption → chromatin effect → transcriptional consequence → potential disease link.

  • [ ] Avoid speculation: If scores are low and plots are flat, report "No Significant Effect" instead of forcing a story.

  • [ ] Address original query: Ensure the report directly answers the user's initial question.

5. Report Readiness
  • [ ] Write a narrative: Focus on telling a biological story, not just dumping data.

  • [ ] Verify references: Ensure all plot files are present and correctly referenced.

  • [ ] Embed all views: Include ISM plots, Detail Views, and Whole-Gene Views where applicable.

  • [ ] Confirm evidence: Verify that allegations of splicing have the required splicing-related plots showing effects, expression changes have RNA-seq differences, and regulatory effects have DNASE/ChIP peak changes.


Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an API key, Needs Python

Security

What our scanner noticed· Low risk

  • Instructions that use the network
  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Google DeepMind
Publisher
Google DeepMind (Official)
Source
google-deepmind/science-skills · skills/alphagenome_single_variant_analysis · commit 4de6786
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Google DeepMind.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download alphagenome-single-variant-analysis.zip