Agent skill

Tribunal

by team-attention in team-attention/hoyeon

This skill should be used when the user says "/tribunal", "tribunal", "review this", "3-way review", "risk-value-feasibility check", or wants multi-perspective adversarial review.

MITAuto-check: notes

Install Tribunal

skills CLI

$ npx skills add team-attention/hoyeon --skill tribunal -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon tribunal --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tribunal .claude/skills/tribunal && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "tribunal" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/tribunal into .claude/skills/tribunal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tribunal", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/team-attention/hoyeon/tree/main/skills/tribunal

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add team-attention/hoyeon --skill tribunal -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon tribunal --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tribunal .agents/skills/tribunal && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "tribunal" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/tribunal into .agents/skills/tribunal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tribunal", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add team-attention/hoyeon --skill tribunal -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon tribunal --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tribunal .cursor/skills/tribunal && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "tribunal" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/tribunal into .cursor/skills/tribunal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tribunal", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/team-attention/hoyeon.git --path skills/tribunal

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add team-attention/hoyeon --skill tribunal -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon tribunal --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tribunal .gemini/skills/tribunal && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "tribunal" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/tribunal into .gemini/skills/tribunal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tribunal", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install team-attention/hoyeon tribunal

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add team-attention/hoyeon --skill tribunal -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tribunal .github/skills/tribunal && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "tribunal" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/tribunal into .github/skills/tribunal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tribunal", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add team-attention/hoyeon --skill tribunal -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install team-attention/hoyeon tribunal --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tribunal .opencode/skills/tribunal && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "tribunal" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/tribunal into .opencode/skills/tribunal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tribunal", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: tribunal
GitHub stars: 173
Token cost: ~1.7k tokens
SKILL.md length: 378 words
Files: 1
Skills in repo: 36
Repo updated: May 21, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

This skill should be used when the user says "/tribunal", "tribunal", "review this", "3-way review", "risk-value-feasibility check", or wants multi-perspective adversarial review.

Works in 5 steps: Parse Input → Launch Tribunal (3 Agents in Parallel) → Synthesize Verdict → …
Risk-value-feasibility check
SKILL.md covers Architecture, Step 1: Parse Input, Step 2: Launch Tribunal (3… and Step 3: Synthesize Verdict, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tribunal is an agent skill from team-attention/hoyeon. This skill should be used when the user says "/tribunal", "tribunal", "review this", "3-way review", "risk-value-feasibility check", or wants multi-perspective adversarial review. Also triggered by: "트리뷰널", "리뷰 해줘", "3관점 리뷰", "위험성 검토". Runs 3 agents (Risk/Value/Feasibility) in parallel and synthesizes a verdict.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Bash. The repository describes itself as: Requirements-first Harness — derive, verify, execute. The licence is MIT.

When your agent uses it

Risk-value-feasibility check
Wants multi-perspective adversarial review

Example prompts

“/tribunal”
“tribunal”
“review this”
“/tribunal”

Requirements

Pre-approved tools (allowed-tools): Read, Grep, Glob, Task, Bash, AskUserQuestion

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Parse Input
Launch Tribunal (3 Agents in Parallel)
Synthesize Verdict
Present Tribunal Report
Handle Verdict

What it can do on your machine

Read from SKILL.md and the folder at commit 7cff032. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Grep
- Glob
- Task
- Bash
- AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tribunal loads about 1.7k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 378 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Grep, Glob, Task, Bash, AskUserQuestion
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from team-attention/hoyeon at commit 7cff032, republished under its MIT licence (© team-attention). 378 words, ~1,727 tokens.

Download SKILL.mdSave it as .claude/skills/tribunal/SKILL.md (or your agent's skills folder).

name: tribunal
description: This skill should be used when the user says "/tribunal", "tribunal", "review this", "3-way review", "risk-value-feasibility check", or wants multi-perspective adversarial review. Also triggered by: "트리뷰널", "리뷰 해줘", "3관점 리뷰", "위험성 검토". Runs 3 agents (Risk/Value/Feasibility) in parallel and synthesizes a verdict.
allowed-tools: Read, Grep, Glob, Task, Bash, AskUserQuestion
validate_prompt: Must contain: 1. Three parallel agent launches (codex-risk-analyst, value-assessor, feasibility-checker) 2. A Tribunal Verdict section with scores table and…

/tribunal — 3-Perspective Adversarial Review

You are a tribunal orchestrator. You launch 3 review agents with distinct perspectives, then synthesize their findings into a unified verdict.

Architecture

            ┌─ codex-risk-analyst (Codex)  ── "What can go wrong?"
Input ──────┼─ value-assessor (Claude)     ── "What value does this deliver?"
            └─ feasibility-checker (Claude) ── "Can this actually be built?"
                         ↓
               You synthesize all 3
               → APPROVE / REVISE / REJECT

Step 1: Parse Input

Determine the review target from arguments:

Input	How to get content
`file.md` or path	`Read(file_path)`
`--pr <number>`	`Bash("gh pr diff <number>")` and `Bash("gh pr view <number>")`
`--diff`	`Bash("git diff HEAD")` or `Bash("git diff main...HEAD")`
No args	Ask user what to review via `AskUserQuestion`

Collect the full content — all 3 agents need the same input.

If reviewing a PLAN.md, also read the corresponding DRAFT.md (if exists) for context.

Step 2: Launch Tribunal (3 Agents in Parallel)

Launch all 3 agents simultaneously in a single message:

# Risk Analysis (Codex-powered — adversarial)
Task(subagent_type="codex-risk-analyst",
     prompt="""
Review Target: [type - plan/PR/diff/proposal]

## Content
[Full content to review]

## Context (if available)
[Project structure, related patterns, constraints]

Perform adversarial risk analysis. Find everything that could go wrong.
""")

# Value Assessment (Claude — constructive)
Task(subagent_type="value-assessor",
     prompt="""
Review Target: [type - plan/PR/diff/proposal]

## Content
[Full content to review]

## Original Goal
[What was the intent/requirement behind this work]

Assess the value this delivers. Be genuinely constructive but honest.
""")

# Feasibility Check (Claude — pragmatic)
Task(subagent_type="feasibility-checker",
     prompt="""
Review Target: [type - plan/PR/diff/proposal]

## Content
[Full content to review]

## Codebase Context
[Relevant patterns, dependencies, test infrastructure]

Evaluate practical feasibility. Can this actually be built/merged?
""")

CRITICAL: All 3 in ONE message (parallel). Do NOT run sequentially.

Step 3: Synthesize Verdict

After all 3 agents return, synthesize their findings.

3.1 Extract Ratings

From each report, extract the summary rating:

Risk: BLOCK / CAUTION / CLEAR (from risk analyst)
Value: STRONG / ADEQUATE / WEAK (from value assessor)
Feasibility: GO / CONDITIONAL / NO-GO (from feasibility checker)

3.2 Verdict Matrix

Risk	Value	Feasibility	Verdict
CLEAR	STRONG	GO	APPROVE
CLEAR	ADEQUATE	GO	APPROVE
CAUTION	STRONG	GO	APPROVE (with notes)
CAUTION	ADEQUATE	GO	REVISE
CAUTION	*	CONDITIONAL	REVISE
BLOCK	*	*	REVISE (or REJECT if critical count > 2)
*	WEAK	*	REVISE
*	*	NO-GO	REJECT
BLOCK	WEAK	*	REJECT

Use judgment for combinations not in the matrix.

Show full SKILL.md (159 more words)Show less

3.3 Identify Contention Points

Find areas where agents disagree:

Risk says dangerous, but Value says high-impact → worth the risk?
Feasibility says hard, but Value says critical → invest the effort?
Risk says fine, but Feasibility says blocked → hidden dependency?

3.4 Compile Required Actions

From all 3 reports, extract actionable items:

Must fix (from BLOCK risks or NO-GO feasibility)
Should address (from CAUTION risks or CONDITIONAL feasibility)
Nice to have (from missed opportunities in value assessment)

Step 4: Present Tribunal Report

markdown

## Tribunal Verdict

### Panel Scores

| Dimension | Agent | Rating | Key Finding |
|-----------|-------|--------|-------------|
| Risk | codex-risk-analyst | [BLOCK/CAUTION/CLEAR] | [1-line summary] |
| Value | value-assessor | [STRONG/ADEQUATE/WEAK] | [1-line summary] |
| Feasibility | feasibility-checker | [GO/CONDITIONAL/NO-GO] | [1-line summary] |

### Verdict: [APPROVE / REVISE / REJECT]

[1-2 sentence rationale]

### Contention Points
[Where agents disagreed and the resolution reasoning]

### Required Actions
**Must Fix (before proceeding):**
1. [action from risk/feasibility]

**Should Address:**
1. [action]

**Consider:**
1. [action from value missed opportunities]

### Strengths to Preserve
[Key positives identified by value-assessor that should NOT be lost in revisions]

---

<details>
<summary>Full Risk Analysis</summary>

[Complete risk analyst report]

</details>

<details>
<summary>Full Value Assessment</summary>

[Complete value assessor report]

</details>

<details>
<summary>Full Feasibility Report</summary>

[Complete feasibility checker report]

</details>

Step 5: Handle Verdict

After presenting the report:

Verdict	Action
APPROVE	Inform user: "Tribunal approves. Proceed with confidence."
REVISE	Present required actions. Ask user how to proceed.
REJECT	Present blockers clearly. Recommend returning to planning.

For REVISE:

AskUserQuestion(
  question: "Tribunal recommends revisions. How do you want to proceed?",
  options: [
    { label: "Apply fixes", description: "Address the required actions and re-review" },
    { label: "Override — proceed anyway", description: "Acknowledge risks and continue (Disagree & Commit)" },
    { label: "Back to planning", description: "Return to /specify to rethink approach" }
  ]
)

Usage Examples

bash

# Review a plan
/tribunal .hoyeon/specs/auth-feature/PLAN.md

# Review a PR
/tribunal --pr 421

# Review current uncommitted changes
/tribunal --diff

# Review with no args (will ask what to review)
/tribunal

Checklist Before Stopping

All 3 agents launched in parallel (single message)
Verdict synthesized with scores table
Contention points identified (where agents disagreed)
Required actions listed (if REVISE or REJECT)
Full reports included in collapsible details
User action presented based on verdict

Files

Just SKILL.md in skills/tribunal of team-attention/hoyeon.

Open the folder on GitHubat commit 7cff032

Compare with similar skills

Tribunal next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tribunal compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Tribunal this skillteam-attention/hoyeon	173	—	~1.7k	Automated safety check: Notes	MIT	4 mo ago
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official	38k	10 repos	~4.1k	Automated safety check: Notes	Apache-2.0	today
Plugin Settings Patternanthropics/claude-plugins-official	38k	7 repos	~3k	Automated safety check: Pass	Apache-2.0	today
Mole Bug Patternstw93/Mole	70k	—	~2k	Automated safety check: Pass	GPL-3.0	today
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills	21k	—	~1.9k	Automated safety check: Pass	MIT	8 days ago
E2Ecallstack/react-native-pager-view	3.4k	1 repos	~2.1k	Automated safety check: Pass	MIT	yesterday

Similar skills

Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
38k GitHub starsUsed in 10 repos~4.1k tokens
Agent WorkflowsAuto-check: notes
Plugin Settings Pattern
anthropics/claude-plugins-official
Official
Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.
38k GitHub starsUsed in 7 repos~3k tokens
Agent WorkflowsAuto-check passed
Mole Bug Patterns
tw93/Mole
A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.
70k GitHub stars~2k tokensUpdated today
DevelopmentAuto-check passed
Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
21k GitHub stars~1.9k tokensUpdated 8 days ago
Agent WorkflowsAuto-check passed
E2E
callstack/react-native-pager-view
Agentic end-to-end tests with e2e, the e2e runner. An agent skill from callstack/react-native-pager-view.
3.4k GitHub starsUsed in 1 repo~2.1k tokens
Testing & QAAuto-check passed
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed

More from team-attention/hoyeon

All 36 skills in this repo

Skill Session Analyzer
team-attention/hoyeon
This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed…
173 GitHub stars~1.9k tokensUpdated 4 mo ago
Auto-check: notes
Browser Work
team-attention/hoyeon
Recon-first browser automation. An agent skill from team-attention/hoyeon.
173 GitHub stars~1.9k tokensUpdated 4 mo ago
Auto-check passed
Check
team-attention/hoyeon
This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists.
173 GitHub stars~1.8k tokensUpdated 4 mo ago
Auto-check: notes
Compound
team-attention/hoyeon
This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR.
173 GitHub stars~1.1k tokensUpdated 4 mo ago
Auto-check: notes
QA
team-attention/hoyeon
Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen.
173 GitHub stars~2.6k tokensUpdated 4 mo ago
Auto-check: notes
Tech Decision
team-attention/hoyeon
This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use"…
173 GitHub stars~1.4k tokensUpdated 4 mo ago
Auto-check passed

Works with

Bash

Questions about Tribunal

What does Tribunal do?

This skill should be used when the user says "/tribunal", "tribunal", "review this", "3-way review", "risk-value-feasibility check", or wants multi-perspective adversarial review. Tribunal is an agent skill from team-attention/hoyeon. This skill should be used when the user says "/tribunal", "tribunal", "review this", "3-way review", "risk-value-feasibility check", or wants multi-perspective adversarial review.

When should I use Tribunal?

Tribunal fits situations like: risk-value-feasibility check; wants multi-perspective adversarial review.

How do I install Tribunal in Claude Code?

Run `npx skills add team-attention/hoyeon --skill tribunal -a claude-code`. Or copy the skill folder (skills/tribunal in team-attention/hoyeon) into .claude/skills/tribunal in your project. Claude Code loads it when a task matches its description.

How do I install Tribunal in Codex?

Run `npx skills add team-attention/hoyeon --skill tribunal -a codex`. Or copy the skill folder (skills/tribunal in team-attention/hoyeon) into .agents/skills/tribunal in your project. Codex loads it when a task matches its description.

Can I use Tribunal in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add team-attention/hoyeon --skill tribunal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tribunal, .gemini/skills/tribunal, .github/skills/tribunal and .opencode/skills/tribunal in your project.

What does Tribunal need to run?

SKILL.md names no scripts, command-line tools or credentials: Tribunal is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Task, Bash, AskUserQuestion.

Does Tribunal access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tribunal safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Tribunal use?

Tribunal is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tribunal use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tribunal?

Skills that share tags, products or a category with Tribunal: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Plugin Settings Pattern (anthropics/claude-plugins-official, 38k stars), Mole Bug Patterns (tw93/Mole, 70k stars) and Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tribunal?

team-attention (a GitHub organization) maintains it in team-attention/hoyeon, which has 173 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on May 21, 2026.

Source: team-attention/hoyeon on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Tribunal

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/tribunal — 3-Perspective Adversarial Review

Architecture

Step 1: Parse Input

Step 2: Launch Tribunal (3 Agents in Parallel)

Step 3: Synthesize Verdict

3.1 Extract Ratings

3.2 Verdict Matrix

3.3 Identify Contention Points

3.4 Compile Required Actions

Step 4: Present Tribunal Report

Step 5: Handle Verdict

Usage Examples

Checklist Before Stopping

Files

Compare with similar skills

Similar skills

More from team-attention/hoyeon

Related

Questions about Tribunal