syjcnss/web3_skills · Archived

trace-tx

Fetches the full execution trace of an EVM transaction using debug_traceTransaction API. Use this skill whenever the user wants to trace a transaction, inspect internal calls, debug a failed tx, check sub-calls or revert reasons, analyze gas usage per call, understand what a transaction actually did on-chain, or investigate MEV / sandwich attacks. Trigger even if the user just says things like "trace this tx", "what did this transaction do?", "why did this tx revert?", "show me the call tree", …

First seen Jun 25, 2026

Installation

$ npx skills add syjcnss/web3_skills --skill trace-tx

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from syjcnss/web3_skills.

npx skills add syjcnss/web3_skills

Browse all from syjcnss/web3_skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch master
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,006 B
  • docs SUMMARY.md 553 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

trace-tx

Fetches the full execution trace for an EVM transaction via debug_traceTransaction. The trace reveals the complete call tree: every internal CALL/DELEGATECALL/CREATE, gas consumed at each step, input/output data, and any revert reasons.

Usage

~/.claude/skills/trace-tx/scripts/trace_tx.sh [-o <output_file>] <TX_HASH> <RPC_URL> [TRACER] [onlyTopCall]
  • Use the RPC URL the user supplied.
  • Or if ALCHEMYAPIKEY is set, construct the Alchemy URL: https://<chain-slug>.g.alchemy.com/v2/$ALCHEMYAPIKEY and use it as the RPC URL. Common slugs: "Ethereum"/"ETH" → eth-mainnet, "Arbitrum"/"Arb" → arb-mainnet, "Base" → base-mainnet, "Optimism"/"OP" → opt-mainnet, "Polygon"/"MATIC" → polygon-mainnet, "BSC"/"BNB Chain" → bnb-mainnet, "Sepolia" → eth-sepolia. Find full slug list in references/rpc_urls.md only when necessary.
  • If neither is available, find an RPC URL that supports debug_traceTransaction for the specific tx.
  • Default tracer: callTracer (nested call tree — best for most tasks). Also supports prestateTracer and raw opcode trace.

Workflow

Use -o to write the trace to a file — traces can be megabytes:

~/.claude/skills/trace-tx/scripts/trace_tx.sh -o trace_0xabc123.json 0xabc... https://your-rpc-url

Tell the user the path to the saved file.

Reference

  • Full RPC URL list: references/rpc_urls.md