Content
30%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a generic, empty shell: a vacuous one-line summary, a 'When to Use' clause that references a nonexistent overview, and standard safety boilerplate. Its only virtue is that it is short and well-sectioned; it provides no actionable instruction or workflow.
Suggestions
Replace 'Development skill skill.' and the 'described in the overview' phrasing with the actual instructions or executable examples the skill is meant to deliver.
If the skill is a multi-step process, add a numbered sequence with explicit validation/verification checkpoints; if it is a code skill, include copy-paste-ready examples.
Resolve the dangling reference to an 'overview' — either write the overview content inline or point to a real reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and does not lecture Claude on known concepts, so it is token-efficient; but it is not score 3 because the tokens carry no real instructional value ('Development skill skill.', 'workflow or actions described in the overview' with no actual overview). | 2 / 3 |
Actionability | There is no code, command, or concrete guidance — 'execute the workflow or actions described in the overview' references an overview that does not exist, so it describes rather than instructs. | 1 / 3 |
Workflow Clarity | No steps, sequence, or validation checkpoints are present because the body describes no actual workflow; it matches the 'steps unclear or missing' anchor. | 1 / 3 |
Progressive Disclosure | Under 50 lines with no external references needed and clearly organized sections (## When to Use, ## Limitations); per the simple-skills scoring note, a well-organized short skill with no external references can score 3. | 3 / 3 |
Total | 7 / 12 Passed |