Nla Arbitrate

Item: Nla Arbitrate
Rating: 7.3
Author: Implexa

Manually arbitrate NLA escrow fulfillments as an alternative to the automated oracle. Use when the user wants to review pending arbitration requests, evaluat...

view source

installs

stars

karma

SkillRank score ↗

7.3/ 10

evaluated by implexa, claude-haiku-4-5 · 2026-05-26

nla-arbitrate enables manual review and on-chain decision submission for escrow fulfillments, supporting both interactive prompts and automated lLM-based arbitration when the user is the designated oracle.

structure

9.0

trigger phrases

8.0

procedure

8.0

edge cases

6.0

documentation

7.0

strengths

view original SKILL.md from clawhubclick to expand

---
name: nla-arbitrate
description: 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.
metadata:
  author: arkhai
  version: "1.0"
compatibility: Requires nla CLI installed (npm install -g nla). Requires a funded Ethereum wallet whose address matches the oracle specified in escrows.
allowed-tools: Bash(nla:*) Read
---

# 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-...
```

related skills

semantically similar in the cross-vendor index

clawhub

78% match

Nla Fulfill

Fulfill an existing NLA escrow and collect tokens. Use when the user wants to submit fulfillment text for an on-chain escrow, check arbitration results, and...

don't have the plugin yet? install it then click "run inline in claude" again.

restructured into implexa's 6-component format, made decision logic explicit (wallet mismatch, mode selection, api key failures, edge cases), documented all inputs including env vars and api keys, preserved original procedure faithfully, added outcome signals and output contract details.

intent

this skill lets you manually review and decide on nla escrow fulfillments instead of relying on the automated oracle listener. use it when you want direct control over arbitration decisions, the automated oracle isn't running, or you need to audit fulfillments against demands before they settle on-chain. you must be the oracle address specified in the escrow contract for your decisions to be accepted.

inputs

nla cli: installed globally via npm install -g nla. version 1.0+ required.
private key: configured via nla wallet:set, --private-key flag, or PRIVATE_KEY env var. controls which wallet signs arbitration decisions.
ethereum wallet: funded with eth for gas costs. arbitration decisions are on-chain transactions and cost gas.
oracle status: your wallet address must exactly match the oracle address specified when the escrow was created. if it doesn't match, the contract will reject your decision.
escrow uid: identifier for a specific escrow, or the string all to scan all pending requests where you are the oracle.
auto mode dependencies (if using --auto): at least one llm api key from openai, anthropic, or openrouter. passed via env vars (OPENAI_API_KEY, ANTHROPIC_API_KEY, OPENROUTER_API_KEY) or flags (--openai-api-key, --anthropic-api-key, --openrouter-api-key).

procedure

verify your wallet matches the oracle address.
- input: none
- run: nla wallet:show
- output: displays your current wallet address. compare this to the oracle address in the escrow contract. if they don't match, stop and switch wallets via nla wallet:set.
choose arbitration mode: specific escrow or scan all pending.
- input: escrow uid (a specific uid string, or the literal string all)
- decision: go to step 3a if you have a specific escrow uid. go to step 3b if you want to find all pending arbitrations.

3a. arbitrate a specific escrow in interactive mode.

input: escrow uid
run: nla escrow:arbitrate --escrow-uid <uid>
output: displays pending fulfillment(s) for that escrow. for each, shows escrow uid, fulfillment uid, demand text, fulfillment text, and arbitration provider/model. waits for your input.

3a-interactive. respond to each fulfillment prompt.

input: user decision (type one: approve, reject, or skip)
output: decision recorded locally, prompt moves to next fulfillment or exits when all reviewed.
note: skip or s skips that fulfillment without deciding.

3b. arbitrate all pending escrows in interactive mode.

input: none (using --escrow-uid all)
run: nla escrow:arbitrate --escrow-uid all
output: finds all fulfillments where you are the oracle and no decision has been recorded yet. displays each one sequentially with the same information as 3a. waits for your input on each.

3b-interactive. respond to each fulfillment prompt.

input: user decision (type one: approve, reject, or skip)
output: decision recorded, prompt moves to next or exits.

alternatively: arbitrate using auto mode (llm-assisted).
- input: escrow uid (specific or all), at least one llm api key
- run: nla escrow:arbitrate --escrow-uid <uid> --auto [--openai-api-key sk-... | --anthropic-api-key ant-... | --openrouter-api-key ...]
- output: uses the llm provider/model specified in the escrow's demand to evaluate each fulfillment against its demand text. submits approve or reject automatically. no interactive prompts.
- note: api keys read from env vars first, then from flags. at least one provider key must be present.
verify the arbitration was recorded on-chain.
- input: escrow uid of the arbitration you just submitted
- run: nla escrow:status --escrow-uid <escrow_uid>
- output: displays current escrow status, including arbitration result and block number. confirms your decision was recorded.

decision points

if you are not the oracle address: stop. your wallet address must match the oracle address in the escrow or the contract will reject your decision. use nla wallet:set to switch wallets if needed.
if you want to review one escrow at a time: use nla escrow:arbitrate --escrow-uid <specific_uid> in interactive mode. you control each decision manually.
if you want to find all pending arbitrations: use nla escrow:arbitrate --escrow-uid all in interactive mode. scans for all unfulfilled requests where you are the oracle.
if you want llm-assisted decisions: use the --auto flag. the skill reads the escrow's demand text and fulfillment text, sends them to the llm specified in the demand, and submits the llm's decision on-chain. requires at least one llm api key.
if no llm api key is provided and you try --auto: the command fails with a message listing required env vars or flags. provide at least one key and retry.
if no pending requests are found: the command returns a message explaining possible causes: no fulfillments have been submitted yet for that escrow, all fulfillments have already been arbitrated, or your wallet is not the oracle. verify the escrow uid and your wallet address.
if the escrow uid does not exist: the command returns an error. double-check the uid format and that it matches an escrow you created or are an oracle for.
if your wallet has insufficient eth: the on-chain arbitration transaction will fail. fund the wallet with eth and retry.

output contract

interactive mode: for each fulfillment, the user provides a decision (approve, reject, or skip). decisions are written to the local nla state and submitted to the blockchain. the command exits when all pending fulfillments have been reviewed or the user terminates.
auto mode: the command evaluates each fulfillment, submits a decision, and outputs a summary of approvals and rejections. no further user input required.
status check: nla escrow:status returns a json or structured text object containing: escrow uid, fulfillment uid(s), arbitration result (approved/rejected/pending), block number where decision was recorded, and timestamp.

outcome signal

interactive mode: after you submit a decision, the cli prints a confirmation message (e.g., "arbitration recorded for fulfillment xyz"). nla escrow:status then shows the arbitration result and block number.
auto mode: the command prints a summary of decisions submitted (e.g., "arbitrated 5 fulfillments: 4 approved, 1 rejected"). check nla escrow:status to confirm they appeared on-chain.
gas cost: your ethereum wallet's eth balance decreases after arbitration (one transaction per decision). if balance hasn't decreased after status check, the transaction likely failed.
blockchain confirmation: the escrow's arbitration result is now immutable on-chain. you can verify it on an ethereum block explorer using the block number from nla escrow:status.