skill-review

1# Skill Review
2 
3IRON LAW: Be specific and actionable. Never say "could be improved" without stating exactly what to change and why it matters for model output quality.
4 
5## Workflow
6 
7```
8Skill Review Progress:
9 
10- [ ] Step 1: Load Target ⚠️ REQUIRED
11  - [ ] 1.1 Identify skill path
12  - [ ] 1.2 Read SKILL.md and inventory all files
13- [ ] Step 2: Analyze ⚠️ REQUIRED
14  - [ ] 2.1 Structure compliance
15  - [ ] 2.2 Description quality
16  - [ ] 2.3 Workflow design
17  - [ ] 2.4 Token efficiency
18  - [ ] 2.5 Anti-pattern detection
19- [ ] Step 3: Report ⚠️ REQUIRED
20  - [ ] 3.1 Strengths (what's done well)
21  - [ ] 3.2 Suggestions (prioritized improvements)
22```
23 
24## Step 1: Load Target ⚠️ REQUIRED
25 
26Identify the skill to review. Accept:
27- Explicit path: `/skill-review path/to/skill`
28- Current directory context: if user is already in a skill folder
29- Skill name: search within the workspace for matching skill directory
30 
31Read the full SKILL.md and list all files in the skill directory. Count SKILL.md line count — this is a key metric.
32 
33## Step 2: Analyze ⚠️ REQUIRED
34 
35Load references/review-criteria.md for detailed criteria. Evaluate the skill across five dimensions:
36 
37### 2.1 Structure Compliance
38 
39Questions to answer:
40- Does the directory follow the standard layout (SKILL.md, scripts/, references/, assets/)?
41- Is SKILL.md under 500 lines?
42- Does frontmatter contain only `name` and `description` (plus optional `allowed-tools`, `license`, `metadata`)?
43…