Skip to main content Skills Marketplace Discover and explore AI skills built by the community.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Show prompt details A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/celestiaorg/hyperlane-ops --skill warp-routeThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Download Zip Downloading... More from this repository
Related occupations SOC
Based on SOC occupation classification
name warp-route description Use this skill when creating, updating, deploying, applying, verifying, or manually testing Hyperlane Warp Routes in this repository (including EVM and Celestia flows).
Warp Route Skill
When to use
Use this skill when the task involves any of the following in this repo:
Adding or updating deployments/warp_routes/<TOKEN>/*-deploy.yaml
Running hyperlane warp deploy or hyperlane warp apply
Producing/updating *-config.yaml warp artifacts
Updating deployments/warp_routes/warpRouteConfigs.yaml
Verifying routers, standards, connections, and decimals
Manual transfer debugging with cast (EVM) or celestia-appd (Celestia)
Required user input intake
Before drafting configs or running any deploy/apply command, explicitly ask the user for missing route inputs.
Minimum required inputs:
token symbol (e.g. USDC)
chains in route (e.g. sepolia, edentestnet, celestiatestnet)
canonical/collateral chain
collateral token address or denom on canonical chain
decimals per chain (or confirmation they are identical)
route intent: new route vs update existing route
Also ask/confirm when unclear:
token name
owner addresses per chain
mesh preference (full mesh vs constrained routing)
whether docs/index updates are required
Source of truth
Always use local docs and local registry files first:
docs/warp-route-multichain.md
docs/manual-warp-transfer.md
deployments/warp_routes/schema.json
deployments/warp_routes/warpRouteConfigs.yaml
existing routes under deployments/warp_routes/<TOKEN>/ Do not rely on memory for chain names, domain IDs, token IDs, or router addresses; copy from repo files.
Required environment Before CLI operations, ensure:
HYP_KEY is set for EVM-chain signingHYP_KEY_COSMOSNATIVE is set for Celestia/cosmosnative signing
HYP_MNEMONIC if direct celestia-appd key recovery is neededchain-specific keys like HYP_CHAINS_<CHAIN>_SIGNER_KEY from .env
Deployer readiness gate (must run before deploy/apply) Always verify deployer configuration before running hyperlane warp deploy or hyperlane warp apply.
use HYP_KEY for EVM chains
use HYP_KEY_COSMOSNATIVE for Celestia/cosmosnative chains
If either required key is missing:
stop and prompt the user to set it (or confirm an alternate signer flow)
do not proceed with deploy/apply until signer configuration is explicit
Workflow
1) Preflight
Confirm all required user inputs are collected (see intake section).
Confirm deployer readiness gate passes (HYP_KEY / HYP_KEY_COSMOSNATIVE as needed).
Confirm chain metadata exists under chains/<chain>/metadata.yaml.
Confirm target route naming convention and chain order in filename:
deployments/warp_routes/<TOKEN>/<chainA>-<chainB>-...-deploy.yaml
Confirm token role per chain (collateral, synthetic, or native) and decimals.
2) Author/update deploy config
Copy an existing route as template where possible.
Set owner, type, token/denom, name, symbol, decimals.
For cosmosnative chains, include fields required by local docs (e.g. scale when needed).
3) Deploy or apply Deploy new route, where <TOKEN> is the token symbol in the warp routes deployments directory of the registry, e.g. ETH:
hyperlane warp deploy \
--warp-route-id <TOKEN>
--registry .
Apply update to existing route:
hyperlane warp apply \
--symbol <TOKEN> \
--config ./deployments/warp_routes/<TOKEN>/<route>-deploy.yaml \
--registry .
4) Persist generated artifacts
Commit generated *-config.yaml.
Update deployments/warp_routes/warpRouteConfigs.yaml with the route block.
Verify the index update actually happened; if CLI did not write it, append the new block manually from generated config.
5) Verify hyperlane warp read --symbol <TOKEN> --registry .
token standard matches intended type per chain
collateralAddressOrDenom exists on collateral routeconnections include expected peers (full mesh unless intentionally restricted)
decimals and symbol/name match deploy config
If multiple routes share the same symbol, select the intended route ID when prompted.
6) Manual transfer/debug flows Use docs/manual-warp-transfer.md:
EVM-origin route calls via cast (approve where collateral applies, then transferRemote)
Celestia-origin via celestia-appd tx warp transfer
Useful Celestia preflight queries:
celestia-appd query warp token <token-id> --node <rpc> -o json
celestia-appd query warp remote-routers <token-id> --node <rpc> -o json
celestia-appd query warp quote-transfer <token-id> <destination-domain> --node <rpc> -o json
Guardrails
Always pass --registry . for Hyperlane CLI commands in this repo.
Never remove or overwrite unrelated warp routes when adding a new one.
Never commit secrets/private keys.
Keep route index and generated config in sync.
