技能复习
- 作者仓库星标 3,526
- 作者仓库 sanyuan-skills
- 领域
- 安全
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @sanyuan0704 · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步:加载目标 ⚠️ 必需
确定要复习的技能。接受:显式路径:`/skill-review path/to/skill` 当前目录上下文:如果用户已位于技能文件夹中 技能名称:在工作区中搜索匹配的技能目录 阅读完整的 SKILL.md 并列出技能目录中的所有文件。计算 SKILL.md 行数——这是一个关键指标。
第 2 步:分析 ⚠️ 必填
加载references/review-criteria.md 了解详细标准。从五个维度评估技能:
# 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)
章节与文件索引
按说明文件中的顺序排列。
第 1 步:加载目标 ⚠️ 必需
第 2 步:分析 ⚠️ 必填
2.1 结构合规性
2.2 描述质量
2.3 工作流程设计
文件/命令 -> /skill-review path/to/skill · name · description · allowed-tools · license · metadata
内容校验值 -> 7e70638ce4f3
当前原文的自动摘译,尚未人工审校。
2.1 结构合规性
要回答的问题:目录是否遵循标准布局(SKILL.md、scripts/、references/、assets/)? SKILL.md 是否低于 500 行? frontmatter 是否仅包含
name和description(加上可选的allowed-tools、license、metadata)?是否存在不必要的文件(README.md、CHANGELOG.md、LICENSE 重复项)?2.2 描述质量
要回答的问题:描述是否包含具体的触发关键字和短语?它是否使用关键字轰炸(同一意图的多个短语)?它是独立的——路由器可以在不阅读正文的情况下理解这项技能的作用吗?它是否避免将“何时使用”信息放在正文中而不是描述中?
2.3 工作流程设计
要回答的问题:是否有具有复制粘贴友好格式的可跟踪清单?关键步骤是否标有 ⚠️ 必需或 ⛔ 阻止?破坏性/生成性操作之前是否有确认门?工作流程是线性且渐进的,还是跳跃式的?