Back to Skills

skill-review

Quality review and audit for Claude Code skills. Analyzes skill structure, description quality, workflow design, token efficiency, and anti-patterns against best practices. Use when user wants to review a skill, audit a skill, check skill quality, evaluate a skill, critique a skill, lint a skill, or validate a skill. Triggers: 'review skill', 'audit skill', 'skill quality', 'check my skill', 'evaluate skill', 'skill lint', 'validate skill', 'skill review', 'is this skill good', 'improve this ski

3,839stars340forksUpdated 8/13/2026

Security Assessment

Safe(96/100)
Security Score96/100

About skill-review

Skill Review is a meta-skill for Claude Code that audits the quality of other skills against a documented set of best practices. It solves a concrete authoring problem: skill authors rarely have an objective yardstick for whether a SKILL.md is well-structured, discoverable, and token-efficient, so this skill turns that judgment into a repeatable review process. Its guiding 'Iron Law' is to be specific and actionable, never offering vague feedback without stating exactly what to change and why it matters for model output quality.

The skill drives a three-step workflow: load the target skill and inventory its files, analyze it across five dimensions (structure compliance, description quality, workflow design, token efficiency, and anti-pattern detection), and produce a report of strengths followed by prioritized suggestions. A companion reference file, review-criteria.md, supplies detailed checks for each dimension — such as the 500-line SKILL.md limit, keyword-bombing indicators for descriptions, confirmation-gate requirements before destructive operations, progressive-loading signals, and anti-patterns like vague directives or placeholder residue. Every suggestion is expected to state what the issue is, where it lives, and the concrete fix.

It is aimed at skill authors, prompt engineers, and teams building libraries of Claude Code skills who want consistent, opinionated quality reviews. Typical uses include linting a newly written skill, auditing an existing one before publishing, or getting a prioritized improvement list. It is read-only guidance that analyzes files and reports findings; it performs no destructive actions.

FAQ

What does this skill actually check?

It evaluates a target skill across five dimensions: directory structure and SKILL.md length, description quality and trigger keywords, workflow design and confirmation gates, token efficiency and progressive loading, and known anti-patterns such as vague directives or placeholder text.

How do I point it at a skill to review?

You can give an explicit path (for example /skill-review path/to/skill), rely on the current directory if you are already inside a skill folder, or provide a skill name so it can search the workspace for the matching directory.

What does the output look like?

A report in two parts: strengths (at least two, quoting specific lines that work) and suggestions sorted by impact, each with the specific issue, its file location, and a concrete actionable fix.

Does it modify or fix my skill automatically?

No. Based on the source it reads SKILL.md and the file inventory and produces a written review; it does not apply changes for you.

What best-practice thresholds does it enforce?

Among others, SKILL.md should be under 500 lines, frontmatter should contain only supported fields, references should be organized with limited nesting and loaded on demand, and critical steps should be marked with required/blocking indicators.

All Files

2 files
references/review-criteria.md3.9 KB
View
SKILL.md4.9 KB
View

Install skill-review

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill