Content
85%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 exemplary lean overview: executable commands, pointers to full documentation, no padding, and unambiguous per-task routing. Its two real gaps are the bare commands lacking a fully-argumented example for the common render case, and a broken in-bundle reference — the transparent-videos.md file it links to is missing from the bundle.
Suggestions
Ship the referenced `transparent-videos.md` in the bundle (e.g. under `references/`) or inline its key guidance, since the body links to a file that is not present.
Add one fully-argumented example, e.g. `npx remotion render src/index.ts <composition-id> out/video.mp4`, alongside the bare commands to cover the common non-default render case.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~15-line body gives the two commands directly ("npx remotion render", "npx remotion still"), links to the full option lists for everything else, and contains zero background explanation or padding — every token earns its place and it fully assumes Claude's competence. There is nothing to trim, so it matches the lean anchor exactly. | 5 / 5 |
Actionability | Both commands are real, copy-paste-runnable CLI invocations, but they are bare: no example with the arguments the common case needs (entry point, composition id, output path, e.g. `npx remotion render src/index.ts MyComp out/video.mp4`). This matches "Mostly executable guidance; concrete code or commands with minor gaps"; it is not 5 because the commands only cover the zero-configuration default case. | 4 / 5 |
Workflow Clarity | This is a simple single-action skill where each task maps to one unambiguous command — video to `npx remotion render`, still to `npx remotion still` — with transparent video explicitly routed to its own section; the simple-skill exception applies and the actions are unambiguous. Rendering a video is neither destructive nor a batch operation, so no validation cap applies. | 5 / 5 |
Progressive Disclosure | The body itself is well-structured and clearly signals a one-level-deep reference ("See [Transparent videos](./transparent-videos.md) for rendering out a video with transparency"), but the referenced file does not exist in the bundle — there is no `references/` directory and no `transparent-videos.md` anywhere, only `assets/remotion-icon.png`. The organization gap is more than minor (the pointer resolves to nothing), so it falls to "Some structure but could be better organized" rather than 4. | 3 / 5 |
Total | 17 / 20 Passed |