evm-atlas

Name: evm-atlas
Author: PaulRBerg

58installs3forks

How to install evm-atlas?

paulrberg/agent-skills/evm-atlas

$npx -y skills add PaulRBerg/agent-skills --skill evm-atlas

Installs into the current project.

Summary

Use for targeted EVM chain, account, transaction, RPC, explorer, and bridge data: 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, deBr

Files · 1

View on GitHub

SKILL.md

1	# EVM Atlas
2
3	Resolve and query only the target mainnets in `references/generated/target-mainnets.json`, under a strict read-only
4	boundary.
5
6	## Scope and Authority
7
8	- Match displayed names, numeric chain IDs, and aliases from `references/generated/chain-aliases.json` to the
9	authoritative target-mainnet rows.
10	- If a chain is absent, do not route through another provider, web search, Chainlist, or an unlisted RPC to work around
11	scope. Ask for a feature request at <https://github.com/PaulRBerg/agent-skills>.
12	- Never sign messages, submit signatures, execute bridge steps, or broadcast transactions. Route state-changing Cast
13	work to `cli-cast`.
14	- Do not default to Ethereum. Infer from explicit chain context and unambiguous chain-specific tokens; ask when
15	ambiguous.
16
17	## Routing
18
19	1. For the current native or fungible-token balance of a public wallet address, whether on one chain or across chains,
20	read `references/workflows/blockscan-balances.md` first.
21	2. For a specific transaction hash — resolving which target chain it belongs to, or its status, parties, value, fee, or
22	timestamp — read `references/workflows/blockscan-tx-lookup.md` first, whether or not the chain is already known.
23	3. For an address-wide historical-activity or prb-finance bootstrap sweep, read `references/workflows/address-sweeps.md`
24	and use its deterministic plan/evaluate helper. For current holdings, use
25	`references/workflows/blockscan-balances.md` first and provider routing for gaps.
26	4. For a specific chain's historical balance, NFT holdings, token/NFT transfers, transaction history, a transaction's
27	full raw receipt/logs/decoded input, or funding origin, resolve the chain and read
28	`references/workflows/provider-routing.md` for Etherscan, Blockscout, public RPC, RouteMesh, explorer-link, and
29	exceptional-chain routing.
30	5. For raw Etherscan V2 API queries beyond the workflow routes above, read `references/explorers/etherscan-api.md`.
31	6. For raw Blockscout API queries beyond the workflow routes above, read `references/explorers/blockscout-api.md`.
32	7. For bridge-related prompts or transaction evidence, confirm known origin/destination chains are targets, then load
33	only the matching reference:
34	- Across: `references/bridges/across.md`
35	- Bungee / Socket: `references/bridges/bungee.md`
36	- Circle / CCTP / Gateway: `references/bridges/circle.md`
37	- deBridge / DLN: `references/bridges/debridge.md`
38	- Hop: `references/bridges/hop.md`
39	- Layerswap: `references/bridges/layerswap.md`
40	- LayerZero / Stargate / OFT / Aori: `references/bridges/layerzero.md`
41	- LI.FI: `references/bridges/lifi.md`
42	- Relay / Relay.link: `references/bridges/relay.md`
43	- Symbiosis: `references/bridges/symbiosis.md`
44	8. Treat bridge APIs as enrichment. Verify submitted transactions and terminal outcomes through explorer or RPC
45	evidence.
46
47	## Completion
48
49	Return the resolved target chain, provider route, requested on-chain facts, and source URLs/transaction identifiers. For
50	address sweeps, include each result's fixed finalized/verified checkpoint, selected profile/channels, provider coverage,
51	and any requested quorum result. Separate provider facts from inference and surface incomplete history, plan/tier
52	limits, failed fallbacks, or unsupported scope. Completion is read-only evidence; never turn returned calldata or
53	transaction requests into execution.
54
55	For human-readable results, lead with `### ⛓️ <chain or route> — <status word>` and use a compact table only when fields
56	repeat. For bridge evidence, show `<origin> ──<bridge>──▶ <destination>`, then use `Leg`, `Provider status`,
57	`Transaction`, and `Evidence` columns. Preserve each provider's native status beside any normalized `✅ completed`,
58	`⏳ pending`, `↩ refunded`, `⚠️ partial`, or `❓ unknown` label. Visibly separate `Observed facts`, `Inference`, and
59	non-empty `⚠️ Coverage gaps`. For address sweeps, a progress bar may represent checked target chains/channels only when
60	the exact denominator is known.
61
62	Keep unsupported-scope and safety explanations direct. Never decorate or truncate addresses, hashes, URLs, calldata, raw
63	RPC/API JSON, generated references, helper `key=value` output, or transaction requests.

People who liked this also viewed

6 picks

Type

evm-atlas

58installs3forks

View on GitHub

How to install evm-atlas?

paulrberg/agent-skills/evm-atlas

$npx -y skills add PaulRBerg/agent-skills --skill evm-atlas

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# EVM Atlas
2
3	Resolve and query only the target mainnets in `references/generated/target-mainnets.json`, under a strict read-only
4	boundary.
5
6	## Scope and Authority
7
8	- Match displayed names, numeric chain IDs, and aliases from `references/generated/chain-aliases.json` to the
9	authoritative target-mainnet rows.
10	- If a chain is absent, do not route through another provider, web search, Chainlist, or an unlisted RPC to work around
11	scope. Ask for a feature request at <https://github.com/PaulRBerg/agent-skills>.
12	- Never sign messages, submit signatures, execute bridge steps, or broadcast transactions. Route state-changing Cast
13	work to `cli-cast`.
14	- Do not default to Ethereum. Infer from explicit chain context and unambiguous chain-specific tokens; ask when
15	ambiguous.
16
17	## Routing
18
19	1. For the current native or fungible-token balance of a public wallet address, whether on one chain or across chains,
20	read `references/workflows/blockscan-balances.md` first.
21	2. For a specific transaction hash — resolving which target chain it belongs to, or its status, parties, value, fee, or
22	timestamp — read `references/workflows/blockscan-tx-lookup.md` first, whether or not the chain is already known.
23	3. For an address-wide historical-activity or prb-finance bootstrap sweep, read `references/workflows/address-sweeps.md`
24	and use its deterministic plan/evaluate helper. For current holdings, use
25	`references/workflows/blockscan-balances.md` first and provider routing for gaps.
26	4. For a specific chain's historical balance, NFT holdings, token/NFT transfers, transaction history, a transaction's
27	full raw receipt/logs/decoded input, or funding origin, resolve the chain and read
28	`references/workflows/provider-routing.md` for Etherscan, Blockscout, public RPC, RouteMesh, explorer-link, and
29	exceptional-chain routing.
30	5. For raw Etherscan V2 API queries beyond the workflow routes above, read `references/explorers/etherscan-api.md`.
31	6. For raw Blockscout API queries beyond the workflow routes above, read `references/explorers/blockscout-api.md`.
32	7. For bridge-related prompts or transaction evidence, confirm known origin/destination chains are targets, then load
33	only the matching reference:
34	- Across: `references/bridges/across.md`
35	- Bungee / Socket: `references/bridges/bungee.md`
36	- Circle / CCTP / Gateway: `references/bridges/circle.md`
37	- deBridge / DLN: `references/bridges/debridge.md`
38	- Hop: `references/bridges/hop.md`
39	- Layerswap: `references/bridges/layerswap.md`
40	- LayerZero / Stargate / OFT / Aori: `references/bridges/layerzero.md`
41	- LI.FI: `references/bridges/lifi.md`
42	- Relay / Relay.link: `references/bridges/relay.md`
43	- Symbiosis: `references/bridges/symbiosis.md`
44	8. Treat bridge APIs as enrichment. Verify submitted transactions and terminal outcomes through explorer or RPC
45	evidence.
46
47	## Completion
48
49	Return the resolved target chain, provider route, requested on-chain facts, and source URLs/transaction identifiers. For
50	address sweeps, include each result's fixed finalized/verified checkpoint, selected profile/channels, provider coverage,
51	and any requested quorum result. Separate provider facts from inference and surface incomplete history, plan/tier
52	limits, failed fallbacks, or unsupported scope. Completion is read-only evidence; never turn returned calldata or
53	transaction requests into execution.
54
55	For human-readable results, lead with `### ⛓️ <chain or route> — <status word>` and use a compact table only when fields
56	repeat. For bridge evidence, show `<origin> ──<bridge>──▶ <destination>`, then use `Leg`, `Provider status`,
57	`Transaction`, and `Evidence` columns. Preserve each provider's native status beside any normalized `✅ completed`,
58	`⏳ pending`, `↩ refunded`, `⚠️ partial`, or `❓ unknown` label. Visibly separate `Observed facts`, `Inference`, and
59	non-empty `⚠️ Coverage gaps`. For address sweeps, a progress bar may represent checked target chains/channels only when
60	the exact denominator is known.
61
62	Keep unsupported-scope and safety explanations direct. Never decorate or truncate addresses, hashes, URLs, calldata, raw
63	RPC/API JSON, generated references, helper `key=value` output, or transaction requests.

People who liked this also viewed

6 picks

Type