Content
71%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 lean, highly actionable best-practices reference: terse rules, executable tsx examples, and explicit good/bad comparisons, with a genuinely well-specified pre-compose procedure. Its main weaknesses are a duplicated Maps section, small correctness slips in the examples (undefined fps, typo-level errors like 'they need to refactored'/'timelien'), and a reference graph that points to ~28 files not present in this bundle, which makes the promised progressive disclosure unusable as shipped.
Suggestions
Remove the duplicate 'Maps' section (keep the later, more detailed one) and consolidate the many one-line 'See X.md' sections into a single grouped 'Topic guides' list to cut tokens.
Fix the example defects: define fps via useVideoConfig() in the first FadeIn example, and correct typos such as 'they need to refactored', 'timelien', and 'useCurrenFrame'.
Ship the referenced files (transitions.md, effects.md, ffmpeg.md, 3d.md, etc.) in the bundle or restructure them under references/ so the body's navigation resolves.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is terse and assumes Claude's competence ("Keep the interpolate() call inline in the style prop", "Use scale, translate, rotate CSS properties over transform") with no padding explaining known concepts, matching the 'efficient; minor instances that could be trimmed' anchor. It is not a 5 because the 'Maps' section appears twice ("See [Remotion Maps](./remotion-maps/SKILL.md) if wanting to include maps" and the later expanded 'Maps' section) and several one-line pointer sections could be consolidated. | 4 / 5 |
Actionability | Guidance is mostly executable: complete tsx examples with real props (e.g. the trimBefore/trimAfter/loop snippets, the Example scene), a concrete command ('npx remotion add @remotion/media'), and explicit do/don't comparisons ('👍 Inline editable keyframes... 👎 Non-inline values and transform strings'). It falls short of 5 because the first FadeIn example uses fps without defining it (no useVideoConfig), the delaying/trimming snippets use '{/* ... */}' placeholders, and the pre-compose workflow describes the procedure in prose rather than showing a minimal before/after example. | 4 / 5 |
Workflow Clarity | The single real multi-step process (the Studio pre-compose request in 'Connected compositions') is well sequenced: find the selected markup, extract into a named component, render one direct instance under a Sequence, register the Composition with dimensions/fps/duration/defaultProps, and 'If the selection or a behavior-preserving connected composition is unclear, ask for clarification instead of guessing'. It is not a 5 because there is no explicit validation/verification checkpoint in that flow (the 'Visual checks' section suggests Studio preview but does not tie it into any procedure), and most other sections are reference material rather than sequenced workflows. | 4 / 5 |
Progressive Disclosure | The body itself is a well-signaled overview with one-level-deep pointers ('See [transitions.md](transitions.md) for scene transition patterns', 'load [./sfx.md](./sfx.md)'), which resembles the 4-5 anchors. However, scored against the actual bundle, none of the ~28 referenced files (transitions.md, effects.md, ffmpeg.md, etc.) exist in this package — only assets/remotion-icon.svg is present — so the navigation the body promises is unresolvable, and the duplicated 'Maps' section hurts organization. This places it between 'references present but not clearly signaled' (3) and the broken-structure level below. | 3 / 5 |
Total | 15 / 20 Passed |