跳到主内容
智客 ZICQ

技能库 智客分类:设计创意 skill-review

Skill Review

Claude代码技能的质量审查和审计。 对照最佳做法分析技能结构、描述质量、工作流程设计、象征性效率以及防标。 当用户想要审查技能、审计技能、检查技能质量、评价技能、批评技能、插入技能或验证技能时使用。 触发器:"审查技能","审计技能","技能质量","检查我的技能","评价技能","技能提示","验证技能","技能审查","这种技能是好的","改进这种技能".

2057 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

Claude代码技能的质量审查和审计。 对照最佳做法分析技能结构、描述质量、工作流程设计、象征性效率和防标

何时用

" 身体中的信息而不是描述?

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Skill Review、Workflow、Step 1: Load Target ⚠️ REQUIRED、Step 2: Analyze ⚠️ REQUIRED、2.1 Structure Compliance、2.2 Description Quality。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/review-criteria.md,属于带资源的技能包,这些文件按需再读。

官方 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 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

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
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. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 1
  • references/review-criteria.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「skill-review」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-454b48aa8deb9075-%E6%8A%80%E8%83%BD%E5%AE%A1%E6%9F%A5.html
请存为 .cursor/skills/skill-review/SKILL.md 或 .claude/skills/skill-review/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/sanyuan0704/sanyuan-skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/sanyuan0704/sanyuan-skills' --list

npx skills add 'https://github.com/sanyuan0704/sanyuan-skills' --skill 'skill-review'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

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)

相关技能

设计创意

Automation Workflows

设计和实施自动化工作流程,以节省时间和规模化操作作为独家. 用于识别重复任务实现自动化,构建跨工具的工作流程,设置触发器和行动,或优化现有自动化. 包括自动化机会识别,工作流程设计,工具选择(Zapier,Make,n8n),测试,和维护. 触发"自动","自动","工作流程自动…

设计创意

Ui Ux Pro Max

UI/UX设计智能及建筑抛光接口实施指导. 当用户要求UI设计,UX流量,信息架构,视觉风格方向,设计系统/托盘,组件规格,副本/显微镜,可访问性,或生成/critique/refine前端UI(HTML/CSS/JS,React,Next.js,Vue,Svelte,Tailw…

设计创意

Frontend Design

创建美丽现代UI的专家前端设计指南. 在构建起落架页面,仪表板,或任何用户界面时使用.

设计创意

N8n Workflow Automation

设计和输出 n8n 工作流程 JSON 有强力触发器, idempotency, 错误处理, 记录, 重试, 以及 人入"一站"审查队列. 当您需要可审计的自动化时使用.