ensembl-database
Skill0 starsChanged 25 days agoApache-2.0View on GitHub
Query the Ensembl database to resolve gene, transcript, and protein IDs, fetch genomic or protein sequences, retrieve gene structures (exons), and get variant consequence and effect predictions (VEP). Use this skill as a primary ID translator, genomic sequence database and variant effect prediction tool.
11 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- 1stANUNNAKI/majlisedited, first seen Nov 8, 2026
- MarieLynneBlock/arcanum-artifextheir own version, first seen Nov 1, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- garri333/Skillstheir own version, first seen Oct 11, 2026
- wu-yc/LabClawtheir own version, first seen Oct 8, 2026
Other versions11 projects use a version of this.
Word for word · 1
- google-deepmind/science-skills★ 3.4k100% same
Edited · 2
- 1stANUNNAKI/majlis★ 297% same
- uppifyagency/boilerplate-saas-2026★ 199% same
Wrote their own version · 8
- wu-yc/LabClaw★ 1.1ksame name
- LeonChaoX/qinyan-academic-skills★ 910same name
- qinyan-ai/qinyan-academic-skills★ 80same name
- MarieLynneBlock/arcanum-artifex★ 4same name
- BrightGold70/skills★ 1same name
- garri333/Skills★ 1same name
- yf8578/claude-skills-collection★ 1same name
- davidanthonyn/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- vector-geneSkill
- alphafold-database-fetch-and-analyzeSkill
- alphagenome-atlas-website-linksSkill
- alphagenome-single-variant-analysisSkill
- alphagenome-variant-impact-scoreSkill
- chembl-databaseSkill
- clinical-trials-databaseSkill
- clinvar-databaseSkill
- credentialsSkill
- dbsnp-databaseSkill
- embl-ebi-olsSkill
- encode-ccres-databaseSkill
- foldseek-structural-searchSkill
- gnomad-databaseSkill
- gtex-databaseSkill
- human-protein-atlas-databaseSkill
- interpro-databaseSkill
- jaspar-databaseSkill
- literature-search-arxivSkill
- literature-search-biorxivSkill
- literature-search-europepmcSkill
- literature-search-openalexSkill
- ncbi-sequence-fetchSkill
- openfda-databaseSkill
- opentargets-databaseSkill
- pdb-databaseSkill
- predictingthepastSkill
- protein-sequence-msaSkill
- protein-sequence-similarity-searchSkill
- pubchem-databaseSkill
- pubmed-databaseSkill
- pymolSkill
- quickgo-databaseSkill
- reactome-databaseSkill
- string-databaseSkill
- ucsc-conservation-and-tfbsSkill
- unibind-databaseSkill
- uniprot-databaseSkill
- uvSkill
- workflow-skill-creatorSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 7 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
uv: Read the uv skill and follow its Setup instructions to ensure uv is installed and on PATH. - Very specific: line 17
User Notification: If .licenses/ensembl_database_LICENSE.txt does not already exist in the workspace root directory then (1) prominently …
- Distinctive: line 44
Use the Wrapper: ALWAYS execute the provided helper scripts to query the database rather than accessing the database directly.
- Very specific: line 47
Default Species: If the species is absent or ambiguous in the prompt, default to "human".
- Distinctive: line 50
Primary Transcripts: When listing transcripts for a gene, only return the MANE Select transcript (for human) or the Canonical transcript …
- Distinctive: line 53
MUST flag to the user when multiple transcripts are available and you are defaulting to the primary one.
- Distinctive: line 61
Notification: If this skill is used, ensure this is mentioned in the output.
- Distinctive: line 171
Presenting VEP Results: After running the VEP command, you MUST present the full VEP Predictions list from stdout to the user.
- Distinctive: line 182
If the user needs detailed, nested structural data (like the precise integer coordinates of Exon 2 of a transcript) that isn't summarized …
- Very specific: line 187
Use terminal tools like jq or write a quick, disposable python snippet to extract the specific data point requested.
- Distinctive: line 193
If you need to make an API call that the script does not support (e.g., fetching protein domain annotations, coordinate mapping between …
- Very specific: line 199
CRITICAL: When writing custom scripts or using alternatives to the provided scripts, you MUST respect the Ensembl REST API rate limits …
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ensembl Database: ID Mapping and Genomic Features
Prerequisites
uv: Read theuvskill and follow its Setup instructions to ensureuvis installed and on PATH.- User Notification: If .licenses/ensembl_database_LICENSE.txt does not already exist in the workspace root directory then (1) prominently notify the user to check the terms at https://useast.ensembl.org/index.html and https://github.com/Ensembl/ensembl-rest/wiki, then (2) create the file recording the notification text and timestamp.
Overview
The Ensembl database is a resource for genome annotation. This skill allows you to interact with the Ensembl REST API to resolve ambiguous symbols, cross-reference IDs (RefSeq, HGNC, UniProt, ENSG), fetch raw sequences, and retrieve detailed transcript structures.
Key Concepts:
- ENSG (Gene): Stable identifier for a human gene. Other species will have different three-letter species codes.
- ENST (Transcript): Stable identifier for a transcript (splicing isoform).
- ENSP (Protein): Stable identifier for a translated protein.
- MANE Select: The consensus primary transcript agreed upon by Ensembl and NCBI.
- Canonical: Ensembl's representative transcript (used if MANE is not available or non-human).
Core Rules
- Use the Wrapper: ALWAYS execute the provided helper scripts to query the database rather than accessing the database directly. The scripts automatically enforce the required rate limit gracefully.
- Default Species: If the species is absent or ambiguous in the prompt,
default to
"human". You MUST explicitly flag this default to the user to ensure they are aware. - Primary Transcripts: When listing transcripts for a gene, only return the MANE Select transcript (for human) or the Canonical transcript (for others) unless the user explicitly asks for all alternative isoforms. You MUST flag to the user when multiple transcripts are available and you are defaulting to the primary one.
- Assembly Handling: The default assembly is GRCh38. For GRCh37 requests,
you MUST use the
--assembly GRCh37flag. You MUST explicitly flag to the user when a non-default assembly is being used. - Output Location: The script writes full JSON/FASTA output to temporary
files in
/tmpby default, or to a user-specified file using the--outputflag. It also prints a concise summary to stdout. - Notification: If this skill is used, ensure this is mentioned in the output.
Available Commands
1. Resolve Gene ID — Resolve a symbol, alias, or RefSeq ID to ENSG ID(s). Automatically falls back to resolving synonyms if primary symbol is not found.
uv run scripts/ensembl_api.py resolve-gene TP53 --species human --output tp53.json
uv run scripts/ensembl_api.py resolve-gene PCL2 --output pcl2.json # Falls back to synonym resolution2. Map ID to External Database — Cross-reference an Ensembl ID to UniProt, HGNC, RefSeq, etc.
uv run scripts/ensembl_api.py map-id ENSG00000141510 --external-db UniProt --output uniprot_map.json
uv run scripts/ensembl_api.py map-id ENST00000269305 --external-db RefSeq_mRNA --output refseq_map.json3. Get Genomic Sequence — Fetch raw DNA for a coordinate window. Supports
GRCh37 via --assembly GRCh37.
uv run scripts/ensembl_api.py get-sequence 17:7661779-7687550 --species human --output seq.txt
uv run scripts/ensembl_api.py get-sequence chr9:21971100-21971200 --assembly GRCh37 --output seq_grch37.txt4. Gene Summary — High-level metadata: symbol, biotype, description, chromosomal location.
uv run scripts/ensembl_api.py gene-summary ENSG00000141510 --output gene_summary.json5. List Transcripts — All transcripts for a gene, with optional
--only-mane or --only-canonical filters. Output includes Transcript Support
Level (TSL).
uv run scripts/ensembl_api.py transcripts ENSG00000141510 --only-mane --output transcripts_mane.json
uv run scripts/ensembl_api.py transcripts ENSG00000141510 --only-canonical --output transcripts_canonical.json
uv run scripts/ensembl_api.py transcripts ENSG00000141510 --output transcripts_all.json5b. Canonical TSS — Get the single coordinate of the Transcription Start Site (TSS) for the canonical transcript of a gene.
[!NOTE] Unlike the standard
transcriptscommand,canonical-tssaccepts both symbols (e.g.,TP53) and Ensembl IDs, and automatically resolves them. It also does the math for strand orientation (TSS isStartfor+strand andEndfor-strand), outputting the single integer coordinate directly.
uv run scripts/ensembl_api.py canonical-tss TP53 --output tp53_tss.json
uv run scripts/ensembl_api.py canonical-tss ENSG00000141510 --output tss.json6. Transcript Structure — Exon coordinates, CDS boundaries, and computed 5'/3' UTR regions for a transcript.
uv run scripts/ensembl_api.py transcript-structure ENST00000269305 --output structure.json7. Protein Info — ENSP ID and sequence length for a transcript.
uv run scripts/ensembl_api.py protein-info ENST00000269305 --output protein_info.json8. Protein Sequence — Amino acid FASTA for a transcript (ENST) or protein (ENSP) ID.
uv run scripts/ensembl_api.py protein-sequence ENST00000269305 --output protein.fasta
uv run scripts/ensembl_api.py protein-sequence ENSP00000269305 --output protein_ensp.fasta9. Variant Consequence (VEP) — Predict molecular consequences for a genomic variant. Includes open-licensed plugins: AlphaMissense, Conservation, DosageSensitivity, IntAct, MaveDB, OpenTargets, LoF (Loftee), NMD, UTRAnnotator, mutfunc, LOEUF.
uv run scripts/ensembl_api.py vep 9:21971147:T:C --species human --output vep.json
uv run scripts/ensembl_api.py vep rs699 --species human --output vep_rs699.jsonExample VEP stdout output:
[*] Variant: 9:21971147:T>C
[*] Most severe consequence: missense_variant
[*] Found 15 transcript consequences.
[*] VEP Predictions:
- ENST00000304494 (CDKN2A): Consequence = missense_variant
- ENST00000304494 (CDKN2A): Amino Acids = N/S
- ENST00000304494 (CDKN2A): SIFT = deleterious (0.01)
- ENST00000304494 (CDKN2A): AlphaMissense Class = likely_benign
- ENST00000304494 (CDKN2A): AlphaMissense Pathogenicity = 0.2129
- ENST00000304494 (CDKN2A): Conservation = 2.05
- ENST00000304494 (CDKN2A): Dosage Sensitivity (Haplo) = 0.889228328567991
- ENST00000304494 (CDKN2A): Dosage Sensitivity (Triplo) = 0.135514349094646
- ENST00000304494 (CDKN2A): Loss of Function (LOEUF) = 0.791Presenting VEP Results: After running the VEP command, you MUST present the full VEP Predictions list from stdout to the user. This list contains both standard VEP predictions (Consequence, Amino Acids, SIFT, PolyPhen) and open-license plugin results (AlphaMissense, Conservation, Dosage Sensitivity, LOEUF, Loftee LoF, NMD, UTRAnnotator, Mutfunc). Do NOT just summarize — show the complete list so the user can see all predictions. If the list is very long (many transcripts), show the MANE Select / canonical transcript rows in full and note that the complete data is in the JSON output.
Parsing Outputs
If the user needs detailed, nested structural data (like the precise integer coordinates of Exon 2 of a transcript) that isn't summarized in stdout:
- Locate the JSON file (either specified via
--outputor the temporary file path printed by the script). - Use terminal tools like
jqor write a quick, disposable python snippet to extract the specific data point requested. Do not attempt to read the entire JSON file into your context if it is very large.
Custom Queries
If you need to make an API call that the script does not support (e.g., fetching
protein domain annotations, coordinate mapping between assemblies, homology
searches, linkage disequilibrium, or phenotype lookups), read
references/ensembl_rest_api_reference.md for a complete reference of available
endpoints, parameters, and response fields.
CRITICAL: When writing custom scripts or using alternatives to the provided
scripts, you MUST respect the Ensembl REST API rate limits (maximum 15
requests per second) and handle 429 Too Many Requests errors gracefully (e.g.,
with exponential backoff).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

