cukascukas/claudes-ai-buddies/skills/leaderboard/SKILL.md

leaderboard

Skill9 starsChanged 8 months agoMITView on GitHub

Show ELO ratings leaderboard — per task class or overall

1 other project uses a version of this.

Adopted by

Most recently taken up by

jim540/clawdboard-plugintheir own version, first seen Oct 20, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
jim540/clawdboard-plugin★ 0same name
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 repository11 other files it gives its agents.
- add-buddySkill
- brainstormSkill
- campfireSkill
- codex-reviewSkill
- codexSkill
- forgeSkill
- gemini-reviewSkill
- geminiSkill
- opencode-reviewSkill
- opencodeSkill
- tribunalSkill

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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:
All buddies start at 1200
line 49
Distinctive:
Suggest /forge: if no data exists yet.
line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

/leaderboard — ELO Ratings

Show the persistent ELO ratings leaderboard. Ratings are updated after each /forge run based on who wins and loses.

How to invoke

/leaderboard              # show all task classes
/leaderboard algorithm    # show only algorithm class
/leaderboard bugfix       # show only bugfix class

Step-by-step workflow

Parse optional task class from the user's message.
Run the leaderboard formatter:

# All classes
bash "${CLAUDE_PLUGIN_ROOT}/scripts/elo-show.sh"

# Specific class
bash "${CLAUDE_PLUGIN_ROOT}/scripts/elo-show.sh" --task-class "algorithm"

Present the output to the user. If no data exists yet, explain that ratings start building after the first /forge run.

Task classes

Ratings are tracked per task class (auto-detected from the forge task description):

Class	Keywords
`algorithm`	algorithm, sort, search, scoring, math, compute
`refactor`	refactor, rename, extract, simplify, reorganize
`bugfix`	fix, bug, error, crash, broken, regression
`feature`	add, implement, create, build, feature, new
`test`	test, spec, coverage, assert
`docs`	doc, readme, comment, changelog
`other`	(default)

How ELO works

All buddies start at 1200
K-factor: 32 (configurable)
Winner gains points, loser loses points (zero-sum)
Ratings below 100 are floored
Provisional status for < 10 games

Configuration

Key	Default	Description
`elo_enabled`	`true`	Enable/disable ELO tracking
`elo_k_factor`	`32`	ELO K-factor (higher = more volatile)

Rules

Read-only. This skill only displays ratings, never modifies them.
Suggest /forge if no data exists yet.
Keep it brief. Just show the table, no analysis unless asked.

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free