review-skill
Review Skill
Audit an existing skill against the write-a-skill guidelines and report issues with suggested fixes.
Quick start
/review-skill path/to/skill-name/ — review a skill by path
/review-skill skill-name — review an installed skill by name
Workflow
1. Locate the skill
If a path is given, read the files there. If a name is given, search ~/.claude/skills/ and installed plugin directories for a matching skill folder.
2. Read all skill files
Read SKILL.md and any accompanying files (REFERENCE.md, EXAMPLES.md, scripts, etc.).
3. Evaluate against guidelines
Check each criterion and mark pass/fail:
Description
- Present and under 1024 chars
- Written in third person
- First sentence states what it does
- Includes "Use when [specific triggers]"
- Triggers are specific enough to distinguish from similar skills
SKILL.md structure
- Has valid frontmatter (
name,description) - Under 100 lines
- No time-sensitive information (dates, versions, URLs that may rot)
- Consistent terminology throughout
- Concrete examples included
- References to other files are one level deep (no deep nesting)
File structure
- Additional content split into separate files when SKILL.md > 100 lines
- Scripts present only for deterministic, repeated operations
- No unnecessary files
4. Report findings
Use the report format from REPORT.md.
5. Offer to fix
Ask the user: apply suggested fixes automatically, or just report?
More from kenlck/skills
bug-fix
Structured bug fixing with reproduction, root cause analysis, fix design, regression risk analysis, and quality review. Only invoke this skill when the user explicitly asks to use it by name (e.g. "use bug-fix", "run bug-fix") or clearly requests a structured/systematic bug fixing process. Do not invoke for general bug reports, error messages, or broken behavior — handle those directly without this skill.
18simplify
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
17feature-dev
Optimized guided feature development with deep requirement drilling, codebase understanding, and design-quality frontend implementation. Use this skill whenever the user wants to build or implement a feature — whether they say "let's build X", "add feature Y", "implement Z", "I want to create", "can we add", or any variation. This is the go-to skill for any non-trivial software feature work. Prefer this over a plain coding response whenever the feature has more than one moving part.
17code-review
Review changed code for bugs, simplicity, security, and convention adherence using parallel reviewer agents. Use when the user asks to review code, review a PR, check quality, or wants a second pair of eyes before merging.
17grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
16frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
14