Content
43%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 a token-lean topic index with clean section structure, but it contains no executable guidance and its three local references point to files missing from the bundle, leaving the Vue/Angular/Svelte sections as the only resolvable pointers (to external URLs). As written, the skill tells Claude what topics exist but not how to do anything with them. The structure is the right shape for an overview skill; the substance is absent.
Suggestions
Ship the referenced files (framework.md, player.md, rendering.md) in the bundle or replace the dead links with inlined essential guidance — as delivered, every local link in the skill is broken.
Replace the filler intro with a minimal quick-start, e.g., a template clone command (`npx create-video@latest`) and a basic composition or <Player> snippet, so the body has at least one concrete, executable step.
Sequence the sections as an explicit build workflow (choose template → build composition → preview with Player → choose a rendering target) with a verification step such as running a local render (`npx remotion render`) to confirm the output before deploying.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dominated by lean one-line section links, but the opening ("One can build apps with Remotion. It is possible to have a simple form and hook it up to a render, or have a complex video editor.") is trimmable filler that neither instructs nor adds anything Claude doesn't know. This is a minor, localized instance of padding, matching "Efficient; minor instances of over-explanation that could be trimmed" rather than score 3, where unnecessary explanation is more pervasive. | 4 / 5 |
Actionability | There is no code, command, or concrete step anywhere in the body — every section is a pointer such as "See [Choosing a framework](framework.md) for help choosing a template or framework", and the locally referenced files do not exist in the bundle. These are high-level hints without the specific steps to execute, matching score 2; not 1 because the pointers are at least topic-specific and would be followable if the files were present. | 2 / 5 |
Workflow Clarity | The sections imply a rough progression (choose template/framework → Player preview → rendering → alternate frameworks) but no steps are actually listed, nothing is sequenced or numbered, and there are no checkpoints or validation. This matches "Rough sequence present but many gaps; steps poorly defined"; it cannot reach 3 because that anchor requires steps to be listed. | 2 / 5 |
Progressive Disclosure | The written structure is the right shape — clearly signaled, one-level references such as "See [Player](player.md)" and "See [Rendering](rendering.md)" — but scoring against the actual bundle structure per the guideline, framework.md, player.md, and rendering.md do not exist (the bundle contains only assets/remotion-icon.png), so every local navigation target is broken and the skill is effectively an empty index. That falls below the 4 anchor ("references mostly clear" assumes they resolve); it stays at 3 rather than 2 because the overview's organization and signaling themselves are genuinely good and the Vue/Angular/Svelte sections do resolve to real external URLs. | 3 / 5 |
Total | 11 / 20 Passed |