From kit
Reviews and promotes skill drafts staged by skill-curator. Lists proposals, vets them against quality criteria, then promotes or rejects them.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kit:skill-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
skill-curator's background reviewer stages skill drafts under `~/.claude/skill-proposals/`. It
skill-curator's background reviewer stages skill drafts under ~/.claude/skill-proposals/. It
NEVER writes ~/.claude/skills/. This skill is the human gate that promotes a vetted draft into the
live library. bin/skill-review (from lib/skill-curator/, put it on PATH or invoke by its full
path) is the only writer of ~/.claude/skills/.
List the staged drafts:
skill-review list # tab-separated: <slug>\t<description>
If "(no staged drafts)", stop and say so.
For each draft, read ~/.claude/skill-proposals/<slug>/SKILL.md and vet it. Run the
superpowers:writing-skills checklist (this skill does NOT reimplement it , delegate):
description a real trigger (what class of task + when), so a future agent matches it?promote also refuses a
draft that still contains one, but check first.references/ add, than a new
skill? If so, reject and patch by hand.Decide per draft (always show the user the draft and your read before acting):
skill-review promote <slug> (moves it into ~/.claude/skills/<slug>/; refuses to
overwrite a live skill without --force).skill-review reject <slug> (moves it to _rejected/, recoverable, never deleted).Report what was promoted vs rejected, and any draft you left staged for the user to decide.
--force overwrite a live skill without explicitly confirming with the user first.~/.claude/skills/. The reviewer cannot (it runs with
no write tool). Keep it that way.auto_promote config knob (default OFF) can auto-pass the lowest-risk class only
(a references/ add to an existing umbrella) via skill-review auto; everything else is manual.npx claudepluginhub dwarvesf/dwarves-kit --plugin kitCreates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.