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.
Retrieves transaction details from EVM chains using transaction hash and optional chain parameter.
npx claudepluginhub cheolwanpark/useful-claude-pluginsThis skill is limited to using the following tools:
Gets transaction details by hash from an EVM blockchain network.
Run the script with transaction hash and optional chain:
${CLAUDE_PLUGIN_ROOT}/scripts/crypto-evm-tx-info.sh <tx_hash> [chain]
tx_hash (required): Transaction hash (0x + 64 hex characters)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 installed# 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
For Solana transaction info, use the sol-tx-info skill instead.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.