nla-arbitrate
Manually arbitrate NLA escrow fulfillments as an alternative to the automated oracle. Use when the user wants to review pending arbitration requests, evaluate demands against fulfillments, and submit on-chain decisions. Supports both interactive and LLM-auto modes.
git clone --depth 1 https://github.com/internet-court/internet-court-skill /tmp/nla-arbitrate && cp -r /tmp/nla-arbitrate/vendored/arkhai/nla-arbitrate ~/.claude/skills/nla-arbitrateSKILL.md
# Manual NLA Arbitration Manually arbitrate escrow fulfillments using the `nla escrow:arbitrate` CLI command, bypassing the automated oracle listener. ## When to use this - The user wants to manually review and decide on escrow fulfillments - The user is the oracle (their wallet address was specified as the oracle when escrows were created) - The automated oracle is not running, or the user wants more control over decisions ## Step-by-step instructions ### 1. Verify oracle identity The user's wallet must be the oracle address specified in the escrow: ```bash nla wallet:show ``` ### 2a. Arbitrate a specific escrow To review fulfillments for a known escrow UID: ```bash # Interactive mode - prompts for approve/reject nla escrow:arbitrate --escrow-uid <uid> # Auto mode - uses the LLM specified in the escrow's demand nla escrow:arbitrate --escrow-uid <uid> --auto ``` ### 2b. Scan for all pending requests To find all unarbitrated fulfillments where the user is the oracle: ```bash # Interactive mode nla escrow:arbitrate --escrow-uid all # Auto mode nla escrow:arbitrate --escrow-uid all --auto ``` ### 3. Review and decide In **interactive mode**, the command displays each pending fulfillment with: - Escrow UID and fulfillment UID - The demand text - The fulfillment text - The arbitration provider/model specified Then prompts for a decision: `approve`, `reject`, or `skip`. In **auto mode** (`--auto`), the command uses the LLM provider/model specified in the escrow's demand to arbitrate automatically. Requires at least one LLM API key via environment variables or flags (`--openai-api-key`, `--anthropic-api-key`, `--openrouter-api-key`). ### 4. Verify After arbitration, check the result: ```bash nla escrow:status --escrow-uid <escrow_uid> ``` ## Key details - The user's wallet address MUST match the oracle address in the escrow - otherwise the on-chain contract rejects the decision - Each arbitration decision is recorded as a permanent on-chain attestation - In interactive mode, type `skip` or `s` to skip a fulfillment without deciding - Auto mode reads LLM API keys from environment variables (OPENAI_API_KEY, etc.) or CLI flags - If no pending requests are found, the command explains possible reasons (no fulfillments yet, already arbitrated, or wrong oracle address) ## Prerequisites - `nla` CLI installed and configured - Private key set via `nla wallet:set`, `--private-key` flag, or `PRIVATE_KEY` env var - ETH in the oracle's account for gas (submitting decisions costs gas) - For auto mode: at least one LLM provider API key ## Examples ```bash # Scan for all pending requests, decide interactively nla escrow:arbitrate --escrow-uid all # Auto-arbitrate a specific escrow using LLM nla escrow:arbitrate --escrow-uid 0xabc123... --auto # Auto-arbitrate all pending, with explicit API key nla escrow:arbitrate --escrow-uid all --auto --openai-api-key sk-... ```
Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use whenever an agent needs to transact with another agent or a paid service, or a user mentions agent payments, paid APIs (HTTP 402/x402), wallet custody or trust concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow, agent identity or reputation (ERC-8004), negotiation between agents (A2A), agent jobs (ERC-8183), machine payments (MPP, AP2), supervision of agent behavior, revocation, verification, or dispute resolution (GenLayer) — even if they never say "Internet Court". Routes to the vendored protocol skills and connector skills in this package.
Connect GenLayer Intelligent Contract decisions to ERC-7710-style delegated authority. Use when an agent needs to design the interface, message schema, relayer/bridge path, EVM revocation controller, constraint updates, proof/finality assumptions, and failure handling that turn a GenLayer agent-performance review into ERC-7710 revocation or policy changes.
Internet Court adapter for GenLayer Intelligent Contract supervision. Use to specify agent-performance rubrics, evidence schemas, decision outputs, and ERC-7710 connector expectations, while delegating actual GenLayer contract writing, linting, testing, deployment, and CLI interaction to the official GenLayer skills at https://skills.genlayer.com/.
Design and implement demos combining x402 HTTP payments with ERC-7710 smart contract delegations and ERC-7715 wallet permission requests for subscriptions, bounded agent budgets, recurring spend, pay-per-use APIs, and agentic commerce.
0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI, or decentralized GPU question.
Use this skill when the user asks to list, create, inspect, update, disable, re-enable, or revoke AltLLM Portal API keys for external agents or applications. Do NOT use for wallet login, billing history, or payment links.
Use this skill when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login for the local altllm CLI. Do NOT use for API key management, billing history, or payment links.
Use this skill when the user asks to inspect AltLLM Portal balance, redeem a promo code, review billing transactions, or view usage analytics by period, model, or API key using the local altllm CLI. Do NOT use for API key lifecycle management or payment-link execution.