Content
78%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 content is highly actionable and token-efficient: concrete rules with executable good/bad code examples throughout, and it includes validation where it matters (connected compositions). Its main weakness is navigation: two of the referenced reference files are missing from the actual bundle, undermining the progressive-disclosure structure.
Suggestions
Add the missing timeline-structure.md and inline-effects.md files to the bundle (e.g. in references/), or remove/fix the links pointing to them, since the skill directs the reader to read timeline-structure.md before writing any scene.
Consider moving the 16-row schema field type table into a reference file (e.g. references/schema-types.md) and keeping only the most common types inline with a pointer.
Give the sibling-skill references (../remotion-markup/video-editing.md, ../remotion-markup/connected-compositions.md) a brief label of what each covers so readers can decide whether to load them without opening the files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with Studio-specific rules Claude would not know, each earning its place with good/bad code pairs and a properly flagged deprecated alias ("text-content is a deprecated alias"), though a few passages (the childrenSchema explanation, the schema fragment listing) could be trimmed. | 4 / 5 |
Actionability | Every rule comes with copy-paste-ready executable code, contrasting ❌ examples, install commands for all four package managers, and exact statements of which interpolate() input forms are supported ("Bare identifiers ... multiplication with a number such as 2 * fps ... are supported"). | 5 / 5 |
Workflow Clarity | There is a clear entry directive ("Before writing a scene or refactoring its layers, read editable timeline structure") and a validation checkpoint for connected compositions ("Validate both its standalone view and the full parent timeline"), but the rest of the body is a set of parallel style rules rather than a sequenced workflow. | 4 / 5 |
Progressive Disclosure | References are well-signaled and one level deep with context for each, but the bundle contains only SKILL.md and assets/remotion-icon.svg — the referenced files timeline-structure.md and ./inline-effects.md do not exist in the bundle, so the primary "read this first" pointer is broken; the 16-row schema type table is also inline API-reference material. | 3 / 5 |
Total | 16 / 20 Passed |