Content
100%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.
The body is an exemplar of skill writing: two runnable examples, exact commands, a validated workflow with a feedback loop and publish-safety check, dense version-pinned facts with zero padding, and clean offloading of exhaustive syntax and CI detail to two well-signaled reference files. The 'Mistakes that cost time' and 'Older versions' sections preempt real failure modes without verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence: it carries only version-specific facts (the 0.12.1 baseline, the '.tape' suffix rule, 'VHS_PUBLISH' semantics, ffmpeg exit-code behavior) and non-obvious pitfalls, with no explanation of concepts Claude already knows. Time-sensitive version information is properly quarantined in a dedicated 'Older versions' section, and the longest prose passage (the build-sentinel rationale) devotes each sentence to a distinct failure mode, so it fits the 'every token earns its place' anchor rather than the level below. | 5 / 5 |
Actionability | It provides two complete, executable tapes — a self-contained demo.tape that 'needs no project binary or fixture' and a full TUI recording tape — plus exact commands with flags ('vhs validate ./*.tape', 'env -u VHS_PUBLISH vhs demo.tape'). The examples are copy-paste ready and cover the common cases (bash demo and alt-screen TUI), matching the fully-executable top anchor. | 5 / 5 |
Workflow Clarity | The 4-step workflow sequences writing, validation ('run vhs validate demo.tape'), a publish-safety check ('Check that VHS_PUBLISH is unset, then render'), and output inspection, with an explicit error-recovery feedback loop ('If a command fails or a wait times out, fix the command or expected text and rerun validation and rendering'). This matches the anchor requiring explicit validation steps and feedback loops; the destructive/batch cap does not apply since rendering is non-destructive and the one risky side effect (accidental public upload) has its own checkpoint. | 5 / 5 |
Progressive Disclosure | The body is a clear overview with two well-signaled, one-level-deep references that both exist and deliver exactly what is promised: 'Read references/tape-syntax.md for every Set option … and the full action list' and 'Read references/ci.md before adding vhs to a pipeline: it covers guarding vhs validate …, the pinned charmbracelet/vhs-action step, and what to pin for golden-file and screenshot fixtures'. Exhaustive Set/action tables and CI details are correctly kept out of the main file, and neither reference nests further references, matching the top anchor for clean structure and easy navigation. | 5 / 5 |
Total | 20 / 20 Passed |