evm-atlas

argument-hint	<chain-name-or-id|address|transaction-hash|order-id>
compatibility	Requires the `routemesh` CLI initialized on macOS with `routemesh init` for RouteMesh requests.
coordination	exempt
disable-model-invocation	false
name	evm-atlas
skill-dependencies	["cli-cast"]
user-invocable	true
description	Use for targeted EVM chain, account, transaction, RPC, explorer, bridge, and DEX evidence: chain name/ID, native symbol, RouteMesh, wallet balances via Blockscan in Chromium, token/NFT holdings/transfers, tx history, funding origin via Etherscan/Blockscout/Chainscout; Across, Bungee, deBridge, Hop, Layerswap, LayerZero, LI.FI, Relay, Socket, Symbiosis; Uniswap v1-v4, Universal Router, Permit2, 1inch Classic/Fusion/Fusion+, and CoW Swap, CoWSwap, CoW Protocol, or GPv2 swaps, orders, liquidity, approvals, permits, rewards, migrations, wrapping, cancellations, and refunds.

EVM Atlas

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

Resolve and query only the target mainnets in references/generated/target-mainnets.json, under a strict read-only boundary.

Scope and Authority

• Match displayed names, numeric chain IDs, and aliases from references/generated/chain-aliases.json to the authoritative target-mainnet rows.
• If a chain is absent, do not route through another provider, web search, Chainlist, or an unlisted RPC to work around scope. Ask for a feature request at https://github.com/PaulRBerg/agent-skills.
• Never sign messages, submit signatures, execute bridge steps, or broadcast transactions. Route state-changing Cast work to cli-cast.
• DEX support is historical and evidence-only. Do not discover live quotes, construct or simulate new trades, prepare approvals or permits, submit orders, administer protocols, interpret CoW AMM positions, handle standalone 1inch limit orders, or assign semantics to arbitrary Uniswap v4 hooks.
• Do not default to Ethereum. Infer from explicit chain context and unambiguous chain-specific tokens; ask when ambiguous.
• Never echo, interpolate, or log API-key values (ETHERSCAN_API_KEY, BLOCKSCOUT_API_KEY, RPC keys). Check presence value-free with [ -n "$ETHERSCAN_API_KEY" ] && echo set || echo unset; never put ${VAR:-...} or ${VAR:+...} expansions in printed output.
• Keyless Blockscout is sunset (July 2026) and hosted *.blockscout.com instance subdomains also rate-limit keyless traffic, so route every Blockscout-hosted chain through the keyed https://api.blockscout.com/{chain_id} gateway. See references/explorers/blockscout-endpoints.md.
• An unreachable or erroring indexer is a coverage gap, never evidence of zero activity. Confirm in Chromium before recording an endpoint as down or blocked, and state the verification method in results.

Routing

1. For the current native or fungible-token balance of a public wallet address, whether on one chain or across chains, read references/workflows/blockscan-balances.md first.
2. For a specific transaction hash on a named chain, resolve the chain against references/generated/target-mainnets.json, then read references/workflows/provider-routing.md directly for the transaction facts. Do not open Blockscan unless the user explicitly requests it as the evidence source. When the chain is unknown, read once to resolve it. For an OP Mainnet target known or suspected to predate the final regenesis, read and return its legacy execution packet or component-specific coverage outcome instead of requiring a current-provider receipt. Otherwise, acquire the exact provider receipt and logs before DEX or bridge outcome interpretation.