Tribunal

Runs a doer -> verifier-panel -> consensus loop to verify a deliverable before it ships. An orchestrator freezes acceptance criteria before implementation, dispatches a doer, then convenes a context-walled panel of independent verifiers - including an adversary with an explicit must-oppose mandate - for evidence-anchored review adjudicated to a SHIP / SHIP_WITH_CAVEATS / ITERATE / BLOCK / ESCALATE verdict logged to a ledger. Use for multi-agent verification of any artifact - code slices, plans, documents, audits - whenever asked to verify a deliverable, vet a plan, run a consensus review or in

23 stars 5 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add a-tokyo/aiworkspace --skill tribunal
Manual install
git clone --depth 1 https://github.com/a-tokyo/aiworkspace.git /tmp/aiworkspace
mkdir -p ~/.claude/skills
cp -r /tmp/aiworkspace/.agents/skills/tribunal ~/.claude/skills/tribunal

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Tribunal

The orchestrator builds nothing and scores nothing itself — it slices the work, dispatches
a *separate* doer, convenes *separate* verifiers, and adjudicates on evidence. Three
behaviors carry the value: an **adversarial second look** that catches
what a single pass ships silently, as named failure scenarios; **calibrated verdicts**
— locally fixable defects get ITERATE, not "rewrite everything", and passing math is
overridden only by verified evidence; **evidence before claims** — nothing is "done"
without fresh reproduction; refuted claims are excluded, never averaged in. Announce
at start: "Running this through the tribunal pattern: doer -> verifier panel -> consensus."

## When to use

Multi-part or high-stakes deliverables where a shipped defect costs more than a panel.
Not for trivial edits, anything one verification command proves, or ordinary code
review (dialogue improving a change vs independent measurements of a frozen artifact
against pre-declared criteria, adjudicated to a ship decision). Never nest tribunals
— no role runs the protocol on its own output.

## The loop

1. Freeze acceptance criteria and verification commands BEFORE implementation; derive
   scoring dimensions, weights, and a pass target from them, recorded so re-panels
   reuse the rubric. Identify the operative skills in play — those bearing on how the
   artifact is built or judged (e.g. production-grade); never the tribunal skill itself
Read the full skill on GitHub

Details

Skill name
tribunal
Path
.agents/skills/tribunal/SKILL.md
License
Apache-2.0
Repo updated
19 August 2026

FAQ

What does the Tribunal skill do?

Runs a doer -> verifier-panel -> consensus loop to verify a deliverable before it ships. An orchestrator freezes acceptance criteria before implementation, dispatches a doer, then convenes a context-walled panel of independent verifiers - including an adversary with an explicit must-oppose mandate - for evidence-anchored review adjudicated to a SHIP / SHIP_WITH_CAVEATS / ITERATE / BLOCK / ESCALATE verdict logged to a ledger. Use for multi-agent verification of any artifact - code slices, plans, documents, audits - whenever asked to verify a deliverable, vet a plan, run a consensus review or in

How do I install the Tribunal skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add a-tokyo/aiworkspace --skill tribunal. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Tribunal popular?

It lives in a-tokyo/aiworkspace, which has 23 GitHub stars and 5 forks.

Related skills

Autoresearch

23

a-tokyo/aiworkspace

Autonomous iterative experimentation loop for any programming task. Guides the user through defining goals, measurable metrics, and scope constraints, then runs an autonomous loop of code changes, testing, measuring, and keeping/discarding results. Inspired by Karpathy's autoresearch. USE FOR: autonomous improvement, iterative optimization, experiment loop, auto research, performance tuning, automated experimentation, hill climbing, try things automatically, optimize code, run experiments, autonomous coding loop. DO NOT USE FOR: one-shot tasks, simple bug fixes, code review, or tasks without a

Productivity & Notes

Production Grade

23

a-tokyo/aiworkspace

Principle-engineering posture for production-grade code: reads the repo first, plans before code, matches conventions, pulls latest docs over training recall, and ships the simplest correct change that holds the bar — proper algorithms and data structures, idempotent writes, schema+queries+indexes as one artefact, typed errors, tests in the same diff. Substrate-agnostic; defers to peer skills on their lanes. Use for non-trivial planning, design, implementation, review, or refactoring; RCA and debugging; performance and optimization work; changes touching a database schema, security, infrastruc

Software Development

Scaffold Skill

23

a-tokyo/aiworkspace

Scaffold new AI agent skills with proper symlinking across all IDE tools (Cursor, Claude Code, Codex, etc.). Use when creating a new skill, adding a local skill, or when the user wants to write a custom skill -- either workspace-wide or for a specific project.

AI, LLMs & Agents

Unity AI Navigation

40

Nice-Wolf-Studio/unity-claude-skills

Unity 6 AI and navigation guide. Use when working with NavMesh, pathfinding, NavMeshAgent, NavMeshSurface, NavMeshObstacle, off-mesh links, or Unity Sentis (ML model inference). Covers AI navigation package, runtime NavMesh baking, and common AI patterns like state machines and behavior trees. Based on Unity 6.3 LTS documentation.

AI, LLMs & Agents

Spiking Network Model Builder

43

NeuroAIHub/awesome_cognitive_and_neuroscience_skills

Assists building spiking neural network simulations: neuron models, connectivity, plasticity rules

AI, LLMs & Agents

Claude Code Best Practices

37

iamneilroberts/claude-skills

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.