cli-cast

Foundry Cast CLI

This skill is coordination-exempt: skip the ai-coord gate for its declared work.

Separate read, preparation, simulation, signing, and broadcast. Do not hide state-changing actions inside command construction.

For EIP-7702 authorization or delegation revocation, read references/eip7702.md before preparation. It defines signer selection, authority versus transaction sender, and conditional staged approval. It also defines authorization verification in addition to the transaction receipt.

Resolve Chain and Provider

Invoke $evm-atlas before every network operation. It owns chain resolution, discrete reads, and bounded live subscriptions. Pass the explicit chain name or ID, JSON-RPC method, exact parameters or call object, and block selector or checkpoint requirement. State why you need the result. Require its read packet containing the resolved chain name and ID, provider route, result, observed block or checkpoint, and coverage gaps.

If the chain is absent from evm-atlas, stop RPC-dependent work. Do not accept an arbitrary RPC URL to bypass that restriction. When the chain is ambiguous, never infer Ethereum.

Use an RPC URL in this skill only for a trace, fork, or send flow you cannot express as bounded discrete reads. For RouteMesh-backed continuous transport, first require evm-atlas to confirm current RouteMesh coverage. Then, if the explicit Foundry alias is configured, use it:

ROUTEMESH_CHAIN_ID="$CHAIN_ID" cast COMMAND --rpc-url routemesh

The alias can interpolate an environment variable, such as ROUTEMESH_API_KEY. The routemesh CLI keeps its own key. Thus, successful atlas reads do not prove that the alias resolves. Before you sign a transaction for alias broadcast, or use the alias in another way, run ROUTEMESH_CHAIN_ID="$CHAIN_ID" cast chain-id --rpc-url routemesh 2>/dev/null. Require the expected chain ID. If the check fails, load the missing variable from the user's environment setup without printing it. If you cannot load it, treat the alias as not configured.