Upgrade them for Opus 5.
Skills written for older models over-explain, over-constrain, and patch weaknesses Opus 5 doesn’t have — so they now make it worse. This one prompt audits every skill you’ve got, then puts the ones you pick through a blind-judged gauntlet: upgraded if that honestly wins, retired if it doesn’t. Paste it into Claude Code and hit run.
Audit every Claude Code skill currently installed and autonomously upgrade the ones I select through a Skill Upgrade Gauntlet.
First, find and inspect every installed skill across every available scope. Preserve an immutable copy of every original skill and its resources.
Before beginning any upgrades, create a live local HTML dashboard showing the complete skill inventory, what each skill does, where it came from, whether it can be edited, and any dependencies or overlaps you discover. Open the dashboard on my computer and give me its link in Claude Code.
The dashboard is view-only. I…
That’s the first 7%.
Unlocked for — copy it and go.
How to run it #
Open Claude Code
On the machine where your skills live — .claude/skills
in a project, or ~/.claude/skills
. Opus 5 or Fable 5 both work.
Paste it, pick your skills
It inventories every skill, opens a live dashboard, and asks which ones to put through the gauntlet. Reply with your picks in Claude Code.
Let it run
Each pick is blind-benchmarked against the original until it’s honestly better — upgraded or retired, with the evidence on the dashboard. It tells you when it’s done.
Before you run it: make sure your skills folder is committed to git or backed up. The prompt tells the agent to keep everything reversible, but your own backup is the one that counts.
Under the hood it’s a Gauntlet Loop: every skill gets its own builder and a separate blind critic, and a skill only survives if it beats bare Opus 5 at its own job.
Want a Gauntlet Loop prompt for anything else? The generator writes one for free.