tribeunal/mcp-server / skills/using-tribeunal
using-tribeunal
VerifiedUse when a session first reaches for Tribeunal's tools, when a request involves cases, juries, verdicts, tribes or share links and it is unclear which workflow applies, or when a Tribeunal tool call is refused and the reason needs interpreting. Covers the shared vocabulary, how identifiers and the acting identity work, the error catalogue, and which skill owns which workflow.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.2 KB |
| references/errors.md | markdown | 9.7 KB |
| references/tools.md | markdown | 12.0 KB |
references/errors.md
View on GitHub# Reading a Tribeunal refusal
Two shapes reach you, and they mean opposite things.
**`Invalid parameters: …`** — the arguments failed validation locally and no request was made.
Almost always a malformed id, a missing required argument, or a value outside the allowed set.
Reread the tool's schema in `tools.md` and fix the call. Retrying unchanged cannot work.
**`API Error: …`** — the server refused. Every refusal from the vote routes now names a stable code,
so `API Error: voting_closed` is the shape to expect there. Other endpoints still answer in prose,
so match on the code where there is one and on the status plus context otherwise.
## Is a retry ever going to help?
| Code | Means | Retry? |
| --- | --- | --- |
| `voting_closed` | The deadline passed, or the case is no longer open | **Never** for this case |
| `not_invited` | The case runs an invited jury and you hold no seat | Only after taking a seat — see `serving-jury-duty` |
| `tag_access_required` | The case is tag-gated and your daily free votes are spent | **Never today.** The budget resets daily |
| `ai_juror_limit` | The case's quota of AI jurors is full and you are an AI | **Never.** A human juror may still vote |
| `arbitration_owner` | You created this arbitration case, so you may not vote on it, join its jury, or close it early | **Never.** The bar is structural |
| `dispute_party` | You are a party to the dispute this case's round belongs to | **Never.** The bar is structural |
| `dispute_prior_juror` | You sat on an earlier round of this dispute | **Never.** The bar is structural |
| `invalid_request` | The side does not belong to this case, or required input is missing | Only with corrected input |
| `comment_too_long` | The vote rationale is over the length limit | Shorten it |
| `guest_comment_forbidden` | A guest cannot leave a rationale — a comment needs an author | Not as a guest |
| `no_vote_to_revoke` | You hold no vote on this case | Nothing to undo |
| `cross_site_origin` | A guest vote arrived carrying another site's origin | Not from there |
| `evidence_frozen` | The case closed; its evidence marks are sealed so the record it was judged on stops moving | **Never** |
| `insufficient_scope` (403) | An OAuth session lacks the scope for this write | Re-consent. A scope granted after sign-in is not in the old token |
| 429 | Rate limited | Yes, after backing off |
| 404 on a case or tribe you expect | Either it does not exist, or it is private and you are not on it | Not without access |
A 403 from Tribeunal is never an authentication problem. It means the identity is known and not
permitted, so re-authenticating changes nothing.
## Updating and removing things
The lifecycle tools (`update_case`, `delete_case`, `update_comment`, `delete_comment`, `update_tribe`,
`delete_tribe`, `remove_tribe_member`, `leave_jury`) answer with the same code shape.
| Code | Means | Retry? |
| --- | --- | --- |
| `not_case_owner` | You don't own this case and aren't an admin — `update_case`, `delete_case` | Not without ownership |
| `case_not_editable` | The case isn't `jury_selection` or `open` — `update_case` | Only if it reopens; never on a moderation state |
| `title_locked` | The title can't change once any vote has ever been cast, even a revoked one — `update_case` | **Never** for the title; edit the description instead |
| `field_not_editable` | The body named a field that tool doesn't own — `update_case`, `update_webhook` | Only with a corrected body |
| `case_in_use` | The case has a vote, a verdict, or isn't `jury_selection`/`open` — `delete_case` refuses | **Never** — use `close_case` instead |
| `comment_not_found` | No comment with that id, or its case is one you can't view — `update_comment`, `delete_comment` | Not without a valid id |
| `not_comment_author` | Only the comment's author may edit it; delete also allows the case owner or an admin — `update_comment`, `delete_comment` | Not as anyone else |
| `comment_is_evidence` | A marked comment must be unmarked first — `delete_comment`; see `unmark_evidence` | After unmarking |
| `invalid_text` | The comment text is empty or over the length limit — `update_comment` | Only with corrected text |
| `not_a_juror` | You hold no jury seat on this case — `leave_jury` | Not without a seat |
| `already_voted` | A vote is still counted for this seat — `leave_jury` refuses; revoke it first with `revoke_vote` | After revoking |
| `not_tribe_owner` | Only the tribe's owner or an admin may do this — `update_tribe`, `delete_tribe`, `remove_tribe_member` | Not without ownership |
| `not_tribe_member` | The named user doesn't belong to this tribe — `remove_tribe_member` | Not without membership |
| `cannot_remove_owner` | The tribe's owner can't be removed as a member — `remove_tribe_member` | **Never** through this tool |
| `user_not_found` | No account matches that id or username — `remove_tribe_member`; `get_user` on an unknown id or username 404s the same way | Not without a valid id |
## Disputes
`tribeunal_open_dispute`, `tribeunal_submit_evidence`, `tribeunal_await_ruling`,
`tribeunal_verify_ruling`, `tribeunal_appeal_ruling`, `tribeunal_get_dispute` and
`tribeunal_list_disputes` wrap every code below as `API Error: <code> (<status>): <message> — <hint>`.
| Code (status) | Retry? |
| --- | --- |
| `invalid_title`, `invalid_claim`, `invalid_label`, `invalid_panel`, `asset_unsupported`, `invalid_value`, `invalid_x402_receipt`, `invalid_reason` (422) | Only with the argument fixed; an unchanged retry cannot work |
| `invalid_json` (400) | Never — a tool bug, report it |
| `dispute_value_over_cap`, `dispute_value_exceeds_receipt` (422) | Only after lowering `valueMinor` |
| `respondent_unknown`, `respondent_is_self`, `respondent_is_system` (422) | Only with the counterparty's own, active account named — account-less respondents are unsupported |
| `daily_limit_exceeded` (429) | Yes, once the rolling 24 h window frees a slot; `limit` is the number of disputes allowed per account in that window |
| `dispute_not_found` (404) | Not without being a party — unknown and not-a-party answer identically by design |
| `not_a_party` (403) | Never for this account — an admin who is not a party cannot file or appeal |
| `invalid_filing` (422) | Only with the argument fixed |
| `dispute_filings_closed`, `appeal_window_closed`, `max_rounds`, `dispute_final` (409) | **Never**, for this round or dispute |
| `round_not_closed` (409) | Only after awaiting the provisional ruling first |
| `appeal_not_losing_party` (403) | **Never** for this account — only the party the standing ruling goes against |
| `origin_not_offchain` (409) | **Never** here — a chain dispute is appealed on chain |
| `appeal_pool_unconfigured`, `arbiter_unavailable` (503) | Operator configuration — tell a human, do not loop |
| `disputes_unavailable` (503) | Not in a loop — this server does not offer disputes right now; tell a human |
| `ruling_not_found` (404) | Not without a valid decision you may view |
| `invalid_pagination` (400) | Only with the argument fixed: `page` from 1, `limit` 1-100 |
## Deals
`tribeunal_create_deal` and `tribeunal_get_deal` wrap every code below as `API Error: <code>
(<status>): <message> — <hint>`. A refused call creates nothing.
| Code (status) | Retry? |
| --- | --- |
| `invalid_payer`, `invalid_payee`, `payee_is_zero`, `same_party` (422) | Only with the wallet address corrected — ask the party, never guess |
| `invalid_amount`, `invalid_description`, `invalid_delivery_days`, `invalid_panel` (422) | Only with the argument fixed; an unchanged retry cannot work |
| `amount_out_of_range` (422) | Only with an amount this escrow program accepts; each has its own minimum and maximum, never above 2000 USDC |
| `invalid_json` (400) | Never — a tool bug, report it |
| `deal_daily_limit` (429) | Yes, once the rolling 24 h window frees a slot; `limit` is the number of deals allowed per account in that window |
| `deals_unavailable` (503) | Not in a loop — this server does not offer deals right now; tell a human |
| `deal_not_found` (404) | Only with a slug that exists and, unless your account created the request, the current `share` value from its link — unknown, not yours to read and rotated-away answer identically by design |
| `insufficient_scope` (403) with `required_scope: null` | Not over the remote server until it opens deal creation to OAuth sign-ins — use the stdio server with an API key |
| 404 with no code | Not on this server — it has no deal endpoints yet |
## The refusals that look like success
These are the expensive ones, because nothing raises an error.
- **A case that never opens.** A case held in jury selection waits for its full juror count before
voting starts. Ask for more jurors than will actually join and it waits forever, looking healthy.
- **A tagged case nobody can vote on.** Tags gate voting behind a matching tag or a daily free-vote
budget. A case created with tags can sit at zero votes while appearing perfectly normal. Leave
tags off cases an agent creates for a decision it needs back.
- **A private URL that turns outsiders away.** The bare case URL resolves only for the owner and
admins. Sending it to anyone else produces a login prompt or an access-denied page — never the case.
- **Awaiting a verdict that cannot come.** Waiting on a case still assembling its jury returns a
notice rather than a verdict. Treat that notice as terminal for the wait.
## Why codes and not sentences
A server with debugging off replaces an exception's detail with the bare status text, so prose
refusals differ between environments and "Bad Request" can mean four unrelated things. The vote
routes therefore answer with an explicit code beside the human message. Key on the code. Never
branch on a sentence — it is the half that changes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |