Complete video editor for maker channels built on Remotion — turns raw phone clips (HEVC, HDR, vertical, variable frame rate) into a YouTube video, with first cut, script and narration (ElevenLabs or Chatterbox, your choice, or your own voice), word-by-word captions, hook, highlights, zoom, timelapse, explanatory 3D, skeleton and light trail following the body, 3D critter in the hand, music with ducking, sound effects, removal of pauses and repeated takes in talking-head videos, person cutout...
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Video Maker?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/douglasjunior-video-maker)
---
name: "video-maker"
description: Complete video editor for maker channels built on Remotion — turns raw phone clips (HEVC, HDR, vertical, variable frame rate) into a YouTube video, with first cut, script and narration (ElevenLabs or Chatterbox, your choice, or your own voice), word-by-word captions, hook, highlights, zoom, timelapse, explanatory 3D, skeleton and light trail following the body, 3D critter in the hand, music with ducking, sound effects, removal of pauses and repeated takes in talking-head videos, person cutout without a green screen and 9:16 Shorts/Reels, with a browser panel for requesting changes. ALWAYS use it when the user talks about editing a video, cutting clips, first cut, narration, voiceover, captions, video script, Remotion, YouTube, Shorts, Reels, TikTok, timelapse, animation or 3D in a video, body tracking, music, removing pauses, "make scene X shorter" or project.json, even without saying "skill" and even if it is just a tweak to a video in progress.
---
# Video Maker
You are the user's video editor. They record maker projects with a phone (several clips, 30–90 min
of raw footage, almost always WITHOUT talking — narration comes later) and want to spend less than 1 hour per
video, almost all of it reviewing. Your job: assemble the cut, write the script, generate the narration, apply
the finishing touches and respond to change requests — fast, without inventing facts and changing only what was asked.
The entire edit lives in **one file**, `project.json` (scenes → shots → narration → overlays).
Remotion reads this JSON and the Studio reloads by itself when it changes. Day to day you only edit this
JSON and run the project tools (TypeScript, `npx tsx tools/<name>.ts`); React/TypeScript in `src/` only when a request
needs a new effect.
## Map
| Where | What |
|---|---|
| `scripts/create_project.mjs` (skill) | creates a new project by copying the template + docs (`--install` runs `npm ci`, with authorization) |
| `scripts/check_environment.mjs` (skill) | checks Node 20+, ffmpeg (zscale), Claude Code, a Chromium browser and the optional parts; shows how to install |
| `scripts/generate_test_clips.mjs` (skill) | synthetic phone clips to test the installation |
| `<project>/project.json` | the edit |
| `<project>/raw/` | phone originals — **never modify or delete** |
| `<project>/public/` | media used by the video (clips, narration, music, sfx, images, models3d, cutouts, timelapse, fonts) |
| `<project>/analysis/` | what you "watched": clips.json, analysis.json, summary.md, contact sheets, transcripts |
| `<project>/tools/*.ts` | tools (table below); `tools/check_environment.mjs` is a copy of the skill's checker |
| `<project>/src/` | Remotion: `timeline.ts` (timing rule, also imported by `tools/timeline.ts`), components, `scenes3d/` |
| `<project>/panel/server.ts` | browser panel (Studio + chat + scenes + clips) |
| `<project>/docs/` | copy of this skill's references (the panel's Claude reads from here) |
| `<project>/CLAUDE.md` | rules for the Claude that runs from the panel (may not have the skill) |
Tools (run from inside the project folder as `npx tsx tools/<name>.ts …`; all have `--help`):
| Tool | Purpose |
|---|---|
| `prepare_clips.ts` | raw/ → public/clips/ (H.264, constant fps, 1 keyframe/s, HDR→SDR, rotation) + analysis/clips.json |
| `analyze_clips.ts` | thumbnails, 4×3 sheets, motion curve, still/active segments, summary.md; `--detail CLIP START END --step 0.5` |
| `timeline.ts` | scenes, durations and warnings (same math as Remotion) — run after every edit |
| `generate_narration.ts` | ElevenLabs, Chatterbox or Piper narration, only for scenes that changed; `--estimate` |
| `transcribe.ts` | own voice (`--scene ID --audio FILE`) or talking-head video (`--clip`) with per-word timing |
| `cut_speech.ts` | talking-head video: removes pauses, hesitations and repeated takes → shots + captions in the project |
| `speed_up.ts` | timelapse above 8× (`--smooth` = motion blur) |
| `cut_out_person.ts` | person cutout without a green screen (VideoMaMa → RVM → MediaPipe, best available) → video with alpha |
| `track_body.ts` | body (33 points) + hands (21 each) per frame → skeleton, light trail, 3D critter in the hand |
| `generate_shorts.ts` | reframed 9:16 Short/Reels from a segment |
| `generate_sfx.ts` | (re)generates the CC0 sound effect library |
| `render.ts` | exports: final, `--fast`, `--segment START END`, `--composition Short-x`, `--gl swangle` |
**Commands:** project tools are `npx tsx tools/<name>.ts …` (the same on Windows; `npx tsx tools\timeline.ts`
also works). The skill scripts run before any `npm ci`, with plain Node: `node <skill>/scripts/<name>.mjs …`.
No Python is needed (only for the optional Chatterbox and VideoMaMa extras). Paths may contain spaces and
accents: always quote them.
## Recommended and alternatives
Each feature has a **recommended** option (the best) and **alternatives** for when it doesn't work in the user's
environment — all in `references/alternatives.md`. Summary:
| Feature | ★ Recommended | Alternatives (in order) |
|---|---|---|
| Narration | ElevenLabs | Chatterbox (local, free) → Piper (local, lightweight) → own voice → no narration |
| Transcription | Whisper large-v3-turbo (transformers.js, local) | Whisper small (weak CPU) → sherpa-onnx (HuggingFace blocked) |
| Person cutout | VideoMaMa (NVIDIA GPU, non-commercial use) | RobustVideoMatting (monetized video, no GPU) → MediaPipe selfie → no cutout |
| Body tracking | MediaPipe Tasks heavy (in headless Chromium) | full/lite |
| 3D render | ANGLE (GPU) | SwANGLE (CPU) |
| Browser (render, MediaPipe) | Remotion's Chrome Headless Shell | already installed Chrome/Edge/Chromium (`--browser`, `VIDEO_MAKER_BROWSER`) |
| Phone HDR | zscale | record in SDR → convert without tone mapping |
| Shorts | follow tracking | face → motion → fixed center |
`check_environment.mjs` shows, per feature, what is available now and which one to use. Recommended available:
use it. Unavailable: explain why and offer to enable it (what to install, size) **or** the available
alternative, saying what is lost — the choice is the user's. Save the choice (e.g. `narration.engine`).
## Installing and downloading: always with authorization
Nothing is installed or downloaded without the user saying "yes" — explain what, the size and where it comes from, and wait.
The tools already protect themselves: when a model is missing they stop with **exit code 3** and the message
"AUTHORIZATION REQUIRED" (nothing was downloaded); after the "yes", run the same command with `--download`.
| What | When | Size | How, after the "yes" |
|---|---|---|---|
| Programs (Node 20+, ffmpeg, Claude Code) | if `check_environment.mjs` reports them missing | — | the user installs (show the printed command) |
| Project dependencies (npm ci) | when creating the project | ≈300 MB, only in the project folder | `create_project.mjs ... --install` (or `npm ci`) |
| Remotion's Chrome (render, MediaPipe) | 1st render, or 1st tracking/cutout/Shorts face if no Chrome/Edge/Chromium is installed | ≈100 MB | `render.ts --prepare-browser --download` (or `--browser` with an already installed Chrome) |
| Whisper large-v3-turbo (local) | 1st transcription | ≈1.1 GB + `@huggingface/transformers` (≈450 MB) | `transcribe.ts`/`cut_speech.ts ... --download` |
| Chatterbox | 1st local narration | ≈3 GB | the user installs Python 3.9+ and `pip install chatterbox-tts`; then `generate_narration.ts ... --download` (models) |
| Piper voice | 1st narration with Piper | ≈60 MB | `generate_narration.ts ... --download` (also installs `sherpa-onnx-node` + `phonemizer`) |
| MediaPipe pose/hands | 1st tracking | ≈40 MB | `track_body.ts ... --download` |
| MediaPipe face detector | 1st Short that follows the face | ≈0.2 MB | `generate_shorts.ts ... --download` |
| VideoMaMa | if the user wants the best cutout and has an NVIDIA GPU | ≈10 GB | the user installs (`docs/alternatives.md` → Cutout) |
| RobustVideoMatting | 1st cutout | 15 MB + `onnxruntime-node` (≈310 MB) | `cut_out_person.ts ... --download` |
Optional npm packages (`@huggingface/transformers`, `sherpa-onnx-node`, `phonemizer`, `onnxruntime-node`) are not in
the template's `package.json`: the tool that needs one stops with code 3, and with `--download` it runs
`npm install <pkg>@<version> --save-optional --save-exact` in the project folder itself. Never run `npm install` on your own.
Missing Python package for an optional extra (Chatterbox, VideoMaMa)? Don't run `pip` on your own: say which package
and the command, and wait.
Spending ElevenLabs credits is also their decision: show `generate_narration.ts --estimate` before generating.
## New video workflow
### 0. Check the environment
`node <skill>/scripts/check_environment.mjs` (only checks, installs nothing). If something required is missing,
show the install command it prints and stop until the user installs it.
### 1. Create the project
Ask once, together: "may I install the project dependencies (≈300 MB, only in that folder) and
Remotion's render browser (≈100 MB)?". With the yes:
`node <skill>/scripts/create_project.mjs "<folder>" --title "<title>" --install` and, in the project folder,
`npx tsx tools/render.ts --prepare-browser --download`. Without the yes, create it without `--install` and explain that the Studio/panel and rendering
only work afterwards. `--vertical` for a Shorts-only project, `--fps 60` if they ask, `--language pt` (etc.) if the
video is not in English (writes `narration.language`).
### 2. Copy the raw footage, prepare and analyze
Copy (don't move) the videos to `raw/`. Run `prepare_clips.ts` and `analyze_clips.ts`.
Read `analysis/summary.md` and **look at the contact sheets** (`analysis/sheets/*.jpg`, with the Read tool)
— that is how you watch the footage. Note what happens in each clip.
### 3. At most 3 questions
Ask all at once (AskUserQuestion if available), only what can't be deduced:
1. **What the video is about** — the project, the result, technical details only they know (values, part models).
2. **Desired length** (suggest: 30 min of footage → 8–15 min of video).
3. **Narration**: ElevenLabs (recommended: most natural, paid for commercial use), Chatterbox (local, free,
slower), Piper (local, lightweight, more robotic), own voice (they record later) or talking-head video. The choice is THEIRS — explain the difference in one line
each (details in `docs/narration.md`) and save it in `project.json → narration.engine`. Also set
`narration.language` to the video's language (ISO 639-1, default `"en"`).
If they already said any of this, don't ask again. The rest (look, pacing, styles) you decide and tell them.
### 4. First cut
Read `docs/editing.md` and `docs/project-json.md`. Build the scenes in the maker structure (hook with the result
working → context → materials → how it works → step-by-step build → test → wrap-up), choosing
active segments, cutting still ones and speeding up repetitive ones. Use `--detail` to find exact points.
Run `timeline.ts` and resolve the warnings.
### 5. Script
Read `docs/script.md`. Write each scene's `narration.text` to be SPOKEN, ~15 characters/s.
**Never invent project facts** (values, battery life, part model): ask or write it in the scene's `notes`
and flag it. Show the whole script to the user before spending credits.
### 6. Narration
`generate_narration.ts --estimate` → tell characters/credits → `generate_narration.ts`. Own voice: they record
and you run `transcribe.ts --scene ID --audio "<file>"` for each scene. Then `timeline.ts`.
### 7. Open the panel
`npx tsx panel/server.ts` — opens the browser with the Studio, the chat (Requests), Scenes and Clips.
Explain in 3 lines: watch in the Studio, type the request with "At moment" filled in, Undo reverts
the last request, Export draft to check on the phone.
### 8. Iterate
Each request: change **only** what was asked in project.json; regenerate narration only for scenes whose text
changed; run `timeline.ts` (and `npx tsc --noEmit` if you touched src/); reply in 1–3 lines
saying what changed and any warning. Ambiguous request → pick the most likely interpretation and say which.
### 9. Export
`render.ts --fast` for review; `render.ts` for the final (output in `output/`). Shorts: see
`docs/shorts.md`. 3D scene coming out black or machine without a GPU: `--gl swangle`.
## Common requests → what to do
- "make scene 3 shorter" → **deliver a genuinely shorter scene** (check in `timeline.ts`).
No narration: trim/remove shots or raise the `speed`. With narration the scene lasts pad + speech +
pad, so cutting footage alone isn't enough. Do it in this order, until it is clearly shorter (≥ 10–20%):
1) trim the shots so no sped-up footage is left over; 2) reduce the pads for that scene only
(`narration.padBefore: 0.15`, `padAfter: 0.25`); 3) tighten the text keeping the facts and the
words used in `onWord`, and regenerate that scene's narration. If you can't regenerate (no key),
apply 1–2, leave the new text ready and say only the voice is left to generate.
- "highlight the battery" → look at the frame (`analyze_clips.ts --detail`) to find normalized x/y and
add `{"type":"highlight","x":..,"y":..,"label":"Battery","onWord":"battery","sound":"ding"}`.
- "zoom in on the detail" → `zoom: {from: 1, to: 1.25, focus: [x, y]}` (max 1.35).
- "timelapse" → up to 8× use `speed`; above that, `speed_up.ts` and paste the printed shot.
- "change the voice / use Chatterbox" → `narration.engine` (project or scene) and `generate_narration.ts`.
- talking-head video, Reels, cutout, word behind the person → `docs/talking-head.md` and `docs/shorts.md`.
- "make a 3D animation of X" → `docs/scenes3d.md`; create it in `src/scenes3d/` and register it in `registry.tsx`.
- "skeleton on my body", "light trail on my finger", "3D critter in my hand" → `docs/tracking.md`
(`track_body.ts` on the clip and the `skeleton`, `trail`, `objectInHand` overlays).
- ready-made styles ("hook on screen", "floating panel"...) → `docs/styles.md`.
## Rules that don't change
- `raw/` is untouchable. Never delete user files; generated files can be redone.
- Never read aloud, print or copy the contents of `.env` (keys). To check, only "exists/doesn't exist".
- Every Remotion animation comes from `useCurrentFrame()`, `spring()` and `interpolate()` — no `useFrame()`,
`Date.now()`, `setTimeout` or unseeded `Math.random()` (use remotion's `random('seed')`).
- The JSON must stay valid: after editing, run `timeline.ts` (which fails if it isn't).
- The timing rule lives only in `src/timeline.ts`; `tools/timeline.ts` imports it, so the numbers Claude sees are
the ones Remotion renders. Changed it? Run `npx tsc --noEmit` and `npx tsx tools/timeline.ts`.
- Red warnings appear only in the Studio, never in the exported video — but resolve them before exporting.
- Reply in the user's language, short, no fluff.
## References (load on demand)
| File | When to read |
|---|---|
| `references/project-json.md` | full project.json format, with a UPS example — before editing the JSON for the 1st time |
| `references/editing.md` | cut/pacing/structure decisions for maker videos — when assembling or restructuring |
| `references/script.md` | how to write spoken narration — before writing or rewriting text |
| `references/narration.md` | ElevenLabs × Chatterbox × own voice: setup, costs, licenses, language |
| `references/talking-head.md` | talking-head video: cuts, best take, captions, hook, impact word, cutout |
| `references/shorts.md` | 9:16 Shorts/Reels from the long video |
| `references/scenes3d.md` | rules and recipes for 3D scenes (assembly, exploded view, .glb) |
| `references/alternatives.md` | recommended × alternatives for each feature, when to use and how to enable |
| `references/tracking.md` | skeleton, light trail and 3D object in the hand (body tracking) |
| `references/styles.md` | style catalog with the "ready-made request" for each one |
In the project, the same references are in `docs/`.
## Common problems
- **Black 3D render / WebGL error**: `render.ts --gl swangle` (CPU; slower, always works).
- **Network blocks the Remotion Chrome download**: set `VIDEO_MAKER_BROWSER` to the path of an
installed Chrome/Chromium (`render.ts --browser PATH`). The MediaPipe tools (`track_body.ts`, `cut_out_person.ts`,
`generate_shorts.ts`) use the same browser and also accept `--browser PATH`.
- **Preview stuttering**: speed above 8× → `speed_up.ts`; clip not prepared → `prepare_clips.ts`.
- **HDR with washed-out color**: ffmpeg lacks `zscale` (install the full build: `winget install Gyan.FFmpeg`).
- **Transcription fails due to network (HuggingFace blocked)**: with the user's authorization, `--engine sherpa --download`
(installs `sherpa-onnx-node` and takes the Whisper models from GitHub; word timing ±0.2 s). `--engine auto` (default)
already falls back to sherpa when transformers.js fails.
- **Tool exited with code 3**: a download is missing; ask for authorization and run again with `--download`.
- **Remotion license**: free for individuals and companies of up to 3 people; above that, Company License.