Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, highly actionable CLI reference with real commands and useful operational notes, appropriate for a short single-purpose skill. The main weaknesses are cosmetic-to-minor: plain-text section headers instead of markdown headings, an unexpanded '--action' placeholder, and purely implicit sequencing with no error-recovery guidance.
Suggestions
Format section titles as markdown headers ("## Setup", "## Common commands", "## Notes") so the structure renders correctly.
Replace the "--action '...'" placeholder with a concrete executable example, e.g. "camsnap watch kitchen --threshold 0.2 --action 'camsnap snap kitchen --out motion.jpg'".
Add one line on error recovery or expected output (e.g. what "camsnap doctor --probe" reports on failure) so users can diagnose a failed capture.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is a usable command, flag, path, or constraint ("Requires `ffmpeg` on PATH", "Prefer a short test capture before longer clips") with zero padding and no explanation of concepts Claude already knows. Anchor 4's "minor instances of over-explanation" does not apply — nothing could be trimmed without losing information. | 5 / 5 |
Actionability | Commands are concrete and mostly copy-paste ready ("camsnap snap kitchen --out shot.jpg", "camsnap clip kitchen --dur 5s --out clip.mp4"), but "--action '...'" is an unexpanded placeholder and the config.yaml format is referenced without being shown. Not 5 because one listed command is not executable as written; well above 3 since real flags and example values are given throughout. | 4 / 5 |
Workflow Clarity | Setup (add camera) preceding usage commands gives a clear implied sequence, and "camsnap doctor --probe" plus "Prefer a short test capture before longer clips" act as validation checkpoints — anchor 4. Not 5 because the sequence and checkpoints are implicit (no explicit workflow or error-recovery guidance); the destructive/batch cap does not apply since capture operations are non-destructive. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines with no need for external references, and content is split into logical sections (Setup, Common commands, Notes) — but the section titles are plain text rather than "##" markdown headers, so the structure will not render and navigation suffers. Anchor 4 fits: good placement with a minor organization gap; not 5 because the unformatted headers break the otherwise well-organized layout. | 4 / 5 |
Total | 17 / 20 Passed |