Remotion renderer that converts JSON timeline specs into video compositions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionjson-render-remotionExecute the skills CLI command in your project's root directory to begin installation:
Fetches json-render-remotion from vercel-labs/json-render and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate json-render-remotion. Access via /json-render-remotion in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
14.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
14.0K
stars
Remotion renderer that converts JSON timeline specs into video compositions.
import { Player } from "@remotion/player";
import { Renderer, type TimelineSpec } from "@json-render/remotion";
function VideoPlayer({ spec }: { spec: TimelineSpec }) {
return (
<Player
component={Renderer}
inputProps={{ spec }}
durationInFrames={spec.composition.durationInFrames}
fps={spec.composition.fps}
compositionWidth={spec.composition.width}
compositionHeight={spec.composition.height}
controls
/>
);
}
import { defineCatalog } from "@json-render/core";
import {
schema,
standardComponentDefinitions,
standardTransitionDefinitions,
standardEffectDefinitions,
} from "@json-render/remotion";
export const videoCatalog = defineCatalog(schema, {
components: standardComponentDefinitions,
transitions: standardTransitionDefinitions,
effects: standardEffectDefinitions,
});
import { z } from "zod";
const catalog = defineCatalog(schema, {
components: {
...standardComponentDefinitions,
MyCustomClip: {
props: z.object({ text: z.string() }),
type: "scene",
defaultDuration: 90,
description: "My custom video clip",
},
},
});
// Pass custom component to Renderer
<Player
component={Renderer}
inputProps={{
spec,
components: { MyCustomClip: MyCustomComponent },
}}
/>
{
"composition": { "id": "video", "fps": 30, "width": 1920, "height": 1080, "durationInFrames": 300 },
"tracks": [{ "id": "main", "name": "Main", "type": "video", "enabled": true }],
"clips": [
{ "id": "clip-1", "trackId": "main", "component": "TitleCard", "props": { "title": "Hello" }, "from": 0, "durationInFrames": 90 }
],
"audio": { "tracks": [] }
}
| Component | Type | Description |
|---|---|---|
TitleCard |
scene | Full-screen title with subtitle |
TypingText |
scene | Terminal-style typing animation |
ImageSlide |
image | Full-screen image display |
SplitScreen |
scene | Two-panel comparison |
QuoteCard |
scene | Quote with attribution |
StatCard |
scene | Animated statistic display |
TextOverlay |
overlay | Text overlay |
LowerThird |
overlay | Name/title overlay |
| Export | Purpose |
|---|---|
Renderer |
Render spec to Remotion composition |
schema |
Timeline schema |
standardComponents |
Pre-built component registry |
standardComponentDefinitions |
Catalog definitions |
useTransition |
Transition animation hook |
ClipWrapper |
Wrap clips with transitions |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
davila7/claude-code-templates
remotion-dev/skills
supercent-io/skills-template
shreefentsar/remotion-video-toolkit
diffusionstudio/lottie
pproenca/dot-skills
We added json-render-remotion from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
json-render-remotion has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in json-render-remotion — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
json-render-remotion fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added json-render-remotion from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in json-render-remotion — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
json-render-remotion fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
json-render-remotion has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: json-render-remotion is focused, and the summary matches what you get after install.
json-render-remotion reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 31