skill-reviewlisted

Review and promote skill drafts that skill-curator staged from past sessions. Use when the user runs /skill-review, says "review my skill drafts", "promote a staged skill", or asks what skills the self-improvement loop proposed. Lists drafts under ~/.claude/skill-proposals/, runs the writing-skills quality bar on each, then promotes the approved ones into ~/.claude/skills/ or rejects them.
dwarvesf/dwarves-kit · ★ 11 · Code & Development · score 77

Install: claude install-skill dwarvesf/dwarves-kit

# skill-review (the promote gate) 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/`. ## Flow 1. **List** the staged drafts: ```bash skill-review list # tab-separated: <slug>\t<description> ``` If "(no staged drafts)", stop and say so. 2. **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): - Is the name class-level (not a PR number, error string, codename, or today-only artifact)? - Is the `description` a real trigger (what class of task + when), so a future agent matches it? - Is it a genuine reusable pattern, or environment-dependent / a complaint that will rot into a refusal? Drop the latter. - **Secret scan**: confirm no token / key / credential is in the body. `promote` also refuses a draft that still contains one, but check first. - Would this be better as a PATCH to an existing umbrella, or a `references/` add, than a new skill? If so, reject and patch by hand. 3. **Decide per draft** (always show the user the draft and your read before acting): - Approve -> `skill-review promote <slug>` (moves it in