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-... ```
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.
Give the AI agent its own EVM wallet with admin-controlled policies the agent CANNOT bypass even under prompt injection. Encrypted keystore (AES-256-GCM, scrypt KDF), policy file the agent has no tool to write, deterministic policy gate on every signing operation, optional local HTTP dashboard. Triggers: agent wallet, give the agent a wallet, agent address, fund the agent, agent autonomy, policy gate, kill switch, agent permissions, bounded autonomy, ERC-4337 alternative, session-key alternative.
Crypto wallet operations via the awal CLI — sign in, check balances, send USDC/ETH/POL/SOL, trade tokens, fund the wallet, and use the x402 payment protocol to discover paid services, pay for API calls, monetize an API, or query onchain data. Use whenever the user mentions signing in, login, authentication, wallet status, balance, address, sending money, paying someone, transferring tokens, ENS names, swapping/trading/converting tokens, funding/topping up/onramp, USDC, ETH, POL, SOL, the x402 bazaar, paid APIs, monetizing an endpoint, or querying onchain data on Base.
Help developers write code that interacts with Alkahest escrow contracts using the TypeScript, Rust, or Python SDK
Interact with Alkahest escrow contracts as a buyer, seller, or oracle using the CLI
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.