tooluniverse-regulatory-variant-analysis

Interprets non-coding variants using GWAS, eQTL, chromatin, and regulatory scoring evidence.

1.7k|254|Updated Mar 3, 2025
One-click install
npx skills add https://github.com/mims-harvard/ToolUniverse --skill tooluniverse-regulatory-variant-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tooluniverse-regulatory-variant-analysis
Source: https://github.com/mims-harvard/ToolUniverse/tree/main/plugins/tooluniverse/skills/tooluniverse-regulatory-variant-analysis
Command: npx skills add https://github.com/mims-harvard/ToolUniverse --skill tooluniverse-regulatory-variant-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interpreting non-coding and regulatory variants requires pulling evidence from many disconnected sources — GWAS catalogs, eQTL databases, chromatin annotations, and regulatory scoring systems — and synthesizing them into a defensible functional impact assessment, which is slow and error-prone when done manually.

Core Features & Use Cases

  • GWAS Association Lookup: Query the GWAS Catalog by rsID, trait, or EFO ID to find genome-wide significant trait associations and effect sizes.
  • eQTL and Regulatory Annotation: Retrieve GTEx tissue-specific eQTL evidence, RegulomeDB scores, and ENCODE histone mark data to determine whether a variant sits in an active regulatory element.
  • Evidence-Graded Impact Synthesis: Combine GWAS, eQTL, chromatin state, and TF-binding evidence into high/moderate/low confidence regulatory impact classifications.
  • Use Case: Given an intronic variant like rs429358, resolve its consequence with Ensembl VEP, check GWAS associations, query GTEx eQTLs for APOE, score it with RegulomeDB, confirm active chromatin via ENCODE H3K27ac, and produce an evidence-graded functional report.

Quick Start

Analyze the regulatory impact of variant rs429358 by looking up its GWAS associations, eQTL evidence, RegulomeDB score, and chromatin context.

Frequently Asked Questions about tooluniverse-regulatory-variant-analysis

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

FAQPage Schema
How do I interpret a non-coding GWAS variant?

Build evidence across four questions: whether the variant overlaps a regulatory element (RegulomeDB, ENCODE), whether it disrupts a TF binding site, whether eQTL data links it to a gene (GTEx), and whether GWAS shows trait association. Converging evidence across multiple lines indicates high-confidence regulatory impact.

How do I find eQTLs for a gene in a specific tissue?

Use GTEx_query_eqtl with a gene symbol or Ensembl ID to get tissue-specific SNP-gene associations with normalized effect sizes and p-values. Confirm the gene is actually expressed in the relevant tissue with GTEx_get_median_gene_expression before weighting the eQTL evidence.

What does a RegulomeDB score mean for variant interpretation?

RegulomeDB scores in categories 1a-2a indicate strong regulatory evidence such as eQTL overlap plus TF binding and chromatin accessibility. Scores 3a-6 represent progressively weaker evidence, and the scores are heuristic rather than proof of functional impact.

Why does my GWAS Catalog search return no results?

Free-text trait matching in the GWAS Catalog is imprecise because it uses controlled vocabulary. Resolve the trait name to an EFO ID with ols_search_terms first, then query with the efo_id parameter, or broaden the trait term.

When should I use regulatory variant analysis instead of coding variant interpretation?

Use regulatory variant analysis for non-coding variants such as intronic, UTR, and intergenic SNPs where the question is regulatory mechanism, eQTL effects, or GWAS hit annotation. Coding variant pathogenicity and ACMG clinical classification require a dedicated coding-variant interpretation skill.

What are the limitations of eQTL-based variant interpretation?

eQTL analysis identifies correlation, not causation, so fine-mapping is needed to pinpoint causal variants. GTEx data is from v8 and some v10 endpoints return empty, and GWAS associations are population-level, so individual effects depend on genetic background.