EVM Crypto Wallet for Your Agent

**Judgement:** A powerful, self-sovereign EVM wallet skill with broad on-chain capabilities and good safety guidance, suitable for serious crypto-enabled agents but inherently high-risk due to irreversible blockchain operations and local key custody. **What it does well** - Implements a full wallet stack: create wallet, check balances (single-chain, all-chains, specific ERC20), send native and ERC20 tokens, swap tokens via Odos, and perform generic contract reads/writes. - Operates self-custodially: private key is stored locally (`~/.evm-wallet.json`, `chmod 600`), avoiding third-party custody or API-key based wallet providers. - Provides clear operational patterns for agents: always use `--json` for parsing, obtain quotes before swaps, and require explicit user confirmation (with details on recipient, amount, chain, gas) before including `--yes` for any state-changing transaction. - Supports multiple major EVM chains (Base, Ethereum, Polygon, Arbitrum, Optimism) and includes chain recommendations (Base for low-fee testing) and common token addresses for convenience. - Includes error-handling guidance (missing wallet, insufficient balance, RPC issues, no swap route, gas estimation failures) to help the agent recover gracefully or give actionable feedback. **Key risks & limitations** - **Irreversible loss risk:** Any mistake in recipient address, chain selection, token amount, or contract call is permanent once broadcast. Bugs in the agent’s reasoning or parsing could cause financial loss. - **Local key security:** The private key file is unencrypted on disk (albeit permission-restricted). Host compromise, misconfigured file permissions, or backups/logging that capture the file can leak the key. - **User error / social engineering:** Despite strong warnings, users might still paste or expose their private key or wallet file contents. Agents using this skill must never request or display the private key. - **External protocol dependencies:** Swaps rely on the Odos aggregator and underlying RPC endpoints; downtime or degraded performance there will affect reliability and speed. - **Environment assumptions:** Requires a Unix-like environment with Node.js, npm, git, and shell access, plus the ability to write to the user’s home directory. Not suitable for extremely locked-down or ephemeral runtime contexts. **Recommended scenarios** - Long-lived, reasonably secure agent environments where local disk and OS permissions can be controlled (e.g., self-hosted servers, developer workstations, or well-managed cloud VMs). - Agents that need to **actively manage on-chain funds**: pay addresses, manage simple treasuries, perform swaps, or interact with DeFi protocols via contract calls. - Power users and developers who understand EVM risks and want an agent to assist with on-chain operations while retaining full custody of keys. **Not ideal for** - Casual end-users unfamiliar with crypto risk, unless the agent adds substantial guardrails and explanations. - Highly regulated or enterprise settings that require hardware security modules, multisig, or custodial services. - Highly transient or restricted environments where persisting `~/.evm-wallet.json` securely is not feasible.