Give Agent-to-Agent Deals a Contract and a Court

Agents are starting to transact without humans in the loop, and every protocol they need — payments, identity, negotiation — solves one layer and assumes the happy path. Internet Court is an open skill that connects the fragments and adds the missing piece: adjudication, agreed before the deal, written into the contract itself.

Why This Skill Matters

The README lays the agentic-commerce world out as six layers: discovery and identity (ERC-8004, ERC-7857), negotiation (A2A), contracts and obligations (ERC-7710, ERC-8183, Arkhai), payment and escrow (x402, MPP, APP), execution, and verification and disputes (GenLayer, Kleros, UMA). That sixth layer is the one Internet Court exists to add — most standards pass a gone-wrong deal down the line, while this skill has both sides agree up front on who judges a dispute. The repository is a consortium effort, not a single-vendor product: 28 founding members are named, from GenLayer and MetaMask to OKX, NEAR, and Kleros. Inside you get a master router SKILL.md, Internet Court connector skills, and 91 vendored skills from 33 owners — committed copies of the protocols' own published skills, pinned by hash in skills-lock.json. The repo never re-implements a protocol's skill; first-party work is only the router and the connectors.

Installation

On Claude Code, install the plugin:

# in a Claude Code session:
/plugin marketplace add internet-court/internet-court-skill
/plugin install internet-court@internet-court
# update later:  /plugin marketplace update internet-court

Other harnesses take the same repo different ways — npx skills add internet-court/internet-court-skill, a clone into ~/.agents/skills/internet-court for Codex, or openclaw skills install git:internet-court/internet-court-skill for OpenClaw. Only the root SKILL.md is registered and triggered; it routes to the sub-skills and pulls them in on demand — from disk when the whole repo is installed, otherwise fetched from the raw GitHub URL, so even a root-only install works.

Real Workflow: Structure a Data Purchase

1. After installing, say "Install the Internet Court skill" in chat — the README's documented way to get the guided introduction.
2. Give the agent a deal to structure in natural language:

我要向另一个 agent 买一份数据集：用 x402 付款，如果交付出问题，争议交给 Kleros 裁决。帮我把这份合同的结构写出来。

3. The master skill routes to the vendored sub-skills the deal needs — an x402 payment skill and the Kleros skills — pulling each into context on demand, and drafts the contract with the adjudication choice baked in.
4. Mind the credentials: some vendored skills act only with their provider's keys (the README names OKX, ChainGPT, and Chainbase API keys), and each skill documents its own requirements.

Most deals never reach the dispute path — when both sides agree, the contract simply settles. What the skill standardizes is the structure around that choice, for the deals that fall off the happy path.

Tips

• Installing the whole repository, not just the root skill, bundles every sub-skill for offline use; root-only installs fall back to on-demand fetching.
• Three standards in the stack have no public skill yet — ERC-7857, ERC-8183, and UMA — so coverage there stops at the README's own note.
• The table in the README maps each layer to its vendored skills; treat it as the inventory when you want to know what a deal can actually route through.
• Codex scans recursively and will surface bundled sub-skills as separate entries — the root skill is the intended entry point.

When Not to Use This

The stack touches real money: payment and escrow skills move funds on-chain, and provider credentials unlock the ones that act. If your agents only exchange work inside one platform's own tooling, six layers of commerce protocol is overhead. And if you need one of the three not-yet-skilled standards specifically, nothing in this repo substitutes for it yet.

See the leaderboard for more skills.