judge-composition
Design and run reliable Codex judges with explicit rubrics, blinded evidence, calibration cases, and auditable verdicts.
Skill by lilCnid
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/lilcnid-judge-composition-89e846
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: design, agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Node.js package
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/judge-composition
What's inside
- Skill name
judge-composition- Description
- Design and run reliable Codex judges with explicit rubrics, blinded evidence, calibration cases, and auditable verdicts.
- License
- CC-BY-4.0
- Instructions
- 116 lines in SKILL.md · view on GitHub
Before installing
- Ships executable scripts
Files (22)
- LICENSE.md
- SKILL.md
- openai.yaml · agents/
- AMBIENT.md · references/
- COMPOSITION_FROM_PRIMITIVES.md · references/
- DOUBTS_WORKSPACE.md · references/
- FOUR_JUDGE_BASIC_MODEL.md · references/
- FOUR_JUDGE_DESIGN.md · references/
- JUDGE_COMPOSITION_CEREMONY.md · references/
- JUDGE_COMPOSITION_GAME.md · references/
- JUDGE_CONVOCATION_DESIGN.md · references/
- JUDGE_INTAKE_DESIGN.md · references/
- PROGRAM_CONTEXT.md · references/
- README.md · references/
- RECONCILIATION.md · references/
- STANDING_MODEL.md · references/
- failure-modes.md · references/
- judge_panel.ts · references/
- registry-parameters.md · references/
- standing-model-reframing.md · references/
- substrate-and-cases.md · references/
- thesis-and-provenance.md · references/
SKILL.md (first lines)
# Judge Composition
A judge is an evidence procedure, not a persona. Define what is being judged,
what evidence is admissible, and how observations become a verdict before any
candidate output is scored.
## 1. Frame the decision
Write:
```text
Object: {Artifact_Or_Behavior_Under_Judgment}
Decision: {Pass_Fail_Rank_Or_Score}
Audience: {Who_Uses_The_Verdict}
Cost asymmetry: {False_Pass_Cost} versus {False_Fail_Cost}
```
The cost asymmetry determines thresholds and whether abstention is allowed.
Separate hard gates from preferences: a valid schema may be mandatory while
tone is graded.
## 2. Build an observable rubric
Each criterion needs four parts:
| Field | Meaning |
|---|---|
| `criterion` | One behavior or property |
| `evidence` | What the judge may inspect |
| `scale` | Anchored outcomes, not adjectives |
| `weight/gate` | Decision effect |
Prefer binary gates for objective constraints and short anchored scales for
quality. Avoid overlapping criteria that count the same defect twice. If a
criterion cannot point to observable evidence, revise or remove it.
Use `prompt-engineering` and `hypershot-protocol` when available to structure
the judge prompt without content-heavy answer examples. When those skills are
not available in the current session, disclose that once and use their shipped
source as the fallback.
## 3. Protect independence
The judge may receive:
- candidate artifact or stable path;
- task specification and admissible source material;
- rubric and output schema;
- case identifier and runtime metadata.
Do not supply the author's preferred verdict, suspected defect, hidden chain of
reasoning, or another judge's score. When using a delegated judge, spawn with
`fork_turns: "none"`. Remember that the filesystem remains shared; restrict
allowed paths and keep author notes elsewhere when blindness matters.
## 4. Calibrate before trusting
Use a compact calibration set:
- a clear pass;
- a clear fail;
- a boundary case;
- a case with tempting but irrelevant surface quality.
Concrete calibration examples belong to the evaluation data layer, not to a
standing skill or system instruction. Record disagreements. If two competent
judges read a criterion differently, the rubric is under-specified.
## 5. Execute and aggregate
Use one judge for cheap deterministic gates. Use multiple independent judges
when the criterion is subjective or the decision is costly. Judges must not see
one another's verdicts before returning.
Aggregate by criterion, not by rhetorical confidence:
1. Apply hard gates.
2. Compare evidence for disagreements.
3. Re-run only ambiguous criteria with a clarified rubric.
4. Report unresolved uncertainty instead of manufacturing consensus.
The parent agent owns the final synthesis and verifies any claim addressable by
files, tests, or primary sources.
## Output contract
```json
{
"verdict": "pass|fail|abstain",
"criteria": [
{
"name": "{Criterion}",
"result": "{Anchored_Result}",
"evidence": ["{Direct_Observation}"],
"uncertainty": "{None_Or_Named_Gap}"
}
],
"blocking_failures": ["{Failed_Gate}"],
"summary": "{Decision_Reason_Without_Hidden_Reasoning}"
}
```
Adapt the schema to the task, but preserve evidence per criterion and an
explicit abstention path when measurement can fail.
## Failure modes
- **Persona judging:** “be a strict expert” without operational criteria.
- **Expectation leakage:** telling the judge what it should discover.
- **Aesthetic substitution:** rewarding polish when correctness is the target.
- **Double counting:** multiple criteria penalize one underlying defect.
- **Context inheritance:** a supposedly independent judge receives the author's
conversation or notes.
- **Unmeasured pass:** missing evidence is silently interpreted as success.From lilCnid/dovetail-codex, CC-BY-4.0.
More from lilCnid/dovetail-codex
- 0.526score
spark-steering
lilCnid
Diagnose a stuck or drifting Codex workflow by locating the wrong control surface, lifecycle, or owner before adding tools or permissions.
SkillBFreshness: BClaude Code +9 - 0.526score
subagent-composition
lilCnid
Partition a Codex task into bounded parallel investigations, choose delegated context deliberately, coordinate shared files, and consolidate evidence.
SkillBFreshness: BClaude Code +9 - 0.526score
upsum
lilCnid
Close a work session by appending a durable record, rebuilding a fixed-size recency-weighted summary, carrying open work forward, and running repository checks.
SkillBFreshness: BClaude Code +9 - 0.526score
self-play
lilCnid
Evaluate prompts, skills, policies, or generated artifacts through clean-room Codex runs, adversarial cases, and evidence-backed revision.
SkillBFreshness: BClaude Code +9 - 0.526score
better-skill-creator
lilCnid
Create or revise Codex skills with precise routing, progressive disclosure, UI metadata, native validation, and behavior-focused evaluation.
SkillBFreshness: BClaude Code +9 - 0.516score
hypershot-protocol
lilCnid
Design prompt templates and model-facing artifacts with abstract structural examples that prime form without importing task-specific content.
SkillBFreshness: BClaude Code +9 - 0.496score
prompt-engineering
lilCnid
Structure or improve prompts, templates, agent instructions, and output schemas using clear hierarchy, semantic boundaries, placeholders, and attention control.
SkillBFreshness: BClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Sep 3, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- CC-BY-4.0
- Repository
- github.com/lilCnid/dovetail-codex
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from lilCnid
- 0.574score
better-skill-creator
lilCnid
Use this skill for anything to do with authoring, fixing, or measuring Claude skills.
SkillBFreshness: B★ 4Claude Code +9 - 0.569score
subagent-composition
lilCnid
Compose a Claude Code sub-agent on the fly — persona, inherited-context transfer, tool budget, and return contract — as either an ephemeral Agent-tool call or…
SkillBFreshness: B★ 4Claude Code +9 - 0.569score
self-play
lilCnid
Run a clean-room self-play search over a problem space you have not solved yet — an AlphaGo-shaped loop over text where isolated sub-agent players (a blind…
SkillBFreshness: B★ 4Claude Code +9 - 0.569score
upsum
lilCnid
Close a working session: append what happened to a growing record, re-derive a fixed-length summary that holds the newest entries at full detail and collapses…
SkillBFreshness: B★ 4Claude Code +9 - 0.569score
judge-composition
lilCnid
Compose an adaptable four-role judge panel (grounding, coherence, corroboration, audit) to evaluate a candidate for promotion — a belief, claim, record entry…
SkillBFreshness: B★ 4Claude Code +9 - 0.564score
hypershot-protocol
lilCnid
Meta-prompting technique using zero-contamination structural examples.
SkillBFreshness: B★ 4Claude Code +9
Cite this page
judge-composition skill. Agent Mart. https://agentmart.dev/skills/lilcnid-judge-composition-89e846 (last updated 2026-10-24)