Agent skill
evm-tx-info
Use this skill when the user asks for "transaction details", "show me tx", "what happened in this transaction", "look up transaction", or mentions viewing transaction data on EVM chains (Ethereum, Polygon, Arbitrum, etc.). Requires a transaction hash 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-tx-info
SKILL.md
EVM Transaction Info Fetcher
Gets transaction details by hash from an EVM blockchain network.
Usage
Run the script with transaction hash and optional chain:
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-tx-info.sh <tx_hash> [chain]
Arguments
tx_hash(required): Transaction hash (0x + 64 hex characters)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- RPC URL is optional (uses PublicNode fallback)
Examples
# Get transaction on Ethereum
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-tx-info.sh 0x1234...abcd
# Get transaction on Polygon
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-tx-info.sh 0x5678...efgh polygon
Note
For Solana transaction info, use the sol-tx-info skill instead.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
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?