court
Put an idea on trial in front of a jury of 12 Claudes. A prosecutor Claude argues it fails, a defense Claude argues it works, they rebut each other, 12 juror Claudes with different backgrounds vote on their own, and a judge Claude reads the verdict and the conditions that would flip it
Install / Use
npx skills add alexyc9381/court-skill --skill courtInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Tags
Our assessment of court
court scores 83/100 on our quality scale, 515th of 642 Marketing skills we index.
Its SKILL.md is 5.0 KB long, split into 7 sections with 3 code examples: a solid amount of guidance for an agent.
It has 342 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 44 days ago, so court is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-12. Automated pattern scan on 2026-11-12. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
court compared with similar skills
All 4 of these similar skills score higher than court; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| court (this skill)by alexyc9381 | 83 | 342 | 44d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install court?
- Run
npx skills add alexyc9381/court-skill --skill court. The install tabs above show the steps for each supported agent. - Which AI agents does court work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is court safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is court still maintained?
- The repository was last updated 44 days ago, so court is actively maintained.
Skill content
View source on GitHubname: court description: >- Put an idea on trial in front of a jury of 12 Claudes. A prosecutor Claude argues it fails, a defense Claude argues it works, they rebut each other, 12 juror Claudes with different backgrounds vote on their own, and a judge Claude reads the verdict and the conditions that would flip it. Use when the user wants honest pushback instead of agreement, says Claude just agrees with everything, asks "is this a good idea", wants an idea, plan, pitch or claim stress-tested, or says "court" or "put it on trial". argument-hint: "[--jury N | --quick] [--seed S] <the idea, plan or claim>" license: MIT metadata: author: "Alex Chen (@nocodealex)" homepage: "https://chen.media" source: "https://github.com/alexyc9381/court-skill" version: "1.0.0"
court
For when Claude agrees with everything you say. Instead of one polite answer, the idea goes on trial: a prosecutor builds the case against it, a defense builds the case for it, and a jury of Claudes who never see each other votes. You are the clerk of the court. You never argue, never vote, and never soften the verdict.
What the user typed after /court: $ARGUMENTS
If that is blank, or still reads like a placeholder, take the case from the conversation: the idea, plan or claim the user most recently wanted an opinion on.
The tool
Every piece of bookkeeping goes through court.py in this skill's folder:
python3 "${CLAUDE_SKILL_DIR}/court.py" <command>
Below, COURT means exactly that command. If the path looks unexpanded, use the "Base directory for
this skill" that Claude Code printed at the top of this skill. The state lives in
.court/<run>/state.json in the current directory, and every command after init finds it through
.court/LATEST.
Step 1: size it
Read the flags out of the request. Everything that is not a flag is the case.
| flag | meaning |
| --- | --- |
| --jury N | N jurors, 3 to 12. Default 12. |
| --quick | 6 jurors. |
| --seed S | Fixes which jurors sit on a smaller jury. Default: random, and recorded. |
Run COURT plan with the same flags and tell the user in one line how big the trial is, for example
"12 jurors, 17 sub-agent calls", then start. If this skill fired on its own (the user never asked for
a trial), ask once first and offer --quick.
Sub-agents write into .court/ in the current directory. In the default permission mode that is one
approval per file. Suggest accept-edits mode (Shift+Tab) for the trial. Do not change the user's
settings yourself.
Step 2: write the case file
Sub-agents cannot see this conversation. The prosecutor, the defense, every juror and the judge
know only what is in the case file, so write .court/case.md to stand on its own:
- First line: the case in one sentence, in the user's own words where you can ("Quit my job to sell candles on Etsy full time").
- Then everything the user told you that matters: numbers, audience, budget, timeline, what they have already tried, constraints.
- Do not add facts the user never gave, and do not write your own opinion of the idea into it. A case file that leans one way decides the trial before it starts.
Step 3: open the trial
COURT init --case-file .court/case.md [--jury N | --quick] [--seed S]
Step 4: the trial
Always drive it with COURT next. It reads the files on disk and tells you the next phase and the
exact command. The phases run in this order: opening, rebuttal, jury, judge.
Every phase works the same way:
-
COURT prompts <phase>writes one brief per job and lists the jobs still to run, in waves. -
Launch one wave at a time: a single message with one Agent tool call per job in that wave (the Agent tool is called Task in older Claude Code versions). Each call is:
subagent_type:general-purposedescription:court <job id>prompt:Read <brief path> and follow it exactly. It is your whole brief.
Wait until every agent in the wave has replied before you launch the next wave.
-
After the last wave, run
COURT next. If an output is missing it sends you back to the same phase, andpromptsthen lists only the missing jobs. Re-run those once. If a juror fails twice, write the single lineNO VOTEinto its file (COURT check jurylists it) and move on. Never write a vote, a statement or a judgment yourself.
Step 5: the verdict
When COURT next says the trial is over:
COURT render
It counts the votes, writes VERDICT.md into the run folder and prints it. Show the user the verdict
line, the vote table and the judge's sections exactly as written. Then add at most two lines of your
own: the single condition for acquittal you would start with, and the path to the full trial.
Rules for you, the clerk:
- Never change, soften or re-count the verdict. A guilty verdict is useful information, not bad news to cushion.
- Never add praise the jury did not give.
- If the user disagrees with the verdict, offer a retrial with the changes from "Conditions for acquittal" written into a new case file. Do not argue for either side yourself.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
