Video Editor Skills
Video Editor Skills guide an editing agent, retaining the creator’s pacing and pause preferences for later video episodes.
- 416 ★ on the repository
- Last commit
Extended access
Why this level
- The agent writes and runs scripts, adds assets in Resolve and calls the configured speech-to-text API.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/video-editor-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent writes and runs scripts, adds assets in Resolve and calls the configured speech-to-text API.
This is third-party code. Review the repository files before installing.
What it does
Video Editor Skills is a Claude Code instruction set for rough cuts in DaVinci Resolve Studio. The agent reads a transcript, selects usable takes and assembles a new timeline. The creator reviews it, judges pacing and makes creative decisions. Separate guidance covers audio, B-roll and captions. The package contains no ready-made executable tools. During setup, the agent and user build small scripts for that workspace and retain settings and editing feedback for later episodes.
Who it is for. Tutorial and vlog creators using Resolve Studio who want an agent to prepare the first edit.
Good fit when
- A recording has repeated takes and false starts to mark before manual editing.
- Recurring episodes follow the same pause, caption and loudness rules.
- Several edits have produced feedback to apply to the next episode.
- A rough cut is ready for review before export to YouTube.
Not a fit when
- You only use free Resolve without external scripting.
- The edit must be final without a creator review.
- You plan a paid product or service without permission for commercial use of these skills.
Example request
Prepare a first cut of this lesson: mark retakes, preserve the original footage and create a new timeline for review.Limitations
Editing requires DaVinci Resolve Studio with external scripting enabled, ffmpeg and Python 3.9 or later; the free Resolve edition does not support this workflow. Transcription requires an API with word-level timestamps. The user stores its credentials in a separate file rather than sending them in agent chat. CC BY-NC 4.0 limits commercial use; obtain the author’s permission before using these skills in paid services or products.
How to disable. Remove the plugin or copied skills from Claude Code. Preserve timelines and generated workspace scripts separately, then disable unused API credentials.
FAQ
Where do the editing scripts come from?
The agent builds them with the user during setup. The package supplies methods and a configuration template, so complete setup before editing.
Can the agent alter original footage?
The skills prohibit changes to raw footage and existing timelines, but these are instructions to the agent. Work on a project copy and confirm that the result goes into a new timeline.
What happens after pacing feedback?
The agent records the decision in `CLAUDE.md` for later edits. Read the new rule to confirm it captures your pacing feedback without extra decisions added by the agent.
Are Figma and Remotion required?
No. They support optional motion overlays and brand designs. The first edit can start without them.
Who publishes the finished video?
The user does. The skills prohibit publishing without the user, so review the export first.
Discussion
No questions or reviews yet.
Related
SkillsA video editing skill for Claude Code and Codex: the agent cuts pauses and filler words, grades color, burns subtitles and adds animated overlays
ChatGPT short-video editing skills
ChatGPT 剪短影音 Skills
Two agent skills: set up the editing environment and build a vertical short video in eight verified steps
Skills for faceless video channels: one topic becomes a video with voiceover, subtitles, covers and per-platform copy.
A skill that turns an idea, a link or a screen recording into finished video: HeyGen avatar, b-roll, captions and quality checks
Skills, a CLI and an MCP server that let Claude Code or Codex make video from a brief: editing, graphics, voiceover, subtitles
An agent edits short talking-head videos: transcript, subtitles, B-roll and export for Xiaohongshu, Douyin and WeChat Channels
README in short
Epidemic Sound music, Figma designs and Remotion graphics need separate connections. Additional guidance covers YouTube export and Resolve API failures.
README badge
Original SKILL.md
---
name: video-editor-setup
description: Sets up an AI first-pass video editing workspace for DaVinci Resolve Studio with Claude Code - folders, tools, API keys handled safely, the Resolve template, and which small scripts to build first. Use for "set up my video editor", "start the video editing system", or before the first /edit-video when no workspace exists yet.
---
# Video editor: setup
You are going to be a **first-pass editor**. The creator films, you import, cut, mark, score and caption; **they make the taste calls**. Everything below was learned editing real YouTube vlogs and classes. Build the workspace with the user, step by step, and ask before installing anything.
## What the user needs
- **DaVinci Resolve Studio** (the free version has no external scripting). In Preferences > System > General set *External scripting using: Local*, restart Resolve.
- **ffmpeg / ffprobe**, Python 3.9+, Node 18+ (only for motion graphics).
- A **speech-to-text API** with word timestamps and verbatim mode (we used ElevenLabs Scribe: word-level timings, audio events like "(laughs)", auto language detection). Any service with per-word start/end works.
- Optional: an **Epidemic Sound** account connected as an MCP server (music + SFX), **Figma** MCP (brand boards), **Remotion** (rendered overlays).
## Folder layout (create it with them)
```
<workspace>/
raw video/ the creator drops footage here: one file, or a folder of clips. READ-ONLY for you.
export edited video/ the creator exports here. Never touch.
brand/ BRAND.md (look + voice rules), brand.json (tokens), logo, sfx/
system/
config.json all defaults (see templates/config.example.json in this package)
keys.env API keys. NEVER print, echo, cat or read it into the conversation.
scripts/ the small scripts you write together (list below)
looks/ exported grade stills (.drx) for log footage
motion/ the motion-graphics kit (Remotion project)
videos/<video>/ per-video work: transcript, decisions, cuts, music bed, captions, overlays
CLAUDE.md house rules + a "Learned facts" list you keep adding to (dated, one line each)
```
## Hard rules to write into CLAUDE.md on day one
1. Never modify, move or copy the raw footage. Resolve plays the camera files in place; you write only small JSON/text into `system/videos/<v>/`.
2. **In Resolve, only add.** Import into bins, create *new* timelines (a rebuild makes "v2", never overwrites), add on free tracks. Never change the creator's template timeline, their own timelines or their media. Never switch, create or close projects.
3. Transcripts stay verbatim. Re-transcribing costs money: ask first.
4. Keys stay secret (see above). Load them from the file inside scripts only.
5. **Decisions are by word index, timing is by script.** You decide which words stay; a script turns that into frame-exact cuts. Never hand-edit generated cut files.
6. If a step fails twice, stop and report the exact error.