Conciseness

The body is lean and assumes Claude's competence: it never explains what Remotion is, just gives the commands ("npx remotion render", "npx remotion still"), one fully-specified example ("npx remotion render [composition-id] out/frames --frames=0,30,90 --image-format=png"), and pointers to the official option docs. Every token earns its place, matching the anchor-5 example's economy.

Actionability

All guidance is copy-paste executable: the render, still, and --frames commands are real CLI invocations, the frames example includes composition id, output path, and flags, and authoritative links are given for the full option lists. It covers the common cases (render a video, render a still, render selected frames) exactly as the anchor-5 description requires.

Workflow Clarity

This is a simple, single-purpose skill where the action is unambiguous — run the one CLI command for the desired output type — which the guidelines explicitly allow to score 5 without a multi-step workflow. The three variants (render/still/frames) are cleanly separated under clear headings; no destructive or batch operation requires a validation checkpoint, so the cap does not apply.

Progressive Disclosure

The structure itself is clean (two well-labeled sections, a clearly signaled one-level-deep link for the advanced transparent-video case), but scoring against the actual bundle shows the sole reference — "See [Transparent videos](./transparent-videos.md)" — points to a file that does not exist anywhere in the skill directory (no references/ folder; only assets/remotion-icon.svg is bundled). A broken primary reference defeats the navigation it signals. It is not a 2 because nothing that belongs in a separate file is inlined and nothing is deeply nested; it is not a 4 because the one reference present cannot actually be followed, which is more than a minor organization gap.

Specificity

The description states only a single generic action — "Export a Remotion video" — which is structurally parallel to the anchor-2 example "Processes PDF files": the domain (Remotion) is named but the actions are minimal and generic. It is not a 3 because anchor 3 requires 1-2 concrete capabilities (e.g. rendering videos, exporting stills, transparent video exports), and here only one bare verb is offered with no elaboration.

Completeness

It has a clear, if terse, "what" ("Export a Remotion video") but no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because there is zero "when" guidance — not even a weakly implied one.

Trigger Term Quality

"Remotion" and "video" are genuinely relevant, natural keywords, but common variations users would say are missing: "render", "MP4", "animation", "still", "frame". This matches anchor 3 ("some relevant keywords but missing common variations or synonyms"), not 2, because "Remotion video" is specific rather than generic filler, and not 4 because the most likely user phrasing — "render" — is absent entirely.

Distinctiveness Conflict Risk

"Remotion" is a highly distinctive niche keyword that uniquely identifies this skill and virtually no other skill would trigger on it, matching anchor 5 (clear niche with distinct triggers; minimal conflict risk). It is not a 4 because the overlap risk with generic video skills is avoided by explicitly scoping to "a Remotion video" rather than video work broadly.