Import Canvas Capture
Import a recorded Remotion Canvas Capture into a project without Studio interactions using the internal experimental-codemod command. Use when adding a capture file as an editable composition with cursor keyframes.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Import Canvas Capture when an AI agent needs a reusable SKILL.md workflow for this job: Import a recorded Remotion Canvas Capture into a project without Studio interactions using the internal experimental-codemod command. Use when adding a capture file as an editable composition with cursor keyframes.
When not to use it
Skip Import Canvas Capture when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/import-canvas-capture # Save SKILL.md to ~/.claude/skills/import-canvas-capture/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/import-canvas-capture/SKILL.md. For a shared project, commit the folder at .claude/skills/import-canvas-capture/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Import Canvas Capture skill for this task: Locate the recorded capture file and the target Remotion project. The original. Confirm any required inputs or files before making changes.
What supports this recommendation?
83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 92/100
- Practical detail
- 92/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Import Canvas Capture
This is an internal, unstable workflow. Keep this skill in `.agents/skills`; do not distribute it through `packages/skills` or document the command as a stable API.
## Workflow
1. Locate the recorded capture file and the target Remotion project. The original recording must contain embedded `REMOTION_CAPTURE_DATA` metadata; a converted video that has lost this metadata cannot be imported. 2. Inspect the project to find the TypeScript file containing its composition registrations (usually `src/Root.tsx`). Choose an unused composition ID. 3. From the target project's root, run:
```sh bunx remotion experimental-codemod add-canvas-capture /absolute/path/capture.webm \ --composition-file src/Root.tsx \ --id MyCapture ```
When developing this command in the monorepo, build the CLI first with `bun run build`, then invoke the local CLI from the target project's root:
```sh node /absolute/path/to/remotion/packages/cli/remotion-cli.js \ experimental-codemod add-canvas-capture /absolute/path/capture.webm \ --composition-file src/Root.tsx --id MyCapture ```
4. Review the reported source files and public asset. The importer generates a component beside the registration file, registers it, copies the video to the public directory, and installs missing `@remotion/media` and `@remotion/mac-cursors` dependencies at the project's Remotion version. Studio does not need to be running. Existing Studio sessions pick up source changes through their file watchers; this operation does not enter Studio's undo stack. 5. Report the composition ID and changed files to the user.
## Options and conflicts
- Defaults match Studio's capture import: 1920×1080, 60 fps, and duration rounded up from the recording. Pass `--width`, `--height`, or `--fps` to override them. Recorded video dimensions remain independent from composition dimensions. - `--public-dir` overrides the configured public directory. `--package-manager` selects the dependency installer. - `--dry-run` parses the recording and generates source changes without installing dependencies or writing project files. The programmatic result includes the proposed source changes. - The registration file is resolved relative to the project root; the CLI capture path is resolved relative to the current working directory. - Existing component files and conflicting public assets are rejected. If the recording is already in the public directory, pass that file as the input to reuse it. Otherwise rename the input or select another composition ID; do not overwrite an existing asset or component to bypass an error.
## Programmatic access
Use `CliInternals.importCanvasCapture` from `@remotion/cli`. It is internal and unstable. Its inputs are `captureFile`, `compositionFile`, `compositionId`, `remotionRoot`, `publicDir`, `fps`, `width`, `height`, `packageManager`, `logLevel`, and `dryRun`. Supply `null` for default directory, dimensions, frame rate, and package manager. File paths are resolved relative to `remotionRoot`.
The result contains the composition ID, source and asset paths, composition metadata, and codemod changes. Pass `dryRun: true` to inspect changes in memory.
Intended uses
- Locate the recorded capture file and the target Remotion project. The original
- Inspect the project to find the TypeScript file containing its composition
- From the target project's root, run:
- Review the reported source files and public asset. The importer generates a
- Report the composition ID and changed files to the user.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.