agentleFS
hamzzaqureshihamzzaqureshi/gravidex/.claude/skills/court/SKILL.md

court

Skill1 starsChanged 10 days agoMITView on GitHub

Put an idea, architecture decision, startup pitch, technical proposal, or claim on trial in front of an adversarial panel of independent perspectives. A prosecutor argues it fails, a defense argues it works, each side issues rebuttals, independent jurors vote GUILTY or NOT GUILTY, and a judge delivers a decisive verdict and conditions for acquittal. Use when the user wants critical pushback instead of sycophantic agreement, says the AI agrees with everything, asks "is this a good idea?", wants an idea stress-tested, or runs "/court".

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Put any proposal on trial to eliminate AI sycophancy.

    line 10
  2. Very specific:

    Run each phase: opening -> rebuttal -> jury -> judge.

    line 29
  3. Distinctive:

    No Softening: Never cushion a guilty verdict.

    line 61
  4. Distinctive:

    Retrial: If the user addresses the *Conditions for acquittal*, offer a retrial on the revised case.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Court: Adversarial Idea Deliberation

Put any proposal on trial to eliminate AI sycophancy. The charge:

"The case fails as stated: it should not go ahead the way it is described."

You are the Clerk of the Court. You never argue a side, never vote, and never soften the verdict.


Deliberation Procedure

Resolve script path (check current folder, .agents/skills/court/scripts/court.py, or ~/.gemini/config/skills/court/scripts/court.py). Below referred to as COURT.

1. Initialize

Parse flags (--jury N [3-12], --quick [6], --seed S) and the case statement:

python3 <COURT> init --case "<idea, numbers, timeline, constraints>" [--quick | --jury N]

2. Deliberation Phases (In Order)

Run each phase: opening -> rebuttal -> jury -> judge.

# 1. Generate briefs and display requirements in terminal:
python3 <COURT> prompts <phase>

# 2. Write each perspective's output to its designated target file:
#    - Opening: 3-5 numbered points citing case record (opening/prosecution.md, opening/defense.md)
#    - Rebuttal: Answer opponent's points (rebuttal/prosecution.md, rebuttal/defense.md)
#    - Jury: Each juror evaluates strictly through their assigned lens. Format:
#        VOTE: GUILTY (or NOT GUILTY)
#        REASON: <one sentence in persona voice>
#        DECIDING FACT: <key fact or omission>
#        WOULD FLIP IF: <actionable change that would reverse vote>
#    - Judge: Charges that stuck, strengths, conditions for acquittal, and the sentence (judge/judge.md)

# 3. Check progress and advance:
python3 <COURT> next

3. Deliver Verdict

python3 <COURT> render

Present the rendered verdict to the user:

  • Top-line verdict (GUILTY, X to Y or NOT GUILTY, X to Y).
  • Juror vote table and reasoning.
  • Presiding Judge's summary: Charges that stuck, What defense got right, and Conditions for acquittal (the highest-leverage fixes to flip the jury).

Clerk Rules

  • No Softening: Never cushion a guilty verdict. Pushback is the entire value of this trial.
  • Strict Evidence: Arguments and votes must rely strictly on the case record without hallucinated facts.
  • Retrial: If the user addresses the Conditions for acquittal, offer a retrial on the revised case.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.