liftover-coordinates

Convert genomic coordinates between genome assemblies with provenance tracking.

26|5|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/ammawla/encode-toolkit --skill liftover-coordinates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: liftover-coordinates
Source: https://github.com/ammawla/encode-toolkit/tree/main/plugin/skills/liftover-coordinates
Command: npx skills add https://github.com/ammawla/encode-toolkit --skill liftover-coordinates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires CrossMap, UCSC chain files, Ensembl REST API, rtracklayer, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables accurate conversion of genomic coordinates between different genome assemblies, preventing errors in data integration.

Core Features & Use Cases

  • Coordinate Liftover: Guides users through transforming coordinates between assemblies like hg19 and hg38, or mm9 and mm10, using tools like UCSC liftOver, CrossMap, or Ensembl API.
  • Provenance Tracking: Logs conversion details including chain files, tools, and loss rates to ensure reproducibility.
  • Use Case: A researcher wants to combine GWAS data from hg19 with ENCODE peaks aligned to GRCh38. This Skill automates the liftover process, handles unmapped regions, and records the operation for reproducibility.

Quick Start

Input the coordinates in the source assembly and specify target assembly; then run the liftover process for accurate position mapping.

Frequently Asked Questions about liftover-coordinates

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

FAQPage Schema
How do I convert genomic coordinates from hg19 to hg38?

To convert genomic coordinates from hg19 to hg38, you input your source assembly coordinates and specify the target assembly. The Skill uses UCSC chain files and tools like CrossMap to ensure accurate position mapping across different genome assemblies.

Can I use CrossMap to liftover VCF and BED files between genome assemblies?

Yes, you can use CrossMap to liftover VCF and BED files between genome assemblies. The Skill handles multiple formats including BED, VCF, bigWig, and BAM, ensuring accurate conversion across multiple species and versions.

What is the best way to track provenance during a genome coordinate liftover?

The best way to track provenance during a genome coordinate liftover is by logging conversion details automatically. This Skill records chain files, tools used, and loss rates to ensure your bioinformatics workflow remains fully reproducible.

Does this genomic coordinate conversion handle unmapped regions in GWAS data?

Yes, this genomic coordinate conversion handles unmapped regions in GWAS data. When combining datasets like hg19 GWAS data with GRCh38 ENCODE peaks, the Skill automates the liftover process and properly manages regions that fail to map.

Why do I need UCSC chain files for genomic coordinate conversion?

You need UCSC chain files for genomic coordinate conversion because they provide the mapping matrix between different genome assemblies. The Skill relies on these chain files alongside tools like rtracklayer and the Ensembl REST API to ensure accurate results.

When should I not use Ensembl REST API for liftover coordinate conversion?

You should avoid using the Ensembl REST API for liftover coordinate conversion when working with large batch files like BAM or bigWig, as local tools such as CrossMap or UCSC liftOver paired with chain files offer better reproducibility and provenance tracking.