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 "block info", "what's in block", "latest block", "get block details", or mentions viewing block data on EVM chains (Ethereum, Polygon, Arbitrum, etc.). Optional block number/tag and chain parameter.
How this skill is triggered — by the user, by Claude, or both
Slash command
/crypto:evm-block-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 block information from an EVM blockchain network.
Gets block information from an EVM blockchain network.
Run the script with optional block and chain:
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-block-info.sh [block] [chain]
block (optional): Block number, hex, or tag (latest, pending, earliest, finalized, safe). Default: latestchain (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# Get latest block on Ethereum
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-block-info.sh
# Get specific block on Polygon
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-block-info.sh 50000000 polygon
For Solana slot/block info, use the sol-slot-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.