Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill body is an exceptionally actionable, well-sequenced workflow with strong validation gates. Its two weak spots are verbosity in the rationale/anecdote prose and a progressive-disclosure structure whose craft/*.md reference targets are missing from the bundle.
Suggestions
Ship the referenced craft/ files (headlines.md, rules.md, export.md, ship.md, evaluate.md, reference-gallery.md, redesign.md, svg-animation.md, operating-mode-question.md) or inline their essential content — the body repeatedly delegates to files that do not exist in the bundle.
Tighten the gate rationale paragraphs (e.g. §1.8, §1.8b, §2.6) by collapsing the repeated 'scope is deliberately narrow…' justifications into a single stated principle; the current restatements pad the token budget.
Consolidate the scattered incident anecdotes (VeloxDB, clawd-on-desk, obsidian-skills, Terminal.Gui) into a single 'past failures' reference file so the main flow stays lean while retaining the lessons.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body (~570 lines) is dense with rationale and incident anecdotes — e.g. multi-paragraph explanations of why each gate's scope is narrow and repeated restatements of the same craft rules. Most of the craft knowledge is non-obvious and earns its place, but there is visible prose padding that could be tightened without losing meaning. | 2 / 3 |
Actionability | Highly executable: concrete commands ('ffmpeg -i recording.mov -vf "fps=0.5,scale=1400:-1"'), exact Puppeteer flags ('deviceScaleFactor: 2', explicit clip), a 6-section index.html structure, and precise file-path conventions. Copy-paste ready guidance throughout. | 3 / 3 |
Workflow Clarity | A clearly sequenced five-phase pipeline with explicit validation gates (Gate A §1.8, Gate B §2.6), a convergence checklist (§1.6), an entry gate before export (§4.0), and a defined one-retry feedback loop on failure — matching the level-3 anchor with checkpoints and error-recovery loops. | 3 / 3 |
Progressive Disclosure | The body is well-organized by phase and signals one-level-deep references to craft/*.md files (headlines.md, rules.md, export.md, ship.md, evaluate.md, reference-gallery.md, redesign.md, svg-animation.md), but the craft/ directory is absent from the actual bundle — only scripts/ exists. Per the guideline to score against the actual bundle structure, a large share of the promised detailed material points at non-existent files, which is a broken reference structure rather than clean one-level disclosure. | 2 / 3 |
Total | 10 / 12 Passed |