Agent skill
evm-contract-source
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/evm-contract-source
SKILL.md
EVM Contract Source Fetcher
Fetches verified smart contract source code from block explorers (Etherscan, Polygonscan, etc.).
Usage
Run the script with address and optional chain:
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-contract-source.sh <address> [chain]
Arguments
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
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- API key must be set for the target chain:
ETHERSCAN_API_KEYfor Ethereum (also used as fallback for other chains)POLYGONSCAN_API_KEYfor PolygonARBISCAN_API_KEYfor ArbitrumOPTIMISM_API_KEYfor OptimismBASESCAN_API_KEYfor BaseBSCSCAN_API_KEYfor BSC
Examples
# 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
Note
For Solana program IDL, use the sol-program-idl 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?