video · remocn — Claude Code skill: what it does, how to install
Builds complete Remotion videos from project briefs using remocn components, timed storyboards, and frame checks. Handy for launch demos and release changelogs.
MIT 482 installs ★ 1,831 updated 2026-10-23
npx skills add Remocn/remocn --skill video -a claude-codeWhat video does
This skill guides an AI assistant through producing an entire Remotion video from brief to export. It inspects repository files like package.json and README, selects an archetype recipe, and drafts a structured frame budget. The workflow pauses for your approval on the storyboard table before generating any code.
Once approved, it executes setup.mjs to configure @remocn registry paths, downloads motion blocks via shadcn add, and writes the composition into src/videos/<slug>/index.tsx. It inspects visual quality by rendering test stills or delegating to the scene-reviewer agent prior to handoff.
You must load the companion remocn skill first because it stores the core archetype blueprints. Remocn Studio is not supported on Windows, which limits rendering on that platform to standard CLI commands.
What it helps with
- Generate product launch and feature announcement videos from project docs
- Plan frame budgets and scene timing before writing React components
- Set up Remotion projects with the remocn component registry
- Catch visual animation glitches by reviewing rendered still frames
Example prompts for the agent
- Create a 30-second product demo video based on our README and landing page copy
- Plan a storyboard and Remotion composition for our new CLI tool release
- Build an open-source showcase video using remocn components
How to install video
1Skills CLI (Vercel)
npx skills add Remocn/remocn --skill video -a claude-code2Manually: put the files in place
~/.claude/skills/video/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/video/
1Skills CLI (Vercel)
npx skills add Remocn/remocn --skill video -a codex2Manually: put the files in place
.agents/skills/video/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Remocn/remocn --skill video -a cursor2Manually: put the files in place
.cursor/skills/video/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Remocn/remocn plugins/remocn/skills/video2Manually: put the files in place
.github/skills/video/SKILL.md1Skills CLI (Vercel)
npx skills add Remocn/remocn --skill video -a gemini-cli2Platform CLI
gemini skills install https://github.com/Remocn/remocn --path plugins/remocn/skills/videoManually: put the files in place
.devin/skills/video/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Remocn/remocn --skill video -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about video
How to install video in Claude Code?
Run npx skills add Remocn/remocn --skill video -a claude-code. The skill definition will be placed in ~/.claude/skills/video/SKILL.md.
What does the video skill do?
It orchestrates end-to-end video production with Remotion. The skill drafts a storyboard table, installs remocn components through shadcn, and writes the composition code.
What prerequisites does this skill require?
It depends on the base remocn skill for archetype blueprints and styling rules. If your repository lacks Remotion, the skill initializes one via npx create-video@latest.
Source text
SKILL.md · MIT
---
name: video
description: >
Make a complete Remotion video from a short brief with remocn components: pick the archetype, plan
a storyboard with frame budgets, install the components, compose the scenes, check the render and
offer to open the project in Remocn Studio. Use when the user asks for a whole video (product demo,
launch, feature announcement, changelog, OSS showcase, CLI demo, testimonials, year in review,
pricing, logo bumper), not a single component.
---
# Make a video with remocn
The brief: $ARGUMENTS
Load the `remocn` skill before anything else. It carries the conventions this flow relies on (the two
component tiers, Canvas & timing, design defaults) and the recipes in its
`references/archetypes/`. This skill is the order of work; that one is the knowledge.
Work through the steps in order. Don't skip the storyboard confirmation: it is the cheapest point to
change direction.
## 1. Read the brief and the project
- Pull the content from the brief and the repo before asking: `README`, landing copy,
`package.json`, recent releases. Ask only for what is still missing, in one message, and fall back
to honest placeholders rather than blocking.
- Pick the archetype from the `remocn` skill's `references/archetypes/index.md` and read that
recipe. Its content contract tells you what to gather; its duration variants set the target length
when the brief doesn't.
## 2. Plan the storyboard
Plan it in the format of [references/storyboard.md](references/storyboard.md).
- If the `remocn:video-director` agent is available, hand it the brief, the gathered content, the
archetype and the target length, and take its storyboard back.
- Otherwise plan it yourself: shortlist from `https://remocn.dev/llms-components.txt`, read the
`.md` page of every pick, and budget each beat as the format describes.
Show the storyboard to the user **as it is in that format**: the header lines, the table with all its
columns, the install line and the missing-content list. Don't retell it as prose or reshape the
table. A few lines above it on the choices you made are fine. Then **wait for a yes or for
changes**, and apply changes to the table, not straight to code.
## 3. Set up the project
Find out which case you are in:
- **No Remotion project yet** (no `remotion` dependency in `package.json`): create one with
`npx create-video@latest --yes --blank <folder>`, then work inside it. Remotion is a prerequisite
of remocn; this is the only time you create it.
- **An existing Remotion project**: work in it as it is. Don't restructure the user's code.
Then, in both cases:
1. Make `shadcn add` work in the project:
```bash
node "${CLAUDE_SKILL_DIR}/scripts/setup.mjs" <project-root>
```
(Outside Claude Code: `scripts/setup.mjs` next to this file.) `shadcn init` refuses Remotion
projects, and Remotion's bundler ignores tsconfig paths, so the script writes `components.json`
with the `@remocn` registry, adds the `@/*` path to `tsconfig.json`, and resolves the same alias
in `remotion.config.ts`. Each step is skipped when the project already has it; relay any
`warning` in the result.
2. Make the project open in Remocn Studio as-is by following the `studio` skill's **Prepare** step.
For an existing project, say which files these two steps will touch and ask before running them.
## 4. Install and compose
1. Run the storyboard's install line: `npx shadcn add @remocn/<a> @remocn/<b> ...`. Dependencies
install transitively.
2. Write the video as **`src/videos/<slug>/index.tsx`**. This layout is what Remocn Studio scans,
and the scan registers it as a Remotion composition with id `<slug>`:
```tsx
export const meta = {
durationInFrames: 1356, // Planned total from the storyboard
fps: 30,
height: 720,
width: 1280,
};
export default function LaunchVideo() {
return (/* the <TransitionSeries> from the storyboard */);
}
```
Scenes that grow past a screen of code go next to it in the same folder
(`src/videos/<slug>/scenes/hook.tsx`), never beside the video folder. Optional extra exports:
`defaultProps` and a zod `schema`, both forwarded to the composition.
3. Use the exact props from each component's docs page. Sequence lengths come from the storyboard,
not from guesses.
4. Typecheck (`npx tsc --noEmit`) and list compositions (`npx remotion compositions`). The slug
must be in the list. Fix every error before moving on. A missing declaration file for a
component's dependency is fixed with `npm i -D @types/<package>`, not with `any`.
## 5. Check the render
The agent that writes the code never sees the frames, so look at them.
- If the `remocn:scene-reviewer` agent is available, hand it the composition id, the storyboard and
the project path. Apply the fixes it returns, then ask it to check again. Stop after **two** review
rounds and tell the user what is still open, if anything.
- Otherwise render stills yourself at the start, the middle of the motion and the end of the hold of
each beat (`npx remotion still <slug> out/review/<beat>-<frame>.png --frame=<n>`), open the images,
and check them against the `remocn` skill's quality bar (`references/anatomy.md` §3).
## 6. Hand off
1. Tell the user how to preview (`npx remotion studio`) and render
(`npx remotion render <slug> out/<slug>.mp4`).
2. Offer **"Open in Remocn Studio to tweak and export?"** and, on a yes, follow the `studio` skill's
**Open** step. Remocn Studio is a desktop app for tuning elements visually and exporting mp4;
skip the offer on Windows, where it isn't available.
© Remocn · MIT · Remocn/remocn
Similar skills
All skills for Frontend and UI →video by other authors comes first.