Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From crypto
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/crypto:evm-address-infoThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gets address balance and account type (EOA vs Contract) from an EVM blockchain network.
Gets address balance and account type (EOA vs Contract) from an EVM blockchain network.
Run the script with address and optional chain:
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-address-info.sh <address> [chain]
address (required): Ethereum address (0x + 40 hex) or ENS namechain (optional): Chain name - ethereum (default), polygon, arbitrum, optimism, base, bsc| Chain | Aliases | Explorer |
|---|---|---|
| ethereum | eth, mainnet | Etherscan |
| polygon | matic | Polygonscan |
| arbitrum | arb | Arbiscan |
| optimism | op | Optimism Etherscan |
| base | - | Basescan |
| bsc | binance | BSCScan |
cast (Foundry) must be installed# 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
For Solana account info, use the sol-account-info skill instead.
npx claudepluginhub cheolwanpark/claude-plugins --plugin cryptoGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.