Content
56%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 skill body is well-structured with a clear philosophy and mostly concrete, executable steps for the understand-write-narrate-audio pipeline. Its two real weaknesses are redundancy across the Philosophy, Script structure, and Narration tips sections, and a render step whose referenced tooling does not match the bundled scripts.
Suggestions
Fix the render step to match the actual bundle: replace ./video/render.sh with the real script (scripts/make-video.sh) and correct its documented inputs, or add the video/ tooling the body describes.
Explain how slide-NN.png images are produced (or reference a script that makes them), since the bundled make-video.sh requires them but no step covers slide image generation.
Merge the duplicated guidance: consolidate "explain the why" / "name files" advice into the Script structure section and fold API configuration into Step 3 rather than repeating it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with real specifics, but key guidance is repeated: "Explain the why, not just the what" and "name files/functions" each appear three times (Philosophy, Code walkthrough guidelines, Narration writing tips), the File organization section restates the tmp/out layout already given up top, and API configuration re-states the GEMINI_API_KEY/voice details from Step 3. | 3 / 5 |
Actionability | Steps 1-4 give executable commands and a complete narration.json example, but Step 5 instructs running "./video/render.sh" which does not exist in the bundle (the actual script is scripts/make-video.sh, taking slide-NN.png files the skill never explains how to produce), so the final, most fragile step is not executable as written. | 3 / 5 |
Workflow Clarity | A clear 5-step sequence with stated dependencies, validation built into audio generation (duration sanity checks with automatic retries), and an end checklist including output verification. Minor gaps: no checkpoint for slide/manifest correctness before the render step, and the render step itself is misdocumented. | 4 / 5 |
Progressive Disclosure | Sectioning is good and references/manifest.md is a real, well-signaled one-level reference, but the body and its file-organization tree reference an entire video/ directory (render.sh, build.mjs, hyperframes.json) that is absent from the actual bundle, leaving the reader navigating to files that do not exist. | 3 / 5 |
Total | 13 / 20 Passed |