From crypto
Use this skill when the user asks to "get contract source code", "show verified contract", "fetch source from etherscan", "view smart contract code", or mentions viewing verified source code on EVM chains (Ethereum, Polygon, Arbitrum, etc.). Requires a contract address and optional chain parameter.
How this skill is triggered — by the user, by Claude, or both
Slash command
/crypto:evm-contract-sourceThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fetches verified smart contract source code from block explorers (Etherscan, Polygonscan, etc.).
Fetches verified smart contract source code from block explorers (Etherscan, Polygonscan, etc.).
Run the script with address and optional chain:
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-contract-source.sh <address> [chain]
address (required): Contract address in hex format (0x + 40 hex characters). ENS names are NOT supported.chain (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 installedETHERSCAN_API_KEY for Ethereum (also used as fallback for other chains)POLYGONSCAN_API_KEY for PolygonARBISCAN_API_KEY for ArbitrumOPTIMISM_API_KEY for OptimismBASESCAN_API_KEY for BaseBSCSCAN_API_KEY for BSC# Get WETH source on Ethereum
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-contract-source.sh 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2
# Get QuickSwap Router source on Polygon
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-contract-source.sh 0xa5E0829CaCEd8fFDD4De3c43696c57F7D7A678ff polygon
For Solana program IDL, use the sol-program-idl 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.