New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Court

by sickn33 in sickn33/agentic-awesome-skills

Put an idea on trial: a prosecutor and a defense Claude argue, 12 juror sub-agents vote independently, and a judge reads the verdict and the changes that would flip it.

MITAuto-check passedAgent Workflows

Install Court

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill court -a claude-code

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills court --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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/court .claude/skills/court && 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/

Facts

Skill name
court
GitHub stars
47k
Token cost
~1.5k tokens
SKILL.md length
859 words
Files
3 (incl. scripts, references)
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Put an idea on trial: a prosecutor and a defense Claude argue, 12 juror sub-agents vote independently, and a judge reads the verdict and the changes that would flip it.

  • Works in 5 steps: size it → write the case file → open the trial → …
  • Tasks that involve Subagents
  • SKILL.md covers When to Use This Skill, The tool, Step 1: size it and Step 2: write the case file, plus 6 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Court is an agent skill from sickn33/agentic-awesome-skills. Put an idea on trial: a prosecutor and a defense Claude argue, 12 juror sub-agents vote independently, and a judge reads the verdict and the changes that would flip it.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/jurors.json` and `scripts/court.py`).

It sits in Agent Workflows, covering Subagents. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Subagents

Example prompts

  • “/court”

Requirements

  • Python 3

Workflow steps

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

  1. size it
  2. write the case file
  3. open the trial
  4. the trial
  5. the verdict

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • instagram.com
    • github.com

    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

Court loads about 1.5k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 859 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

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 passed

The automated check found no risky patterns in SKILL.md.

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); the scripts in this folder are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 859 words, ~1,525 tokens.

Download SKILL.mdSave it as .claude/skills/court/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
court
description
Put an idea on trial: a prosecutor and a defense Claude argue, 12 juror sub-agents vote independently, and a judge reads the verdict and the changes that would flip it.
category
productivity
risk
safe
source
community
source_repo
alexyc9381/court-skill
source_type
community
date_added
2026-10-03
author
Alex Chen (@nocodealex)
tags
decision-making, critical-thinking, feedback, subagents, multi-agent
tools
claude
license
MIT

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.

When to Use This Skill

  • Use when the user wants pushback instead of agreement, or says Claude agrees with everything.
  • Use when the user asks "is this a good idea?" about a plan, a purchase, a post, a code plan or a claim.
  • Use when the user says "court", "put it on trial" or "/court".

The tool

Every piece of bookkeeping goes through scripts/court.py in this skill's folder:

bash
python3 "${CLAUDE_SKILL_DIR}/scripts/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.

flagmeaning
--jury NN jurors, 3 to 12. Default 12.
--quick6 jurors.
--seed SFixes 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

bash
COURT init --case-file .court/case.md [--jury N | --quick] [--seed S]
Show full SKILL.md (402 more words)Show less

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:

  1. COURT prompts <phase> writes one brief per job and lists the jobs still to run, in waves.

  2. 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-purpose
    • description: 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.

  3. After the last wave, run COURT next. If an output is missing it sends you back to the same phase, and prompts then lists only the missing jobs. Re-run those once. If a juror fails twice, write the single line NO VOTE into its file (COURT check jury lists 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:

bash
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.

Examples

text
/court Quit my job to sell candles on Etsy full time. I have $8,000 saved and 40 sales so far.
/court --quick The plan you just gave me is the right one.

Limitations

  • The jury is made of language models: treat the verdict as a structured second opinion, not legal, financial or professional advice.
  • The jury only knows what the user wrote; vague cases get vague verdicts.
  • A full trial is 17 sub-agent calls (11 with --quick), and each counts toward the user's Claude plan usage.
  • Runs in Claude Code (it spawns sub-agents and calls its script through ${CLAUDE_SKILL_DIR}).

Source

By Alex Chen (@nocodealex). Original repo with tests and a real example run: https://github.com/alexyc9381/court-skill

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts, references) in skills/court of sickn33/agentic-awesome-skills.

  • SKILL.md
  • references/jurors.json
  • scripts/court.py

Open the folder on GitHubat commit b84d35a

Compare with similar skills

Court 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.

Court compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Court this skillsickn33/agentic-awesome-skills47k—~1.5kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k7 repos~2.8kAutomated safety check: PassApache-2.0
Subagent Driven DevelopmentAsvarox/allkaraoke26138 repos~1.2kAutomated safety check: PassNone
Dispatching Parallel Agentsultralisp/ultralisp25841 repos~1.5kAutomated safety check: PassNone
Reflect on Session Learningscursor/plugins11k5 repos~1.2kAutomated safety check: PassNone
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence

Similar skills

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 38 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • Dispatching Parallel Agents

    ultralisp/ultralisp

    A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    258 GitHub starsUsed in 41 repos~1.5k tokens
    Agent WorkflowsAuto-check passed

  • Reflect on Session Learnings

    cursor/plugins

    Official

    Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.

    11k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • Paseo Advisor Second Opinion

    getpaseo/paseo

    Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed

  • Task Observer

    rebelytics/one-skill-to-rule-them-all

    Monitors task execution for skill improvement opportunities.

    3.2k GitHub starsUsed in 1 repo~11k tokens
    Agent WorkflowsAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo

  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed

  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed

  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about Court

What does Court do?

Put an idea on trial: a prosecutor and a defense Claude argue, 12 juror sub-agents vote independently, and a judge reads the verdict and the changes that would flip it. Court is an agent skill from sickn33/agentic-awesome-skills. Put an idea on trial: a prosecutor and a defense Claude argue, 12 juror sub-agents vote independently, and a judge reads the verdict and the changes that would flip it.

When should I use Court?

Court fits situations like: tasks that involve Subagents.

How do I install Court in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill court -a claude-code`. Or copy the skill folder (skills/court in sickn33/agentic-awesome-skills) into .claude/skills/court in your project. Claude Code loads it when a task matches its description.

How do I install Court in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill court -a codex`. Or copy the skill folder (skills/court in sickn33/agentic-awesome-skills) into .agents/skills/court in your project. Codex loads it when a task matches its description.

Can I use Court 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 sickn33/agentic-awesome-skills --skill court -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/court, .gemini/skills/court, .github/skills/court and .opencode/skills/court in your project.

What does Court need to run?

Going by SKILL.md and its folder, Court needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Court access the network?

SKILL.md names 2 domains. As links in the text: instagram.com and github.com. This is read from the text; nothing was executed.

Is Court safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Court use?

Court is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Court use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 473 tokens, read only when the agent opens those files.

What are the alternatives to Court?

Skills that share tags, products or a category with Court: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Reflect on Session Learnings (cursor/plugins, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Court?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.