Skip to content
Back to skills

Multi Judge Aggregation

ASecurity

Collect independent rankings from multiple judges, aggregate using social choice methods, and identify disagreement hotspots.

  • 417 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added May 27, 2026
research

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill multi-judge-aggregation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Multi Judge Aggregation?

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

Security grade badge for Multi Judge Aggregation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-multi-judge-aggregation/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-multi-judge-aggregation)

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: multi-judge-aggregation
description: Collect independent rankings from multiple judges, aggregate using social choice methods, and identify disagreement hotspots.
execution: tactic
used-by: pairwise-ranking
---

# Multi-Judge Aggregation

Collect independent ballots from multiple judges or perspectives, aggregate them into a consensus ranking using social choice theory, and surface disagreement patterns for further investigation.

## Stages

1. **Collect** — ballot-collection gathers independent rankings from each judge/perspective
2. **Aggregate** — aggregation-method applies social choice method to produce consensus
3. **Audit** — cycle-detection checks for Condorcet cycles in the aggregated preference matrix

## Available SOPs

| Stage | SOP | Input | Output |
|-------|-----|-------|--------|
| Collect | ballot-collection | candidates[], perspectives[] | ballots[] |
| Aggregate | aggregation-method | ballots[], method | consensus_ranking |
| Audit | cycle-detection | comparison_matrix | cycles[], transitivity_score |

## Execution Guidance

- Ensure judges evaluate independently (no anchoring or information leakage)
- Use ≥3 judges for meaningful aggregation
- Default to Schulze method (satisfies many desirable social choice properties)
- Cross-validate with Borda count as sanity check
- Flag pairs where judge agreement < 60% as disagreement hotspots
- If Condorcet cycles exist, report them explicitly — do not silently resolve

## Minimum Yield

- Consensus ranking + disagreement heatmap
- Consensus ranking with method used and confidence
- Disagreement heatmap: for each pair, what fraction of judges agree
- Condorcet winner identification (or explicit statement of cycle)
- Per-judge deviation from consensus (who disagrees most, on what)

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.