Content
63%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 clean, brief template README with a sensible four-step workflow and no padding. It is weakened by non-executable guidance — no render command, and the `source/` bundle it instructs the reader to open is missing from the skill directory — which undercuts both actionability and the disclosure structure.
Suggestions
Ship the `source/` bundle (at minimum `source/index.html`) or correct the path; the workflow's first step is unactionable without it.
Replace the vague render step with the concrete renderer invocation or command (and note how to select 16:9 / 9:16 / 1:1 and duration), which would lift actionability toward executable guidance.
Drop the intro line that duplicates the frontmatter description verbatim, and add a short post-render verification step (confirm output duration/fps or preview a frame) to give the workflow a checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence — no explanation of GSAP, WebGL, or video rendering — and the format spec ('16:9, 9:16, 1:1, default 15s, 60fps') is dense useful signal. The only trimmable token is the intro line, which repeats the frontmatter description verbatim, matching 'minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place level 5. | 4 / 5 |
Actionability | Steps are directionally concrete ('Read source/index.html', 'Replace the sample copy', 'do not introduce external network assets') but the critical render step is a pointer with no command ('Render to MP4 via the html-video / HyperFrames renderer'), and the referenced `source/index.html` bundle is absent from this skill's directory, so nothing is directly executable as written. This lands at 'some concrete guidance but incomplete; missing key details' rather than the mostly-executable level 4. | 3 / 5 |
Workflow Clarity | The four-step workflow (read source, swap copy, keep self-contained, render) is a clear, correctly ordered sequence with an explicit preservation constraint ('keep the motion timing and visual signature intact'). It lacks any checkpoint for verifying the render succeeded or previewing the output — minor validation gaps, since the operation is non-destructive and the feedback-loop cap does not apply. | 4 / 5 |
Progressive Disclosure | Sections are well organized and the body is short, but the primary deep content lives in `source/index.html` ('A HyperFrames-ready HTML + CSS + GSAP motion composition, bundled under `source/`') and that directory does not exist in the skill bundle — the one reference the skill depends on is broken/unverifiable. Per the guideline to score against the actual bundle structure, this is 'some structure but references not verifiable / not clearly organized' rather than the well-signaled, resolvable references of level 4. | 3 / 5 |
Total | 14 / 20 Passed |