remotion-interactivity
Structures Remotion markup so layers, timing and styles are editable in Remotion Studio
Install / Use
npx skills add remotion-dev/skills --skill remotion-interactivityInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of remotion-interactivity
remotion-interactivity scores 93/100 on our quality scale, 202nd of 1,155 Content & Media skills we index (top 18%).
Its SKILL.md is 19 KB long, well organised into 17 sections with 18 code examples: a thorough specification that gives an agent plenty to work with.
With 4,702 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so remotion-interactivity is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
remotion-interactivity compared with similar skills
All 4 of these similar skills score higher than remotion-interactivity; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| remotion-interactivity (this skill)by remotion-dev | 93 | 4.7k | 53d ago | SKILL.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install remotion-interactivity?
- Run
npx skills add remotion-dev/skills --skill remotion-interactivity. The install tabs above show the steps for each supported agent. - Which AI agents does remotion-interactivity work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is remotion-interactivity safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is remotion-interactivity still maintained?
- The repository was last updated about 2 months ago, so remotion-interactivity is actively maintained.
Skill content
View source on GitHubname: remotion-interactivity description: Structure Remotion markup for interactivity version: 4.0.531
By writing Remotion markup in a specific way, the Remotion Studio is able to recognize the structure of the code and makes it interactive:
- Allowing items to be selected by clicking on them
- Allowing drag+drop, resizing and rotation
- Editing the CSS styles
- Making keyframes and easing values editable
If the markup is too complex for the Studio to make it interactive, then the values become grayed out.
Prefer interactive components with their own timelines
Use Interactive.withSchema({wrapInSequence: true}) for custom scenes, cards,
titles, and other visual components whose props should be editable per instance.
Expose meaningful content and appearance controls in an InteractivitySchema.
Keep decorative implementation details inside the component.
The component must accept style and forward it to one visual root. Keep a
shared root when transforms, cropping, or opacity should affect all its layers.
Flatten redundant inner wrappers when their styles can move onto an existing
element without changing layout or animation.
import type React from 'react';
import {Interactive, type InteractivitySchema} from 'remotion';
type LowerThirdProps = {
readonly children: string;
readonly accentColor: string;
readonly style?: React.CSSProperties;
};
const LowerThirdInner: React.FC<LowerThirdProps> = ({
children,
accentColor,
style,
}) => {
return (
<Interactive.Div
style={{
position: 'absolute',
left: 80,
bottom: 80,
display: 'flex',
alignItems: 'center',
gap: 20,
backgroundColor: 'white',
borderRadius: 16,
padding: '20px 32px',
color: 'black',
fontFamily: 'Helvetica, Arial, sans-serif',
fontSize: 48,
fontWeight: 600,
...style,
}}
>
<div
style={{
width: 8,
alignSelf: 'stretch',
borderRadius: 4,
backgroundColor: accentColor,
}}
/>
{children}
</Interactive.Div>
);
};
const lowerThirdSchema = {
children: {type: 'text-content', default: '', description: 'Text'},
accentColor: {
type: 'color',
default: '#0b84f3',
description: 'Accent color',
},
} as const satisfies InteractivitySchema;
export const LowerThird = Interactive.withSchema({
Component: LowerThirdInner,
componentName: '<LowerThird>',
schema: lowerThirdSchema,
wrapInSequence: true,
});
Forwarding the injected style inside the component is required; keep editable
styles inline at the component's call site.
Choose schema fields
Each key in the schema is a prop that Studio can read and edit at the call site.
Props that are not in the schema still work, but are not editable in Studio.
Keys may use dot notation, such as style.color.
| Type | Use for | Keyframable |
| ---------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------- |
| text-content | Text, such as a title | No |
| number | Numbers, with optional min, max, step, integer | Yes |
| boolean | On/off switches | Yes (hold) |
| color | CSS color strings | Yes |
| enum | A choice between variants, each with its own nested schema | Opt-in (hold) |
| array | Lists of numbers, colors, enums and more | No |
| asset | Media sources, with optional assetType | No |
| font-family | CSS font family | No |
| font-weight | Font weight | Yes |
| translate, scale, rotation-css, rotation-degrees, transform-origin | Transforms | Yes |
| uv-coordinate | A normalized [x, y] point on the element | Yes |
| svg-path | SVG path data | Yes |
| remotion-captions | Caption[] data | No |
| hidden | A value kept out of the controls | — |
Every field needs a default and should have a description, which Studio shows as the label.
Set keyframable: false to show a static control.
Expose content and per-instance appearance, such as the text and an accent color.
Do not add fields for style.translate, style.scale, style.rotate, style.transformOrigin and style.opacity: wrapInSequence: true already adds them.
To make CSS properties of the root editable per instance, spread the built-in schema fragments:
const cardSchema = {
...Interactive.textSchema, // style.color, style.fontSize, style.fontWeight, ...
...Interactive.backgroundSchema, // style.backgroundColor
...Interactive.borderRadiusSchema, // style.borderRadius, ...
} as const satisfies InteractivitySchema;
Also available: Interactive.borderSchema, and Interactive.captionsSchema for components that accept captions.
See InteractivitySchema for all options.
Register reusable components as connected compositions
Register substantial scenes and reusable components with their own layers or animation as standalone compositions. Studio calls these connected compositions: they can be opened in their own timeline while sharing the same component implementation with the parent video.
Register the same exported component reference that the parent renders. For the
example above, use component={LowerThird}, not LowerThirdInner or an inline wrapper.
With wrapInSequence: true, no extra <Sequence> is needed for the connection.
import {Composition} from 'remotion';
import {LowerThird} from './LowerThird';
export const RemotionRoot = () => (
<Composition
id="LowerThird"
component={LowerThird}
width={1280}
height={720}
fps={30}
durationInFrames={30}
defaultProps={{
children: 'Jane Doe, Product Designer',
accentColor: '#0b84f3',
}}
/>
);
Choose a unique ID, representative inline defaults, and dimensions, fps, and duration suitable for previewing the component. Registration defaults do not automatically copy props from a parent instance. See connected compositions for registration and extraction details.
Put timing directly on the component
Avoid a separate <Sequence> around one component that already accepts timing
props. Built-in interactive components and custom components made with
wrapInSequence: true can receive name, from, durationInFrames,
trimBefore, playbackRate, and premountFor directly.
<LowerThird
name="Lower third"
from={30}
durationInFrames={90}
accentColor="#0b84f3"
>
Jane Doe, Product Designer
</LowerThird>
When removing a redundant sequence, move its timing and name to the child.
Preserve any existing child timing; do not overwrite or double-apply offsets.
A useCurrentFrame() call inside the component reads its local frame, while a
style expression at the call site still uses the caller's frame. Preserve that
distinction when moving animation styles.
Keep a <Sequence> when it provides shared timing for multiple siblings,
overrides dimensions for useVideoConfig(), or wraps a component that does not
handle timing. Keep <Series.Sequence> for consecutive layout and
<TransitionSeries.Sequence> for transitions; direct from props do not
replace those behaviors.
Give every independently editable item its own JSX node
The Studio edits the JSX source node that created an item. If multiple runtime items come from the same JSX node, they share one source-editing target.
For every composition registration, clip, scene, layer or sequence that should
be editable on its own, write a separate JSX node and keep its editable props
on that node. This applies to <Composition>, <Still>, built-in media
components, <Sequence>, <Series.Sequence>, <TransitionSeries.Sequence>
and custom components.
For example, author an editable timeline like this:
<Series>
<Series.Sequence name="Introduction" durationInFrames={90}>
<Introduction />
</Series.Sequence>
<Series.Sequence name="Demo" durationInFrames={150}>
<Demo />
</Series.Sequence>
</Series>
A .map() or another programmatic loop would create multiple runtime items
from one JSX source node. That is appropriate for repeated output that is
intentionally controlled as one template, such as visualization bars or
particles. It is not appropriate when the instances need independent IDs or
names, props, metadata, timing, ordering, deletion or duplication in the
Studio.
Make an HTML element interactive using Interactive
Every HTML and SVG element (except <Img>, it already is interactive) such as <div> can be turned interactive using Interactive:
<Interactive.Div
name="Greeting card"
style={{fontSize: 80, padding: 24}}
>
Hello
</Interactive.Div>
This allows styles and keyframes to be set in the Studio. Be sensible, if a component has many elements, the timeline might get messy.
Prefer inline text
If text is fixed and only used once, write it directly inside the interactive element instead of extracting it into a constant.
// 👍 Fixed copy stays editable
<Interactive.Div name="Title">
Remotion Best Practices
</Interactive.Div>
Use a prop or variable only when the text is dynamic or reused.
Give interactive elements a descriptive name
Add a name prop to elements to make them easily identifyable.
Avoid computed names, hardcode them.
<>
<Interactive.Div name="Hero title" style={{fontSize: 80}}>
Launch day
</Interactive.Div>
<Img name="Avatar" src="https://remotion.media/image.jpeg" />
<Video name="Background" src="https://remotion.media/video.mp4" />
<Interactive.Div name="Title">
Launch day
</Interactive.Div>
</>
Keep all CSS styles inline
The best way is to just pass a plain object to style - no referring to constants, no object spreading, no math.
<Interactive.Div
style={{
fontSize: 80,
color: 'red',
}}
>
Hello World!
</Interactive.Div>
const baseStyle = useMemo(() => {
return {
fontSize: 12 // ❌ Non-inline styles are not supported
}
}, []);
<Interactive.Div
style={{
...baseStyle, // ❌ Spreading is not supported
color: RED, // ❌ Referring to cons
Truncated for display — read the full file on GitHub.
Related Skills
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
