What it does
Quality review and audit for Claude Code skills. Analyzes skill structure, description quality, workflow design, token efficiency, and anti-patterns against best practices
Skills ZICQ category:Design 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 skill'.
Official URL:skills.sh
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
Quality review and audit for Claude Code skills. Analyzes skill structure, description quality, workflow design, token efficiency, and anti-patterns against best practices
" info in the body instead of the description?
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Skill Review; Workflow; Step 1: Load Target ⚠️ REQUIRED; Step 2: Analyze ⚠️ REQUIRED; 2.1 Structure Compliance; 2.2 Description Quality. It includes spec-recommended sections: step-by-step instructions.
File analysis: besides SKILL.md, the body references references/review-criteria.md. Those resources load on demand.
Skill ReviewWorkflowStep 1: Load Target ⚠️ REQUIREDStep 2: Analyze ⚠️ REQUIRED2.1 Structure Compliance2.2 Description Quality2.3 Workflow Design2.4 Token Efficiency2.5 Anti-Pattern DetectionStep 3: Report ⚠️ REQUIREDOutput FormatTone
Source category:skills.sh agent-skill
nameskill-reviewdescriptionreferences/review-criteria.mdThese paths are extracted from the text. Check the upstream package to verify the files exist.
Invocation syntax and available tools depend on your Agent client. Client integration guide ↗
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "skill-review" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-454b48aa8deb9075-Skill-Review.html Save it as .cursor/skills/skill-review/SKILL.md or .claude/skills/skill-review/SKILL.md and keep the frontmatter name and description exactly as-is. This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/sanyuan0704/sanyuan-skills instead of creating only a SKILL.md.
Requires Node.js and npx. First inspect the repository's skill list to confirm the name.
npx skills add 'https://github.com/sanyuan0704/sanyuan-skills' --list
npx skills add 'https://github.com/sanyuan0704/sanyuan-skills' --skill 'skill-review'
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
IRON LAW: Be specific and actionable. Never say "could be improved" without stating exactly what to change and why it matters for model output quality.
Skill Review Progress:
- [ ] Step 1: Load Target ⚠️ REQUIRED
- [ ] 1.1 Identify skill path
- [ ] 1.2 Read SKILL.md and inventory all files
- [ ] Step 2: Analyze ⚠️ REQUIRED
- [ ] 2.1 Structure compliance
- [ ] 2.2 Description quality
- [ ] 2.3 Workflow design
- [ ] 2.4 Token efficiency
- [ ] 2.5 Anti-pattern detection
- [ ] Step 3: Report ⚠️ REQUIRED
- [ ] 3.1 Strengths (what's done well)
- [ ] 3.2 Suggestions (prioritized improvements)
Identify the skill to review. Accept:
/skill-review path/to/skillRead the full SKILL.md and list all files in the skill directory. Count SKILL.md line count — this is a key metric.
Load references/review-criteria.md for detailed criteria. Evaluate the skill across five dimensions:
Questions to answer:
name and description (plus optional allowed-tools, license, metadata)?Questions to answer:
Questions to answer:
Questions to answer:
Check for these known bad patterns:
Present the review in this order:
1. Strengths — What this skill does well. Be specific: quote the actual lines or patterns that work. Minimum 2 strengths, even for weak skills (find what's salvageable).
2. Suggestions — Improvements sorted by impact (highest first). Each suggestion must include:
Group suggestions by dimension only if there are many (5+). Otherwise present as a flat prioritized list.
Design
Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to autom…
Design
UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, info…
Design
Expert frontend design guidelines for creating beautiful, modern UIs. Use when building landing pages, dashboards, or any user interface.
Design
Designs and outputs n8n workflow JSON with robust triggers, idempotency, error handling, logging, retries, and human-in-the-loop review queu…