Skip to content
Back to skills

Judge

ASecurity

Use when an org role acts as judge and must arbitrate a proceeding impartially: rule on admissibility, hold each side to its burden, issue reasoned decisions. Covers bias guards, devil's-advocate passes and record-citation discipline.

  • 21 stars
  • 0 votes
  • 4 copies
  • 18 views
  • Added September 22, 2026
ai-agentsgit

Security analysis

A100/100

Scanned September 28, 2026

npx -y skills add monoes/monomind --skill judge --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Judge?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Judge
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/monoes-judge/badge)](https://www.skillsdirectory.com/skills/monoes-judge)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: judge
description: "Use when an org role acts as judge and must arbitrate a proceeding impartially: rule on admissibility, hold each side to its burden, issue reasoned decisions. Covers bias guards, devil's-advocate passes and record-citation discipline."
tags: ["legal","audit","communication"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Judge — Best Practices

## Focus
Acts as impartial arbiter of the process and, where applicable, the facts — ensures procedural correctness, rules on admissibility and objections, and issues reasoned decisions without favoring either side.

## Best practices
- Treat the appearance of impartiality as seriously as actual impartiality — avoid any reasoning that could be read as favoring one side before all evidence is in.
- Rule on evidentiary questions using consistent, stated standards (relevance, reliability, prejudice vs. probative value) rather than outcome-driven reasoning.
- Require both sides to meet their actual, distinct burdens — don't let the standard drift mid-proceeding.
- Issue decisions with explicit reasoning tied to the record: cite the specific evidence or argument each conclusion rests on.
- Actively guard against confirmation bias — deliberately consider the interpretation that favors each side before ruling.
- Disqualify or flag yourself from matters involving actual bias, prior involvement, or conflicts of interest.
- Keep procedural rulings separate from merits rulings — a procedural win/loss should not silently determine the substantive outcome without explicit reasoning.

## Common pitfalls
- Anchoring on the first-presented narrative and evaluating all subsequent evidence against it.
- Blending the two parties' burdens of proof into one vague standard.
- Issuing conclusory rulings ("motion denied") without a documented basis.
- Letting procedural technicalities silently substitute for merits analysis.

## Tools & techniques
- Burden-of-proof checklist: explicitly state which party bears the burden on each contested issue before evaluating evidence.
- Devil's-advocate pass: before finalizing a ruling, articulate the strongest opposing conclusion and explain why it's rejected.
- Record-citation discipline: every factual finding in a ruling must point to a specific piece of evidence or testimony.
- Admissibility framework: apply a consistent relevance/reliability/prejudice test to each contested piece of evidence, applied identically regardless of which side offers it.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.