auto-editor-export — Claude Code skill: what it does, how to install
Exports auto-editor cuts and mic recordings to DaVinci Resolve, Premiere Pro, Final Cut Pro, or timeline files instead of direct rendering.
npx skills add WyattBlue/auto-editor --skill auto-editor-export -a claude-codeWhat auto-editor-export does
By default, auto-editor outputs a rendered media file. This skill configures --export to generate project files for non-linear editors instead: XML for Adobe Premiere Pro, FCPXML for DaVinci Resolve and Final Cut Pro, or projects for ShotCut and Kdenlive. It also handles exports to split clip sequences and native .v1, .v2, or .v3 timeline formats.
Recording from a microphone via :mic keeps a companion *_RECORDING.mka track next to the project file. The default audio encoder is lossless FLAC. You can select another Matroska-compatible codec with -c:a, but unsupported encoders will fail immediately before capture starts. For Final Cut Pro and Resolve, the skill configures the FCPXML version and custom timeline names.
Importing works in reverse. Auto-editor accepts .v3 timelines and experimental FCP7 XML files directly as inputs to render the final video. That lets you inspect and tweak cut points before starting a render pass.
What it helps with
- export auto-editor cut decisions directly to DaVinci Resolve or Premiere Pro
- preserve microphone capture in a companion MKA audio file
- split media into individual clip files at cut points
- render edited
.v3timeline files or FCP7 XML projects back to video - adjust FCPXML compatibility versions for legacy editing software
Example prompts for the agent
- Export the edit of video.mp4 to a DaVinci Resolve fcpxml project
- Record audio from :mic and export a Premiere XML project named interview
- Render the finished video from timeline.v3
How to install auto-editor-export
1Skills CLI (Vercel)
npx skills add WyattBlue/auto-editor --skill auto-editor-export -a claude-code2Manually: put the files in place
~/.claude/skills/auto-editor-export/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/auto-editor-export/
1Skills CLI (Vercel)
npx skills add WyattBlue/auto-editor --skill auto-editor-export -a codex2Manually: put the files in place
.agents/skills/auto-editor-export/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add WyattBlue/auto-editor --skill auto-editor-export -a cursor2Manually: put the files in place
.cursor/skills/auto-editor-export/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install WyattBlue/auto-editor auto-editor-export2Manually: put the files in place
.github/skills/auto-editor-export/SKILL.md1Skills CLI (Vercel)
npx skills add WyattBlue/auto-editor --skill auto-editor-export -a gemini-cli2Platform CLI
gemini skills install https://github.com/WyattBlue/auto-editor --path skills/auto-editor-exportManually: put the files in place
.devin/skills/auto-editor-export/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add WyattBlue/auto-editor --skill auto-editor-export -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 auto-editor-export
How do I install auto-editor-export in Claude Code?
Run npx skills add WyattBlue/auto-editor --skill auto-editor-export -a claude-code in your terminal.
What does auto-editor-export do?
It guides the agent on using auto-editor's --export flags for video editors like Premiere, Resolve, Final Cut Pro, ShotCut, and Kdenlive, as well as importing timeline files for rendering.
How does microphone export preserve audio?
When using :mic, auto-editor writes a companion *_RECORDING.mka file with lossless FLAC by default, keeping the audio source intact alongside the exported project timeline.
Source text
SKILL.md · Unlicense
--- name: auto-editor-export description: Export auto-editor's edit or microphone recording to a video editor (Premiere, DaVinci Resolve, Final Cut Pro, ShotCut, Kdenlive), to individual clips, or to auto-editor timeline files (.v1/.v2/.v3); and import timeline/XML files to render them. Use when someone wants an editor-ready project, a preserved microphone source, split clips, or timeline files instead of a finished video. --- # Exporting & importing By default auto-editor renders a media file. `--export` (`-ex`) changes the target. The output extension is chosen automatically per mode. ```bash auto-editor video.mp4 --export premiere # → video_ALTERED.xml for Premiere Pro ``` ## Export targets | `--export` | For | Output | |---|---|---| | `premiere` | Adobe Premiere Pro (fcp7 xml) | `.xml` | | `resolve` | DaVinci Resolve (fcpxml) | `.fcpxml` | | `resolve-fcp7` | Resolve via legacy fcp7 xml | `.xml` | | `final-cut-pro` | Final Cut Pro | `.fcpxml` | | `shotcut` | ShotCut | `.mlt` | | `kdenlive` | Kdenlive | `.kdenlive` | | `clip-sequence` | individual media clips, one per kept segment | media files | | `v1` / `v2` / `v3` | auto-editor timeline files | `.v1` / `.v2` / `.v3` | | (default) | rendered media file | per container | ```bash auto-editor video.mp4 --export resolve auto-editor video.mp4 --export final-cut-pro auto-editor video.mp4 --export clip-sequence auto-editor video.mp4 --export v3 -o timeline.v3 ``` ## Export a microphone recording Use `:mic` as the input and press Ctrl-C to finish capture. Editor and timeline exports keep a sibling `*_RECORDING.mka` source so the project remains usable: ```bash auto-editor :mic --export resolve -o interview.fcpxml # writes interview.fcpxml and interview_RECORDING.mka ``` With `-c:a auto` (the default), persistent recordings use lossless FLAC. Choose another Matroska-supported encoder explicitly; unsupported encoders fail before capture. Encoder sample rates and channel layouts are negotiated during the recording transcode. ```bash auto-editor :mic --export resolve -c:a opus -o interview.fcpxml auto-editor :mic --sample-rate 44.1kHz --export v3 -o interview.v3 ``` Ordinary rendered outputs and `clip-sequence` use a temporary capture instead; their final audio codec still follows the output container and `-c:a`. ## Naming the timeline `premiere`, `resolve`, and `final-cut-pro` accept a `name` attr (default "Auto-Editor Media Group"). Pass extra attrs after a colon: ```bash # POSIX shells auto-editor example.mp4 --export 'premiere:name="Your name here"' # PowerShell (double the inner quotes) auto-editor example.mp4 --export 'premiere:name=""Your name here""' ``` `final-cut-pro` and `resolve` also accept `version`, the FCPXML version to write: `11` (default) for FCPXML 1.11, or `10` for FCPXML 1.10, for an older editor that can't read 1.11. ```bash auto-editor example.mp4 --export final-cut-pro:version=10 ``` ## Split into clips without further editing To split at the cut points but make no other edits, set both actions to `nil`: ```bash auto-editor example.mp4 -w:0 nil -w:1 nil --export premiere ``` ## Importing timelines auto-editor reads timeline/XML files as inputs and renders them like any media: ```bash auto-editor myFcp7File.xml -o render.mp4 # render an fcp7 xml (experimental) auto-editor timeline.v3 -o render.mp4 # render an auto-editor timeline file ``` Importers: auto-editor timeline files (`.v1`, `.v2`, `.v3`) and FCP7 XML (experimental). The input format is detected by extension. PRs for more importers are welcome. ## Timeline format notes `.v1`/`.v2`/`.v3` are auto-editor's own timeline formats; `.v3` is the current layered format (supports stacked tracks / overlay compositing). See <https://auto-editor.com/docs/v3> (and `/docs/v1`, `/docs/v2`). Export a timeline to inspect or hand-tweak the edit, then re-import it to render. For plain rendering, edit methods, and pace, see the **auto-editor** skill.
© WyattBlue · Unlicense · WyattBlue/auto-editor