Skip to main content
ZICQ

Skills ZICQ category:Design skill-review

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'.

2057 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

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

When to use it

" info in the body instead of the description?

How agents load it

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

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

SKILL.md & Agent activation

Official spec ↗
name
skill-review
description
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'.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 1
  • references/review-criteria.md

These 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 ↗

Install this skill

Skills CLI ↗

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.

Ask your Agent to install

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.

Full package on GitHub ↗

Install from the terminal · Skills CLI

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.

Readable layout

name: skill-review description: "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'."

Skill Review

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.

Workflow

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)

Step 1: Load Target ⚠️ REQUIRED

Identify the skill to review. Accept:

  • Explicit path: /skill-review path/to/skill
  • Current directory context: if user is already in a skill folder
  • Skill name: search within the workspace for matching skill directory

Read the full SKILL.md and list all files in the skill directory. Count SKILL.md line count — this is a key metric.

Step 2: Analyze ⚠️ REQUIRED

Load references/review-criteria.md for detailed criteria. Evaluate the skill across five dimensions:

2.1 Structure Compliance

Questions to answer:

  • Does the directory follow the standard layout (SKILL.md, scripts/, references/, assets/)?
  • Is SKILL.md under 500 lines?
  • Does frontmatter contain only name and description (plus optional allowed-tools, license, metadata)?
  • Are there unnecessary files (README.md, CHANGELOG.md, LICENSE duplicates)?
  • Are references organized by domain with one level of nesting?

2.2 Description Quality

Questions to answer:

  • Does the description include concrete trigger keywords and phrases?
  • Does it use keyword bombing (multiple phrasings of the same intent)?
  • Is it self-contained — can a router understand what this skill does without reading the body?
  • Does it avoid putting "When to Use" info in the body instead of the description?
  • Would a user's natural language query match this description?

2.3 Workflow Design

Questions to answer:

  • Is there a trackable checklist with copy-paste-friendly format?
  • Are critical steps marked with ⚠️ REQUIRED or ⛔ BLOCKING?
  • Are there confirmation gates before destructive/generative operations?
  • Is the workflow linear and progressive, or does it jump around?
  • Are sub-steps used where complexity demands it?

2.4 Token Efficiency

Questions to answer:

  • Is there an Iron Law or core constraint at the top?
  • Does SKILL.md only contain what Claude doesn't already know?
  • Are references loaded progressively (on-demand) rather than all upfront?
  • Are instructions in imperative form (not "You should...")?
  • Are scripts executed rather than loaded into context?
  • Is there redundancy between SKILL.md and reference files?

2.5 Anti-Pattern Detection

Check for these known bad patterns:

  • Vague directives ("ensure good quality", "make it better")
  • Placeholder residue (TODO, FIXME, xxx, TBD)
  • Over-specification of things Claude already knows
  • No anti-patterns section (model has no guardrails against lazy defaults)
  • Missing pre-delivery checklist (no concrete verification criteria)
  • Giant monolithic SKILL.md with no reference extraction
  • Instructions that describe WHAT rather than constrain HOW

Step 3: Report ⚠️ REQUIRED

Output Format

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:

  • What: the specific issue found
  • Where: file and location
  • Fix: concrete actionable change (show before/after when helpful)

Group suggestions by dimension only if there are many (5+). Otherwise present as a flat prioritized list.

Tone

  • Direct, constructive, collegial
  • Lead with genuine strengths — not filler praise
  • Suggestions are opportunities, not failures
  • If the skill is already solid, say so briefly and move on

Anti-Patterns for This Skill

  • Giving vague praise ("nice structure!") without quoting what specifically works
  • Listing problems without actionable fixes
  • Reviewing against personal taste rather than the documented principles
  • Suggesting over-engineering for simple skills
  • Flagging missing features that the skill intentionally omits (check if simplicity is the point)

Related skills

Design

Automation Workflows

Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to autom…

Design

Ui Ux Pro Max

UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, info…

Design

Frontend Design

Expert frontend design guidelines for creating beautiful, modern UIs. Use when building landing pages, dashboards, or any user interface.

Design

N8n Workflow Automation

Designs and outputs n8n workflow JSON with robust triggers, idempotency, error handling, logging, retries, and human-in-the-loop review queu…