warp-fork
Skill76 starsChanged 20 days agoApache-2.0View on GitHub
Fork a warp route using the local HTTP registry. Instructions: Prerequisites: Related skills: 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.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Check if http://localhost:3333 is running.
- Distinctive: line 23
Run the command in the background:
- Very specific: line 29
Use the registry URL from step 0 for $REGISTRY (http://localhost:3333 by default, or user-provided if the local registry failed)
- Very specific: line 30
Use run_in_background: true so it doesn't block the conversation.
- Distinctive: line 32
After starting, report the task/shell ID and the fork registry server port back to the user.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Warp Fork
Fork a warp route using the local HTTP registry.
Instructions:
- Check if
http://localhost:3333is 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 ofhttp://localhost:3333. - 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!
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:3333by default, or user-provided if the local registry failed) - Use
run_in_background: trueso it doesn't block the conversation.
- Use the registry URL from step 0 for $REGISTRY (
- After starting, report the task/shell ID and the fork registry server port back to the user.
- Remind the user they can stop it later with
KillShellusing 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
anvilonPATH; Sealevel chains need a locally-installedsurfpoolbinary (>= 1.5.0) onPATH— there is no Docker fallback in the CLI. Install the pinned, checksum-verifiedsurfpoolrelease the way CI does — see theInstall surfpoolstep in.github/workflows/test-cli-e2e.yml(a pinnedv1.5.0release tarball verified against its SHA-256); do not pipe the mutablerun.surfpool.runinstaller to a shell. If the binary is missing,warp forkaborts 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-megaethin background (shell ID:shell_abc123). To stop it later, I can use KillShell with that ID.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-registry-changesetSkill
- build-docker-imageSkill
- classify-onchain-ownerSkill
- code-reviewSkill
- debug-messageSkill
- debug-rpc-providerSkill
- debug-validator-checkpoint-inconsistencySkill
- denylist-stuck-messagesSkill
- fetch-linear-ticketSkill
- fetch-safe-tx-batchSkill
- find-docker-imageSkill
- fix-merkle-root-mismatchSkill
- fix-rpc-urlsSkill
- gcp-logsSkill
- hyperlane-message-utilsSkill
- hyperlane-utilsSkill
- inline-pr-commentsSkill
- investigate-merkle-root-mismatchSkill
- investigate-stuck-messagesSkill
- registry-yaml-sort-policySkill
- security-reviewSkill
- self-relay-hyperlane-messageSkill
- set-moonpay-standing-quotesSkill
- start-http-registrySkill
- stop-http-registrySkill
- svm-warp-alt-manageSkill
- svm-warp-program-upgradeSkill
- tob-reviewSkill
- verify-warp-contractsSkill
- warp-balancesSkill
- warp-deploy-fund-deployerSkill
- warp-deploy-init-routeSkill
- warp-deploy-nexusSkill
- warp-deploy-register-routeSkill
- warp-deploy-select-keysSkill
- warp-deploy-send-testSkill
- warp-deploy-update-ownersSkill
- warp-deploy-validate-ownersSkill
- warp-key-value-expansionSkill
- warp-manage-offchain-quotesSkill
- warp-route-checkSkill
- warp-run-logSkill
- warp-simulate-svm-txsSkill
- warp-update-extendSkill
- warp-update-proposeSkill
- warp-update-resolve-artifactsSkill
- warp-updateSkill
- warp-verify-onchain-configSkill
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.