judge
Skill1 starsChanged 4 months agoMITView on GitHub
Scores parallel implementations with a 5-criteria worksheet (fitness, justified complexity, readability, robustness, maintainability; 25 points max), hard gates on score=1 or Fitness delta>=2, and Speed-Run efficiency tiebreakers. Invoked automatically by speed-run:showdown and speed-run:any-percent at Phase 4; not for direct user invocation.
12 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- fcsouza/agent-skillstheir own version, first seen Nov 15, 2026
- joi-fairshare/agentic-workflowtheir own version, first seen Nov 14, 2026
- JHostalek/dotclaudetheir own version, first seen Nov 1, 2026
- ilang-ai/autocodetheir own version, first seen Nov 1, 2026
- jthorare/agentic-workflowtheir own version, first seen Oct 25, 2026
- simota/agent-skillstheir own version, first seen Oct 23, 2026
Used with
Projects with it also use review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- 2389-research/test-kitchen★ 429% same
Wrote their own version · 11
- nudgebee/nudgebee★ 525same name
- ilang-ai/autocode★ 106same name
- simota/agent-skills★ 99same name
- fcsouza/agent-skills★ 26same name
- rvdbreemen/adr-kit★ 13same name
- JHostalek/dotclaude★ 11same name
- Walllmat/verdict★ 4same name
- joi-fairshare/agentic-workflow★ 3same name
- jthorare/agentic-workflow★ 3same name
- vanderheijden86/showdown-claude-skill★ 1same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- any-percentSkill
- showdownSkill
- speed-runSkill
- turboSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Fitness Gate: If Fitness Δ ≥ 2 between impls → Higher fitness WINS immediately
- Distinctive: line 32
Critical Flaw: If ANY criterion = 1 → That impl is ELIMINATED
- Distinctive: line 47
When total scores are tied or within 1 point, prefer the implementation that:
- Distinctive: line 66
Read: all implementation code (should already be in context)
- Distinctive: line 72
CRITICAL: Use integer scores only (1-5).
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Speed-Run Judge
Score implementations using the 5-criteria framework. Fill out ALL sections exactly as shown.
Terminology: This skill uses "impl" but works for both:
- Showdown: runner-1, runner-2, runner-3 (same design, different implementations)
- Any%: variant-a, variant-b (different approaches/designs)
REQUIRED OUTPUT FORMAT
See references/scorecard-template.md for the complete output template. Do not summarize or abbreviate any section.
Scoring Reference
Scores Meaning
| Score | Meaning |
| 5 | Excellent - exceeds expectations |
| 4 | Good - fully meets requirements |
| 3 | Adequate - core works, some gaps |
| 2 | Poor - significant issues |
| 1 | Critical flaw - disqualifying |
Hard Gates (Automatic)
- Fitness Gate: If Fitness Δ ≥ 2 between impls → Higher fitness WINS immediately
- Critical Flaw: If ANY criterion = 1 → That impl is ELIMINATED
Fitness Gate Interpretation
The Fitness Gate triggers the same way in both contexts, but means different things:
| Context | What Fitness Δ ≥ 2 Means |
| Showdown | One runner deviated from or misunderstood the design. All runners should have similar Fitness since they're implementing the same spec. A large gap is a red flag. |
| Any% | One approach genuinely solves the problem better. Different approaches can legitimately have different Fitness. A large gap means one approach is clearly superior. |
In both cases, higher Fitness wins. The interpretation just explains why the gap exists.
Tiebreaker: Speed-Run Efficiency
When total scores are tied or within 1 point, prefer the implementation that:
- Used fewer hosted LLM fix cycles (cleaner contract prompts)
- Had fewer total hosted LLM calls (better task decomposition)
- Generated code faster (simpler, more focused prompts)
This rewards better use of the speed-run pipeline, not just code quality.
Feasibility Red Flags
Check before scoring:
- O(n²) or worse on unbounded data
- Unbounded memory growth
- Self-DDoS patterns (polling, no backoff)
- Missing pagination
- Blocking I/O in hot path
- No error recovery
Process
- Read all implementation code (should already be in context)
- Fill out the worksheet for EACH implementation - do not skip sections
- Fill out the Speed-Run Metrics table
- Check hard gates
- Announce winner with rationale (include token efficiency note)
CRITICAL: Use integer scores only (1-5). Do not use half points like 4.5.
CRITICAL: Fill out every checkbox. Do not summarize or abbreviate the worksheet.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

