How do I install the Ca Tribunal skill?

Run npx skillmds add majiayu000/ca-tribunal in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ca Tribunal safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ca Tribunal?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ca Tribunal free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ca Tribunal?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ca Tribunal by majiayu000 — Agent Skill

Name: Ca Tribunal
Rating: 4.2 (5 reviews)
Author: majiayu000

Ca Tribunal

Deep, rarely-convened whole-codebase audit — eleven specialist lenses, a resumable on-disk audit log, findings filed as GitHub issues on approval. Expensive; estimates cost and STOPs before running. Never a required gate.

majiayu000 9c859ca 2 files · 4.4 KB Updated Sep 9, 2026 567 repo stars

File contents

$ca-tribunal — deep codebase audit

The deepest, most expensive review codeArbiter offers, convened rarely and on demand. Routes to the tribunal skill. Eleven lenses judge the codebase; every finding persists to its own file (plus append-only triage/run logs) under .codearbiter/reports/<run-id>/, so an interrupted run resumes from disk. Never a required gate — critical/high are blocking-severity findings, not a pipeline halt.

Cost first — this lane routinely costs millions of tokens on a large repo. Phase 0 sizes the codebase, prints a token-cost band, recommends the highest-reasoning model, and STOPs for your acknowledgement before dispatching anything. Nothing runs unacknowledged.

Flow

Load and follow the tribunal skill (${CLAUDE_PLUGIN_ROOT}/routines/tribunal/SKILL.md). In brief:

Phase 0 (STOP) — cost estimate, model recommendation, resume check. Phase 1 (BLOCK) — map the codebase; risk-rank and mark trust boundaries; record AI-authorship markers and iteration depth. Phase 2 (BLOCK) — dispatch the eleven tribunal-* lenses in priority waves (≤5 in flight); each writes one file per finding under its own findings/<lens>/ dir. Phase 3 (BLOCK) — triage per wave from disk: dedup, independent calibration, decision vocabulary. Phase 4 (BLOCK) — project the human-readable report from the logs. Phase 5 (BLOCK) — on explicit selection, file findings as GitHub issues; idempotent against the tracker. Phase 6 (STOP) — optional, opt-in KPI telemetry to the public codeArbiter repo.

Arguments

"scope-path" — focus the audit on a subtree (default: repository root). The full lens roster still runs; only the scope narrows.

--tag <label> — freeform run label recorded in telemetry (see references/telemetry.md).

Routes to

${CLAUDE_PLUGIN_ROOT}/routines/tribunal/SKILL.md — dispatches the eleven tribunal-* reviewers (and, on a large repo, the optional map-structure / map-deps mappers).

When NOT to use

A review of the current diff → $ca-review (gate-blocking, fast).
A lean periodic sweep → $ca-checkpoint (cheap, frequent; tribunal is its rare, deep counterpart).
An adversarial STRIDE pass on one sensitive feature → $ca-threat-model.
A governance packet for a window → $ca-audit.
Anything on a schedule or in a hot loop — tribunal is a rare, deliberate, expensive convening, not a routine gate.

Hard gate

MUST NOT dispatch any lens before you acknowledge the Phase 0 cost estimate. MUST NOT act as a required gate or block a merge/commit. MUST NOT file an issue or send telemetry without explicit authorization. Read-only on project code until the filing gate; findings file as GitHub issues, never the task board.

---name: ca-tribunaldescription: Deep, rarely-convened whole-codebase audit — eleven specialist lenses, a resumable on-disk audit log, findings filed as GitHub issues on approval. Expensive; estimates cost and STOPs before running. Never a required gate.---# $ca-tribunal — deep codebase audit The deepest, most expensive review codeArbiter offers, convened rarely and on demand. Routes to the tribunal skill. Eleven lenses judge the codebase; every finding persists to its own file (plus append-only triage/run logs) under `.codearbiter/reports/<run-id>/`, so an interrupted run resumes from disk. Never a required gate — critical/high are blocking-severity findings, not a pipeline halt. Cost first — this lane routinely costs millions of tokens on a large repo. Phase 0 sizes the codebase, prints a token-cost band, recommends the highest-reasoning model, and STOPs for your acknowledgement before dispatching anything. Nothing runs unacknowledged. ## Flow Load and follow the tribunal skill (`${CLAUDE_PLUGIN_ROOT}/routines/tribunal/SKILL.md`). In brief: Phase 0 (STOP) — cost estimate, model recommendation, resume check. Phase 1 (BLOCK) — map the codebase; risk-rank and mark trust boundaries; record AI-authorship markers and iteration depth. Phase 2 (BLOCK) — dispatch the eleven tribunal-* lenses in priority waves (≤5 in flight); each writes one file per finding under its own `findings/<lens>/` dir. Phase 3 (BLOCK) — triage per wave from disk: dedup, independent calibration, decision vocabulary. Phase 4 (BLOCK) — project the human-readable report from the logs. Phase 5 (BLOCK) — on explicit selection, file findings as GitHub issues; idempotent against the tracker. Phase 6 (STOP) — optional, opt-in KPI telemetry to the public codeArbiter repo. ## Arguments `"scope-path"` — focus the audit on a subtree (default: repository root). The full lens roster still runs; only the scope narrows. `--tag <label>` — freeform run label recorded in telemetry (see `references/telemetry.md`). ## Routes to `${CLAUDE_PLUGIN_ROOT}/routines/tribunal/SKILL.md` — dispatches the eleven tribunal-* reviewers (and, on a large repo, the optional map-structure / map-deps mappers). ## When NOT to use - A review of the current diff → `$ca-review` (gate-blocking, fast). - A lean periodic sweep → `$ca-checkpoint` (cheap, frequent; tribunal is its rare, deep counterpart). - An adversarial STRIDE pass on one sensitive feature → `$ca-threat-model`. - A governance packet for a window → `$ca-audit`. - Anything on a schedule or in a hot loop — tribunal is a rare, deliberate, expensive convening, not a routine gate. ## Hard gate MUST NOT dispatch any lens before you acknowledge the Phase 0 cost estimate. MUST NOT act as a required gate or block a merge/commit. MUST NOT file an issue or send telemetry without explicit authorization. Read-only on project code until the filing gate; findings file as GitHub issues, never the task board.

Frequently asked questions