Arbiter
Push decisions to Arbiter Zebu for async human review. Use when you need human input on plans, architectural choices, or approval before proceeding.
Push decisions to Arbiter Zebu for async human review. Use when you need human input on plans, architectural choices, or approval before proceeding.
Real data. Real impact.
Emerging
Developers
Per week
Open source
Skills give you superpowers. Install in 30 seconds.
Push decisions to Arbiter Zebu for async human review. Use when you need human input on plans, architectural choices, or approval before proceeding.
Quick install via ClawHub:
clawhub install arbiter
Or via bun (makes CLI commands available globally):
bun add -g arbiter-skill
Or manual:
git clone https://github.com/5hanth/arbiter-skill.git cd arbiter-skill && npm install && npm run build ln -s $(pwd) ~/.clawdbot/skills/arbiter
bunx arbiter-zebu)~/.arbiter/queue/ directory (created automatically by the bot)Set these in your agent's environment for automatic agent/session detection:
| Variable | Description | Example |
|---|---|---|
| Agent ID | , |
| Session key | |
Do NOT use for:
Create a decision plan for human review.
CLI:
arbiter-push '<json>' — takes a single JSON argument containing all fields.
arbiter-push '{ "title": "API Design Decisions", "tag": "nft-marketplace", "context": "SWE2 needs these decided before API work", "priority": "normal", "notify": "agent:swe2:main", "decisions": [ { "id": "auth-strategy", "title": "Auth Strategy", "context": "How to authenticate admin users", "options": [ {"key": "jwt", "label": "JWT tokens", "note": "Stateless"}, {"key": "session", "label": "Sessions", "note": "More control"}, {"key": "oauth", "label": "OAuth", "note": "External provider"} ] }, { "id": "database", "title": "Database Choice", "context": "Primary datastore", "options": [ {"key": "postgresql", "label": "PostgreSQL + JSONB"}, {"key": "mongodb", "label": "MongoDB"} ], "allowCustom": true } ] }'
JSON Fields:
| Field | Required | Description |
|---|---|---|
| Yes | Plan title |
| No | Tag for filtering (e.g., project name) |
| No | Background for reviewer |
| No | , , , (default: normal) |
| No | Session to notify when complete |
| No | Agent ID (auto-detected from env) |
| No | Session key (auto-detected from env) |
| Yes | Array of decisions |
Decision object:
| Field | Required | Description |
|---|---|---|
| Yes | Unique ID within plan |
| Yes | Decision title |
| No | Explanation for reviewer |
| Yes | Array of |
| No | Allow free-text answer (default: false) |
| No | Suggested option key |
Returns:
{ "planId": "abc123", "file": "~/.arbiter/queue/pending/ceo-api-design-abc123.md", "total": 2, "status": "pending" }
Check the status of a decision plan.
CLI:
arbiter-status <plan-id> or arbiter-status --tag <tag>
arbiter-status abc12345 # or arbiter-status --tag nft-marketplace
Returns:
{ "planId": "abc123", "title": "API Design Decisions", "status": "in_progress", "total": 3, "answered": 1, "remaining": 2, "decisions": { "auth-strategy": {"status": "answered", "answer": "jwt"}, "database": {"status": "pending", "answer": null}, "caching": {"status": "pending", "answer": null} } }
Get answers from a completed plan.
CLI:
arbiter-get <plan-id> or arbiter-get --tag <tag>
arbiter-get abc12345 # or arbiter-get --tag nft-marketplace
Returns:
{ "planId": "abc123", "status": "completed", "completedAt": "2026-01-30T01:45:00Z", "answers": { "auth-strategy": "jwt", "database": "postgresql", "caching": "redis" } }
Error if not complete:
{ "error": "Plan not complete", "status": "in_progress", "remaining": 2 }
Block until plan is complete (with timeout).
arbiter-await abc12345 --timeout 3600
Polls every 30 seconds until complete or timeout.
Returns: Same as
arbiter_get on completion.
# Push plan decisions (single JSON argument) RESULT=$(arbiter-push '{"title":"Clean IT i18n Plan","tag":"clean-it","priority":"high","notify":"agent:swe3:main","decisions":[{"id":"library","title":"i18n Library","options":[{"key":"i18next","label":"i18next"},{"key":"formatjs","label":"FormatJS"}]},{"id":"keys","title":"Key Structure","options":[{"key":"flat","label":"Flat (login.button)"},{"key":"nested","label":"Nested ({login:{button}})"}]}]}')PLAN_ID=$(echo $RESULT | jq -r '.planId') echo "Pushed plan $PLAN_ID — waiting for human review"
# Check if decisions are ready STATUS=$(arbiter-status --tag nft-marketplace)if [ "$(echo $STATUS | jq -r '.status')" == "completed" ]; then ANSWERS=$(arbiter-get --tag nft-marketplace) AUTH=$(echo $ANSWERS | jq -r '.answers["auth-strategy"]') echo "Using auth strategy: $AUTH"
Proceed with implementation
else echo "Still waiting for $(echo $STATUS | jq -r '.remaining') decisions" fi
# Wait up to 1 hour for decisions ANSWERS=$(arbiter-await abc12345 --timeout 3600)if [ $? -eq 0 ]; then
Got answers, proceed
echo "Decisions ready: $ANSWERS" else echo "Timeout waiting for decisions" fi
--tag project-name)urgent for true blockers| Path | Purpose |
|---|---|
| Plans awaiting review |
| Answered plans (archive) |
| Agent notifications |
In your HEARTBEAT.md, add:
## Check Arbiter Notifications
- Check if
has files for my session~/.arbiter/queue/notify/- If yes, read answers and proceed with blocked work
Delete notification file after processing
| Issue | Solution |
|---|---|
| Plan not showing in Arbiter | Check file is valid YAML frontmatter |
| Answers not appearing | Check , may be incomplete |
| Notification not received | Ensure was set correctly |
No automatic installation available. Please visit the source repository for installation instructions.
View Installation Instructions1,500+ AI skills, agents & workflows. Install in 30 seconds. Part of the Torly.ai family.
© 2026 Torly.ai. All rights reserved.