Content
65%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 exemplary in token efficiency — lean, non-padded, and free of concepts Claude already knows — but its workflow is not fully executable: the render step has no concrete command, there is no validation checkpoint, and the `source/index.html` bundle it depends on is absent from the package. Structure and brevity are strengths; executability is the weakness.
Suggestions
Add the actual render command for step 4 (e.g. the specific html-video/HyperFrames CLI invocation with output path, format, and fps flags) so the workflow is copy-paste executable.
Insert a validation checkpoint between edit and render, e.g. 'Preview the animation in a headless browser and confirm timing/16:9 framing before rendering', with a fix-and-retry loop.
Ship the `source/` bundle (index.html and its CSS/GSAP assets) with the skill, or correct the referenced path, so step 1 resolves to a real file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is ~30 lean lines with zero padding: no explanation of what HTML/CSS/GSAP or MP4 rendering is, and every line either states the artifact ("renders deterministically to MP4 / WEBM at 16:9, default 10s, 30fps"), constrains the work ("do not introduce external network assets"), or sequences a step. Matches 'Lean and efficient; assumes Claude's competence; every token earns its place'. | 5 / 5 |
Actionability | Steps 1-3 are concrete directives ("Read `source/index.html`", "Replace the sample copy... keep the motion timing and visual signature intact"), but step 4 ('Render to MP4 via the html-video / HyperFrames renderer') gives no executable command, and the referenced `source/` bundle does not exist in the package, so step 1 cannot actually be executed. Fits 'Some concrete guidance but incomplete; missing key details'; not a 4 because the key execution details (the render command, the actual bundle) are missing rather than minor gaps. | 3 / 5 |
Workflow Clarity | The four steps are clearly sequenced but contain no validation or verification checkpoint (nothing like 'confirm the render completed at 30fps' or a preview/inspect step), and the final render step lacks its command. Fits 'Steps listed but validation gaps; sequence present but checkpoints missing'. Not a 4: there are no checkpoints at all, not 'most checkpoints present with minor gaps'. The destructive/batch cap does not apply since the operation is non-destructive template editing. | 3 / 5 |
Progressive Disclosure | The body itself is well organized into short sections with a single clearly signaled one-level-deep reference ("Read `source/index.html`"), but scoring against the actual bundle structure, that path does not exist — there is no `source/`, `references/`, `scripts/`, or `assets/` directory, so navigation from the SKILL.md immediately dead-ends. Fits 'Some structure but could be better organized; references present but not clearly signaled' in effect (the reference is signaled but broken). Not a 4 because a missing referenced bundle is a navigation failure rather than a minor organization gap. | 3 / 5 |
Total | 14 / 20 Passed |