skill-reviewer

Based on Anthropic’s Claude Code Skills architecture. A reviewer for the skills you write on that foundation.

You built a skill. You want feedback. You ask a friend. Your friend says: “Looks great! Maybe consider adding tests?” That’s not a review. That’s a hug.

skill-reviewer reads every file, cites specific lines, and separates strengths from weaknesses with severity-rated finding cards. It refuses to hedge: if something is fragile, it’ll say so; if something is unusually well-done, it’ll say that too.

~4 min read · scan the TL;DR if you only have 30 seconds

TL;DR

• What: A Claude Code skill that reviews other Claude Code skills with file:line citations, severity-rated finding cards, and an optional second-opinion challenger pass.
• Why: Polite-by-default feedback ships skills with quiet flaws. skill-reviewer gives you the candid review you’d want before publishing.
• Install: Two /plugin commands in Claude Code (below); then /skill-reviewer is available in any session.
• Try first: /skill-reviewer summary /path/to/some-skill — 5-minute sanity check (TL;DR + top 5 strengths + top 5 weaknesses). Lighter than a full review.
• Example output: a real review of the unforget skill.
• Maturity: v0.3.0; five releases so far; the skill reviews itself after every meaningful edit.

Newer to Claude Code?

A skill is a markdown file Claude Code knows how to run. When you type /skill-reviewer review , Claude follows the instructions in this skill, reads the target skill’s files, and writes you a structured report. You don’t have to memorize anything — the skill tells Claude what to do, you read the report.

A real fragment

This is the top of a real review (skill-reviewer reviewing the unforget skill). It’s the kind of output you’ll get on your own work:

## TL;DR

`unforget` is a Claude Code skill that consolidates deferred work into one
structured UNFORGET.md per project. It's more disciplined than most skills
I've reviewed: thin SKILL.md → fat reference files, deterministic Python
helpers with prose fallbacks, backups before destructive operations, and the
verify-still-open recipe is a genuinely original idea worth generalizing.
The standout strength is structural; the standout weakness is that the
canonical example never demonstrates the project's signature feature.