Write or refactor editable Remotion markup with appropriate tracks, shared timing boundaries, and connected compositions.
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/remotion-new-markup/SKILL.mdRead editable timeline structure before choosing components and wrappers. Start with what should be edited together, then choose independent tracks or consecutive sequences. The guide includes the complete interactive element, scene, parent, and registration.
For footage with synchronized captions or overlays, also read editable video timelines. For extracting a group into its own timeline, use connected compositions.
Call useCurrentFrame() in the smallest component that needs the frame to
render. Keep composition and scene components that arrange clips and tracks
free of frame subscriptions when only a soundtrack volume, animated title, or
overlay needs to change. Extract that item into a component defined at module
scope, and read the frame there instead of passing it down from the parent.
This prevents that animation from re-rendering unrelated clips and scenes on
every frame.
Keep editable interpolate() calls inline on the animated item's props. For
example, a Soundtrack component can read useCurrentFrame() and return an
Audio with volume={interpolate(frame, ...)}, while the composition only
renders <Soundtrack /> alongside its scenes. Prefer a static value when the
output does not actually vary with the frame.
Preserve the existing timing boundary when extracting: placing the hook inside
a Sequence or a timed component changes its frame coordinates. Keep trims,
offsets, volume envelopes, and animation keyframes on the same clock, or adjust
the keyframes deliberately to preserve the edit. A plain React component is
enough for this render boundary; add timeline wrappers only for editing needs.
Verify a structural change in the full composition and any standalone views. Preserve the existing edit, and distinguish useful markup grouping from Studio's row expansion and layout behavior.
remotion-dev/remotion
cc7879e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.