# Yellow Settlement Room

Yellow Network Protocol app sessions for AI agents - a shared room where several agents...

- Repository: https://github.com/internet-court/internet-court-skill (7050 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add internet-court/internet-court-skill --skill yellow-settlement-room -g -a claude-code -y`
Codex: `npx skills add internet-court/internet-court-skill --skill yellow-settlement-room -g -a codex -y`
Cursor: `npx skills add internet-court/internet-court-skill --skill yellow-settlement-room -g -a cursor -y`
Gemini CLI: `npx skills add internet-court/internet-court-skill --skill yellow-settlement-room -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add internet-court/internet-court-skill`

## Description

Yellow Network Protocol app sessions for AI agents - a shared room where several agents pool funds, reallocate off-chain at machine speed, and settle one final split. Use for multiparty settlement among agents. Covers connecting, the funded-account prerequisite, creating a session with participants + weights + quorum, deposit, operate, withdraw, close, and the trust boundary. Grounded in the official @yellow-org/sdk lifecycle example.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Yellow Settlement Room

Use this skill when several AI agents need to hold funds together and settle one outcome: open a shared session, each agent's balance is tracked inside it, they reallocate between themselves off-chain with no gas per step, and they co-sign the final split.

**The session holds N agents, not two.** A payment rail moves value from one payer to one payee; a swarm of agents settling over a rail needs a separate escrow per pair. One session settles all of them at once: one object, one deposit per agent, one final allocation. That is the shape to reach for when more than two agents have a stake in the same outcome.

This skill covers the **app-session (virtual) layer** only. It operates on funds that are *already in an account balance at Yellow*. A session opens with zero allocations, so not every participant needs funds - only a participant that makes a deposit does. Getting funds into an account is a one-time on-chain step, out of scope here - see `## Prerequisite`. This skill never funds accounts; before a participant deposits, check its balance with `client.getBalances(wallet)`, and if it is short, stop and report it.

Package: `@yellow-org/sdk` (v1). A complete runnable reference is the official example at `github.com/layer-3/docs`, `examples/nitrolite-v1-lifecycle`; the flow below matches it exactly, generalised from two participants to N. For method lookups, the docs MCP: `npx -y @yellow-org/sdk-mcp@^1`.

## Core Model

```text
Each agent runs its own client with its own key (backend: private-key based)
  -> agents open one app session: N participants, signature weights, quorum
     (opens with ZERO allocations; nobody needs funds yet)
  -> a depositing agent commits its OWN funds into the session
     (only depositors need a funded account; others can hold zero)
  -> agents reallocate between themselves (operate), each update co-signed to quorum
  -> withdraw / close: the final split releases back to channels, withdrawable on-chain
```

The rest: https://github.com/internet-court/internet-court-skill/blob/HEAD/vendored/yellow/yellow-settlement-room/SKILL.md