skilld
All skills
paulrberg avatar

/evm-atlas

@592682c
by Paul Bergpaulrberg/agent-skills94 stars
7

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/paulrberg/agent-skills/evm-atlas

This session only. Nothing lands on disk.

referencesbridgeslayerzero.md

≈1.1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

LayerZero Bridging

Overview

Use LayerZero as a read-only source for bridge route discovery, supported-token discovery, and deployment metadata on target chains. This reference covers unauthenticated LayerZero Value Transfer API (VTA) discovery endpoints only.

Default to the VTA base URL:

https://transfer.layerzero-api.com/v1

Do not use authenticated VTA transfer endpoints from this skill. Do not request API keys, build user steps, submit signatures, approve spenders, or broadcast transactions. If the user provides transaction hashes or LayerZeroScan links, verify them with explorer/RPC data instead.

Legacy Stargate API

The Stargate API at https://stargate.finance/api/v1 is deprecated in favor of LayerZero VTA. Use Stargate docs only as legacy context when analyzing older integrations or URLs.

Legacy discovery endpoints:

Endpoint Use
GET /chains List legacy Stargate chain keys and chain IDs
GET /tokens List legacy Stargate bridgeable tokens

Do not prefer legacy Stargate endpoints for new data unless the user specifically asks about Stargate API behavior.

Read-Only Router

Use this router after the known origin and destination chains are confirmed against references/generated/target-mainnets.json.

  1. Supported chains: call GET /chains.
  2. Supported tokens or destinations: call GET /tokens. Use transferrableFromChainKey and transferrableFromTokenAddress together to find valid destination tokens from a source token.
  3. Deployment metadata: call GET /metadata when contract addresses or deployment details matter.
  4. Known transaction hash or LayerZeroScan link: verify the referenced transaction on-chain with explorer/RPC data.

Example discovery:

curl -sS "https://transfer.layerzero-api.com/v1/chains"
curl -sS "https://transfer.layerzero-api.com/v1/tokens?transferrableFromChainKey=base&transferrableFromTokenAddress=0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE"
curl -sS "https://transfer.layerzero-api.com/v1/metadata?chainKey=base"

Report Fields

Extract and report these fields when present:

Field VTA path examples
Chain identity chains[].chainKey, chains[].chainId, chains[].chainType
Token identity tokens[].chainKey, tokens[].address, symbol, decimals
Token routes tokens[].transferableTo[], token route metadata
Deployments metadata contract addresses and deployment labels

Token amounts, if present in supplied external data, are raw integer units. Convert with token decimals when present, and preserve raw values when decimals are absent.

Route Types

Common LayerZero route types and integrations to recognize in logs, explorer labels, or supplied payloads:

Type Meaning
OFT Omnichain Fungible Token route
STARGATE_V2_TAXI Stargate V2 instant route
STARGATE_V2_BUS Stargate V2 batched route
CCTP Circle native USDC burn/mint
AORI Intent-based route through Aori

Failure Handling

  • Empty discovery results: report the missing chain, token, or deployment metadata; do not infer bridge support from token symbols alone.
  • Rate limits and 5xx responses: report the API limitation and continue normal explorer/RPC analysis.
  • Non-target chains in VTA results: report that the leg is outside this skill and ask for a feature request rather than continuing analysis on that leg.

Sources

Source: SKILL.md on GitHub

Third-party checks

No alerts1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The skill is a comprehensive toolkit for exploring EVM blockchain data across multiple networks, bridges, and DEXes. It utilizes local shell and Python scripts to process API responses from well-known cryptocurrency services like Etherscan and Blockscout. While the skill possesses an attack surface for indirect prompt injection via the processing of externally controlled blockchain data, it includes robust instructions and deterministic logic to mitigate these risks.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: LOW · No issues

Provenance

Signed by skilld at 592682c. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago

Capability

argument-hint
<chain-name-or-id|address|transaction-hash|order-id>
coordination
exempt
skill-dependencies
[
  "chromium-browser",
  "cli-cast"
]
Other metadata
compatibility
Requires the `routemesh` CLI initialized on macOS with `routemesh init` for RouteMesh requests.

README badge

README badge for paulrberg/agent-skills/evm-atlas