Skip to content
cccskills
FreePublished on GitHub

warp-fork

Fork a warp route from the local HTTP registry for development and testing. Forks each chain with the right local node per protocol — anvil for EVM chains, surfpool (Solana mainnet fork) for Sealevel chains. Use when the goal is to simulate transactions on a set of local forks before submitting them on-chain.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Warp Fork

Fork a warp route using the local HTTP registry.

Instructions:

  1. Check if http://localhost:3333 is running. If not, run the start-http-registry SKILL. If that fails, ask the user to prompt the user for an alternate registry URL to use instead of http://localhost:3333.

  2. First, ask the user to prompt the user for the warp route ID:

    • Question: "Which warp route would you like to fork?"
    • Header: "Warp Route"
    • Options: Provide 2-3 common examples if known, otherwise use generic placeholders. Note that the fork may fail if the warp routes are invalid. Re-prompt the user!
  3. Run the command in the background:

    pnpm -C typescript/cli exec tsx cli.ts warp fork --registry $REGISTRY --warpRouteId $WARP_ROUTE_ID
    
    • Use the registry URL from step 0 for $REGISTRY (http://localhost:3333 by default, or user-provided if the local registry failed)
    • Use run_in_background: true so it doesn't block the conversation.
  4. After starting, report the task/shell ID and the fork registry server port back to the user.

  5. Remind the user they can stop it later with KillShell using that ID

Prerequisites:

  • The http-registry server must be running on port 3333. If not, start it first with /start-http-registry.
  • Forking is per-protocol: EVM chains need Foundry anvil on PATH; Sealevel chains need a locally-installed surfpool binary (>= 1.5.0) on PATH — there is no Docker fallback in the CLI. Install the pinned, checksum-verified surfpool release the way CI does — see the Install surfpool step in .github/workflows/test-cli-e2e.yml (a pinned v1.5.0 release tarball verified against its SHA-256); do not pipe the mutable run.surfpool.run installer to a shell. If the binary is missing, warp fork aborts with a "surfpool 1.5.0+ is required" error before forking.

Related skills:

  • /warp-simulate-safe-txs — EVM fork → replay a Safe batch → check.
  • /warp-simulate-svm-txs — Sealevel fork → replay SVM/Squads governance txs → check.

Example output:

Started warp fork for EZETH/ethereum-megaeth in background (shell ID: shell_abc123). To stop it later, I can use KillShell with that ID.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Write a changeset file in the `hyperlane-registry` repo for a PR that adds, updates, or modifies warp route config / chain metadata / addresses. Canonical pattern — never run the interactive `pnpm changeset` CLI; write the file directly. Referenced by any skill that opens a registry PR.

The English summary is being prepared. Showing the original description.

hyperlane-xyz/hyperlane-monorepo76Updated Oct 23, 2026

Trigger Docker image builds for Hyperlane agent, monorepo, or node service images. Use when the user wants to build new Docker images for a branch, commit, or tag.

The English summary is being prepared. Showing the original description.

hyperlane-xyz/hyperlane-monorepo76Updated Oct 23, 2026

The low-level on-chain probes for identifying what an owner address is — cast code → EOA / EIP-7702-delegated EOA / contract, VERSION() → Gnosis Safe, read-only get-owner-ica.ts derive → ICA derivation, getAccountInfo → Sealevel account existence — with how to interpret each result. The primitive layer beneath validate-owners / resolve-artifacts / update-owners, which each apply their own per-chain or per-artifact policy on top.

The English summary is being prepared. Showing the original description.

hyperlane-xyz/hyperlane-monorepo76Updated Oct 23, 2026

Review code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.

The English summary is being prepared. Showing the original description.

hyperlane-xyz/hyperlane-monorepo76Updated Oct 23, 2026

Debug why a Hyperlane message is not being processed. Use when given a message ID or explorer URL to investigate delivery failures, gas estimation errors, validator issues, or other processing problems.

The English summary is being prepared. Showing the original description.

hyperlane-xyz/hyperlane-monorepo76Updated Oct 23, 2026

Debug RPC provider health issues for a chain. Use when alerts mention RPC failures, high latency, stale blocks, or provider errors. Diagnoses the issue and recommends fixes.

The English summary is being prepared. Showing the original description.

hyperlane-xyz/hyperlane-monorepo76Updated Oct 23, 2026

See all skills by hyperlane-xyz

Report a problem with this skill