Agent skill
evm-address-info
Use this skill when the user asks to "check balance", "what's the balance of", "is this a contract or EOA", "get address info", or mentions checking wallet balance or account type on EVM chains (Ethereum, Polygon, Arbitrum, etc.). Requires an address and optional chain parameter.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/evm-address-info
SKILL.md
EVM Address Info Fetcher
Gets address balance and account type (EOA vs Contract) from an EVM blockchain network.
Usage
Run the script with address and optional chain:
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-address-info.sh <address> [chain]
Arguments
address(required): Ethereum address (0x + 40 hex) or ENS namechain(optional): Chain name - ethereum (default), polygon, arbitrum, optimism, base, bsc
Supported Chains
| Chain | Aliases | Explorer |
|---|---|---|
| ethereum | eth, mainnet | Etherscan |
| polygon | matic | Polygonscan |
| arbitrum | arb | Arbiscan |
| optimism | op | Optimism Etherscan |
| base | - | Basescan |
| bsc | binance | BSCScan |
Requirements
cast(Foundry) must be installed- RPC URL is optional (uses PublicNode fallback)
Examples
# Check ENS name balance on Ethereum
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-address-info.sh vitalik.eth
# Check address on Polygon
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-address-info.sh 0x1234...abcd polygon
Note
For Solana account info, use the sol-account-info skill instead.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?