A wright is a maker — a shipwright builds ships, a playwright builds plays. A rpcwright builds (and proves) Ethereum JSON-RPC.
rpcwright is an agent skill that teaches an AI agent how to implement and conformance-test a change to the Ethereum execution-layer JSON-RPC API — across the four repos that have to agree:
| repo | role |
|---|---|
| the client (go-ethereum, Nethermind, Besu, Erigon, Reth, ethrex, Nimbus) | implements the method |
| execution-apis | the OpenRPC spec (the contract) |
| testgen / rpctestgen | generates .io fixtures from a real client |
hive (rpc-compat) |
replays fixtures against every client |
The one-line behavior change is easy. The hard part is the build/test plumbing and the dozen places a silent failure hides — a green hive run that executed zero tests, a fixture that passes validation only because the param was still "required", a harness quietly testing the upstream image instead of your change. This skill encodes the exact commands and those gotchas so future sessions don't rediscover them the slow way.
SKILL.md: scope, reference selection, workflow, and validation requirements.references/go-ethereum.md— build, test, RPC method & optional-parameter patterns, in-process RPC test harness.references/execution-apis.md— OpenRPC YAML,specgen/openrpc.json,speccheck, and therequiredsemantics.references/testgen.md—rpctestgen,make fill, the.ioformat, generating fixtures with a local client, determinism.references/hive.md— therpc-compatsimulator, local fixtures, building clients from source, client-files, the--sim.limittrap, reading results.references/clients.md: handler locations, registration, build examples, and contribution checks for six clients.references/hivechain.md: chain generation, fork configuration, and special-purpose chains.references/tracers.md: named-tracer schemas and validation.references/trace-namespace.md: thetrace_*draft spec, decision ledger, and cross-client evidence (work in progress).references/gotchas.md— the full catalog.
Claude Code and Codex both read the same format — a directory with a SKILL.md —
so one copy serves both. Only the directory each one scans differs:
| tool | personal scope | repo scope | explicit call |
|---|---|---|---|
| Claude Code | ~/.claude/skills/ |
.claude/skills/ |
/rpcwright |
| Codex | ~/.agents/skills/ |
.agents/skills/ |
$rpcwright, or /skills |
/plugin marketplace add MysticRyuujin/rpcwright
/plugin install rpcwright@rpcwright
Clone once, then symlink it into the tools you use. Both follow a symlinked skill
directory, so a single git pull updates every tool:
git clone https://github.com/MysticRyuujin/rpcwright.git
mkdir -p ~/.claude/skills ~/.agents/skills
ln -s "$PWD/rpcwright" ~/.claude/skills/rpcwright # Claude Code
ln -s "$PWD/rpcwright" ~/.agents/skills/rpcwright # CodexEither tool discovers the skill from its SKILL.md frontmatter and loads it when a
task involves the Ethereum JSON-RPC API, execution-apis, rpctestgen/testgen,
.io fixtures, speccheck, openrpc.json, or hive rpc-compat.
AGENTS.md, CLAUDE.md, and llms.txt are symlinks to SKILL.md, so a repo that
vendors rpcwright at its root also picks it up as plain project instructions.
The skill covers changes and reviews across six execution clients, execution-apis, testgen, and Hive. Use only the stages required by the task. Confirm paths, toolchain pins, and historical observations against the selected revisions.
MIT — see LICENSE.