skills/taiko-node/SKILL.md
Set up, run, and manage Taiko nodes on Hoodi testnet or mainnet using Docker or from source. Use when "run node", "node operator", "simple-taiko-node", "taiko-geth", "taiko-client", or "sync" is mentioned.
npx skillsauth add taikoxyz/taiko-ai taiko-nodeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Run Taiko nodes. A node = taiko-geth (execution) + taiko-client (consensus).
Network Selection: Always ask which network if user hasn't specified "hoodi" or "mainnet".
| Task | Resource | |------|----------| | Network config, chain IDs, RPCs | Networks Reference | | Run node (Docker, recommended) | Docker setup | | Build from source | Source build | | Run Ethereum Hoodi L1 | eth-docker | | Debug issues | Troubleshooting |
^24.0, git ^2 (source: also Go ^1.21, make ^4)git clone https://github.com/taikoxyz/simple-taiko-node.git && cd simple-taiko-node
cp .env.sample .env # mainnet (.env.sample.hoodi for testnet)
# Edit .env: set L1_ENDPOINT_WS, L1_BEACON_HTTP, COMPOSE_PROFILES
docker compose up -d # mainnet
docker compose -f docker-compose-hoodi.yml up -d # testnet
L1 endpoints: Use host.docker.internal or machine's private IP, not 127.0.0.1.
Use taiko --json for structured output:
taiko node status --json # health: block, peers, sync %, L1 anchor
taiko node logs --service taiko_client_driver --tail 50 # taiko-client logs
taiko node logs --service l2_execution_engine --tail 50 # taiko-geth logs
taiko node restart --json # restart with structured confirmation
All commands return: { schema_version, command, status, network, data, errors, warnings, metrics }
development
Deploy, test, and interact with smart contracts on Taiko networks (Type-1 ZK-EVM rollup on Ethereum). Use when "Taiko", "Hoodi", "L2 deployment", "bridge", "forge", or "Taikoscan" is mentioned. For x402 payment APIs use the taiko-x402 skill instead.
tools
Build and integrate x402 HTTP payment flows on Taiko using Taiko-operated facilitators. Use when adding per-request USDC payment gating to APIs deployed on Taiko (seller), building AI agents or clients that autonomously pay for x402 services (buyer), or configuring Taiko facilitators. Triggers: "x402", "HTTP payment", "pay per request", "monetize API", "USDC payment", "402 Payment Required", "facilitator.taiko.xyz", "paid API", "AI agent payments", "payment middleware".
tools
Use when performing private or anonymous ETH transfers on Taiko. Covers deposit creation, target address funding, ZK proof generation, and on-chain claiming via REST API or CLI.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.