/clinvar-annotation
Guide for annotating ENCODE regulatory variants with ClinVar clinical significance. Use when users need to check if variants in ENCODE peaks have clinical associations, find pathogenic variants in regulatory regions, or assess variant clinical impact. Trigger on: ClinVar,
$ npx -y skills add ammawla/encode-toolkit --skill clinvar-annotation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/clinvar-annotation
Context preview
The summary Claude sees to decide when to auto-load this skill.
Guide for annotating ENCODE regulatory variants with ClinVar clinical significance. Use when users need to check if variants in ENCODE peaks have clinical associations, find pathogenic variants in regulatory regions, or assess variant clinical impact. Trigger on: ClinVar,
SKILL.md
clinvar-annotation.SKILL.mdname: clinvar-annotation
description: "Guide for annotating ENCODE regulatory variants with ClinVar clinical significance. Use when users need to check if variants in ENCODE peaks have clinical associations, find pathogenic variants in regulatory regions, or assess variant clinical impact. Trigger on: ClinVar, clinical significance, pathogenic variant, variant classification, clinical variant, disease variant, VUS, benign, likely pathogenic."
When to Use
- User wants to check if variants in ENCODE regulatory peaks have clinical significance in ClinVar
- User asks about "ClinVar", "pathogenic variants", "clinical significance", or "variant classification"
- User needs to annotate ENCODE-derived regulatory variants with disease associations
- User wants to find clinically relevant variants within enhancers, promoters, or open chromatin regions
- Example queries: "check ClinVar for variants in my ATAC-seq peaks", "find pathogenic variants in pancreas enhancers", "annotate regulatory variants with clinical significance"
Annotating ENCODE Regulatory Variants with ClinVar Clinical Significance
Cross-reference ENCODE functional genomic elements with ClinVar clinical variant classifications to identify pathogenic variants in regulatory regions and understand non-coding disease mechanisms.
Scientific Rationale
**The question**: "Do any clinically significant variants fall within my ENCODE regulatory elements, and can ENCODE data explain their pathogenic mechanism?"
ClinVar is NCBI's public archive of variant-disease associations, aggregating submissions from clinical laboratories, research groups, and expert panels. Most ClinVar annotations focus on coding variants, but a growing number of non-coding variants are being classified. ENCODE provides the functional context to explain WHY a non-coding variant is pathogenic — by showing that it disrupts an active enhancer, promoter, or insulator in disease-relevant tissue.
This bidirectional integration serves two use cases: 1. **Forward**: Start from ENCODE peaks, find clinically significant variants within them 2. **Reverse**: Start from ClinVar pathogenic variants, use ENCODE to explain their mechanism
The Non-Coding Variant Challenge
- ~90% of GWAS-associated variants are in non-coding regions (Maurano et al. 2012)
- ClinVar increasingly includes non-coding variants, but most lack mechanistic annotation
- ENCODE regulatory annotations provide the "why" behind non-coding pathogenicity
- A variant classified as VUS (variant of uncertain significance) may be reclassified with ENCODE functional evidence
Key Literature
- **Landrum et al. 2018** "ClinVar: improving access to variant interpretations and supporting evidence" (Nucleic Acids Research, ~2,000 citations). Describes the ClinVar database architecture, submission standards, and the star-rating review system for variant classifications. [DOI: 10.1093/nar/gkx1153](https://doi.org/10.1093/nar/gkx1153)
- **Riggs et al. 2020** "Technical standards for the interpretation and reporting of constitutional copy-number variants: a joint consensus recommendation of the ACMG and ClinGen" (Genetics in Medicine, ~500 citations). Framework for interpreting structural variants, relevant when ENCODE elements overlap CNVs. [DOI: 10.1038/s41436-019-0686-8](https://doi.org/10.1038/s41436-019-0686-8)
- **Richards et al. 2015** "Standards and guidelines for the interpretation of sequence variants: ACMG/AMP joint consensus recommendation" (Genetics in Medicine, ~12,000 citations). The ACMG variant classification framework (pathogenic through benign). ENCODE functional data can provide evidence for PS3/BS3 (functional studies) criteria. [DOI: 10.1038/gim.2015.30](https://doi.org/10.1038/gim.2015.30)
- **ENCODE Project Consortium 2020** (Nature, ~1,656 citations). Registry of 926,535 human cCREs — the functional annotation layer for interpreting non-coding ClinVar variants. [DOI: 10.1038/s41586-020-2493-4](https://doi.org/10.1038/s41586-020-2493-4)
ClinVar Clinical Significance Categories
| Classification | Meaning | ENCODE Relevance | |---------------|---------|-----------------| | **Pathogenic** | Causes disease | If in regulatory region, ENCODE explains mechanism | | **Likely pathogenic** | Strong evidence for disease causation | ENCODE data may upgrade to pathogenic | | **Uncertain significance (VUS)** | Not enough evidence to classify | ENCODE functional data may help resolve | | **Likely benign** | Strong evidence against pathogenicity | — | | **Benign** | Does not cause disease | — | | **Conflicting interpretations** | Labs disagree on classification | ENCODE data may resolve conflict | | **Risk factor** | Increases disease risk | May overlap ENCODE regulatory elements |
ClinVar Star Ratings
| Stars | Review Status | Confidence | |-------|-------------|-----------| | 0 | No assertion criteria | Very low — treat with caution | | 1 | Single submitter with criteria | Low-moderate | | 2 | Multiple submitters, no conflict | Moderate | | 3 | Expert panel reviewed | High | | 4 | Practice guideline | Highest |
**Always check star ratings.** A 0-star "pathogenic" classification has very different reliability than a 3-star classification.
NCBI E-utilities API Reference
**Base URL**: `https://eutils.ncbi.nlm.nih.gov/entrez/eutils/`
No authentication required for low-volume use. Rate limit: 3 requests/second without API key, 10/second with NCBI API key.
Key Endpoints
| Endpoint | Purpose | Example | |---------|---------|---------| | `esearch.fcgi?db=clinvar&term=...` | Search ClinVar | Search by gene, variant, condition | | `efetch.fcgi?db=clinvar&id=...` | Fetch full record | Get complete variant details | | `esummary.fcgi?db=clinvar&id=...` | Summary record | Get classification, review status | | `elink.fcgi?db=clinvar&dbfrom=...` | Cross-database links | Link to PubMed, Gene, etc. |
ClinVar VCF Downloads
For bulk intersection with ENCODE peaks, download the Cl
Read more
name: clinvar-annotation description: "Guide for annotating ENCODE regulatory variants with ClinVar clinical significance. Use when users need to check if variants in ENCODE peaks have clinical associations, find pathogenic variants in regulatory regions, or assess variant clinical impact. Trigger on: ClinVar, clinical significance, pathogenic variant, variant classification, clinical variant, disease variant, VUS, benign, likely pathogenic."
When to Use
- User wants to check if variants in ENCODE regulatory peaks have clinical significance in ClinVar
- User asks about "ClinVar", "pathogenic variants", "clinical significance", or "variant classification"
- User needs to annotate ENCODE-derived regulatory variants with disease associations
- User wants to find clinically relevant variants within enhancers, promoters, or open chromatin regions
- Example queries: "check ClinVar for variants in my ATAC-seq peaks", "find pathogenic variants in pancreas enhancers", "annotate regulatory variants with clinical significance"
Annotating ENCODE Regulatory Variants with ClinVar Clinical Significance
Cross-reference ENCODE functional genomic elements with ClinVar clinical variant classifications to identify pathogenic variants in regulatory regions and understand non-coding disease mechanisms.
Scientific Rationale
**The question**: "Do any clinically significant variants fall within my ENCODE regulatory elements, and can ENCODE data explain their pathogenic mechanism?"
ClinVar is NCBI's public archive of variant-disease associations, aggregating submissions from clinical laboratories, research groups, and expert panels. Most ClinVar annotations focus on coding variants, but a growing number of non-coding variants are being classified. ENCODE provides the functional context to explain WHY a non-coding variant is pathogenic — by showing that it disrupts an active enhancer, promoter, or insulator in disease-relevant tissue.
This bidirectional integration serves two use cases: 1. **Forward**: Start from ENCODE peaks, find clinically significant variants within them 2. **Reverse**: Start from ClinVar pathogenic variants, use ENCODE to explain their mechanism
The Non-Coding Variant Challenge
- ~90% of GWAS-associated variants are in non-coding regions (Maurano et al. 2012)
- ClinVar increasingly includes non-coding variants, but most lack mechanistic annotation
- ENCODE regulatory annotations provide the "why" behind non-coding pathogenicity
- A variant classified as VUS (variant of uncertain significance) may be reclassified with ENCODE functional evidence
Key Literature
- **Landrum et al. 2018** "ClinVar: improving access to variant interpretations and supporting evidence" (Nucleic Acids Research, ~2,000 citations). Describes the ClinVar database architecture, submission standards, and the star-rating review system for variant classifications. [DOI: 10.1093/nar/gkx1153](https://doi.org/10.1093/nar/gkx1153)
- **Riggs et al. 2020** "Technical standards for the interpretation and reporting of constitutional copy-number variants: a joint consensus recommendation of the ACMG and ClinGen" (Genetics in Medicine, ~500 citations). Framework for interpreting structural variants, relevant when ENCODE elements overlap CNVs. [DOI: 10.1038/s41436-019-0686-8](https://doi.org/10.1038/s41436-019-0686-8)
- **Richards et al. 2015** "Standards and guidelines for the interpretation of sequence variants: ACMG/AMP joint consensus recommendation" (Genetics in Medicine, ~12,000 citations). The ACMG variant classification framework (pathogenic through benign). ENCODE functional data can provide evidence for PS3/BS3 (functional studies) criteria. [DOI: 10.1038/gim.2015.30](https://doi.org/10.1038/gim.2015.30)
- **ENCODE Project Consortium 2020** (Nature, ~1,656 citations). Registry of 926,535 human cCREs — the functional annotation layer for interpreting non-coding ClinVar variants. [DOI: 10.1038/s41586-020-2493-4](https://doi.org/10.1038/s41586-020-2493-4)
ClinVar Clinical Significance Categories
| Classification | Meaning | ENCODE Relevance | |---------------|---------|-----------------| | **Pathogenic** | Causes disease | If in regulatory region, ENCODE explains mechanism | | **Likely pathogenic** | Strong evidence for disease causation | ENCODE data may upgrade to pathogenic | | **Uncertain significance (VUS)** | Not enough evidence to classify | ENCODE functional data may help resolve | | **Likely benign** | Strong evidence against pathogenicity | — | | **Benign** | Does not cause disease | — | | **Conflicting interpretations** | Labs disagree on classification | ENCODE data may resolve conflict | | **Risk factor** | Increases disease risk | May overlap ENCODE regulatory elements |
ClinVar Star Ratings
| Stars | Review Status | Confidence | |-------|-------------|-----------| | 0 | No assertion criteria | Very low — treat with caution | | 1 | Single submitter with criteria | Low-moderate | | 2 | Multiple submitters, no conflict | Moderate | | 3 | Expert panel reviewed | High | | 4 | Practice guideline | Highest |
**Always check star ratings.** A 0-star "pathogenic" classification has very different reliability than a 3-star classification.
NCBI E-utilities API Reference
**Base URL**: `https://eutils.ncbi.nlm.nih.gov/entrez/eutils/`
No authentication required for low-volume use. Rate limit: 3 requests/second without API key, 10/second with NCBI API key.
Key Endpoints
| Endpoint | Purpose | Example | |---------|---------|---------| | `esearch.fcgi?db=clinvar&term=...` | Search ClinVar | Search by gene, variant, condition | | `efetch.fcgi?db=clinvar&id=...` | Fetch full record | Get complete variant details | | `esummary.fcgi?db=clinvar&id=...` | Summary record | Get classification, review status | | `elink.fcgi?db=clinvar&dbfrom=...` | Cross-database links | Link to PubMed, Gene, etc. |
ClinVar VCF Downloads
For bulk intersection with ENCODE peaks, download the Cl
Showing the first part of this file.
Search ENCODE, cross-reference 14 databases, run 7 analysis pipelines, and generate publication-ready methods — all from natural language in Claude Code.
Repo: ammawla/encode-toolkit
Other skills on encode-toolkit.
- /accessibility-aggregation
Build comprehensive chromatin accessibility maps by aggregating ATAC-seq and DNase-seq narrowPeak data across multiple ENCODE experiments, donors, and labs. Use when the user wants to answer "where is chromatin accessible in my tissue?" by combining peak calls into a union peak
Open skill - /batch-analysis
Guide for multi-experiment batch operations: QC screening, batch download, comparison, and report generation across many ENCODE experiments simultaneously. Use when users need to process 5+ experiments together, create experiment comparison tables, perform batch quality checks,
Open skill - /bioinformatics-installer
Install bioinformatics tools for ENCODE data analysis. Covers CLI tools (BWA, STAR, samtools, MACS2), R/Bioconductor packages (DESeq2, Seurat, ChIPseeker), Python packages (Scanpy, deeptools), and Nextflow pipeline infrastructure. Generates conda environments, R install scripts,
Open skill - /cellxgene-context
Guide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when users need cell-type-specific expression context for ENCODE regulatory data, want to deconvolve bulk ENCODE signals, or validate regulatory elements at single-cell resolution. Trigger
Open skill - /cite-encode
Generate proper ENCODE citations for publications, grants, and presentations. Use when the user needs to cite ENCODE data, create bibliography entries, write acknowledgment sections, or ensure compliance with ENCODE data use policy.
Open skill - /compare-biosamples
Compare ENCODE experiments across different biosamples, tissues, or cell lines to identify tissue-specific regulatory patterns. Use when the user wants cross-tissue comparison, cell-type comparison, tissue-specific elements, differential chromatin, biosample matching, disease vs
Open skill

