FilmCraft
Skill1 starsChanged 18 days agoMITView on GitHub
Use whenever working with FilmCraft on this machine — the Rust video editor and Premiere Pro alternative — including launching the app with control port ("FilmCraftを起動", "FilmCraftを立ち上げて", "launch FilmCraft"), creating, editing, trimming, colouring or exporting sequences and projects (.fcproj, MP4/MOV/MXF, PNG/TIFF/GIF, WAV/AIFF/AAC, XML/FCPXML/OTIO/EDL/AAF/OMF, SRT/VTT/SCC), driving the running desktop window, or using its MCP server, filmcraft-cli or control channel. Triggers on "FilmCraft", "filmcraft-cli", "filmcraft mcp", "FilmCraft MCP", "FilmCraftを起動", "FilmCraft立ち上げて", "FilmCraft開いて", "edit this video", "build a sequence", "cut this clip", "add a transition/effect/caption", "export to MP4/ProRes/DNxHR", "export XML for Premiere", "take a FilmCraft screenshot", "drive the FilmCraft window", and requests to automate video editing or FilmCraft itself. Invoke with @filmcraft.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- rawphp/skillstheir own version, first seen Nov 1, 2026
- midasmatterhorn/artcraft-skillstheir own version, first seen Oct 17, 2026
- hermes-pro/storytold-skillstheir own version, first seen Oct 13, 2026
- OmkarPalika/filmcrafttheir own version, first seen Jul 20, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- midasmatterhorn/artcraft-skills★ 82same name
- hermes-pro/storytold-skills★ 36same name
- OmkarPalika/filmcraft★ 2same name
- rawphp/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- canvas-designSkill
- EffectCraftSkill
- style-stockSkill
- video-directorSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Check that FilmCraft CLI is installed and compatible:
- Distinctive: line 21
If command not found: tell the user "FilmCraft is not installed.
- Very specific: line 22
Check FILMCRAFT_CONTROL_TOKEN is set for live GUI bridge mode
- Distinctive: line 69
When the user asks to start or launch FilmCraft (「FilmCraftを起動して」「立ち上げて」「開いて」「start FilmCraft」):
- Very specific: line 73
If running, verify if the control port is responsive (filmcraft-cli --bridge 127.0.0.1:50051 inspect).
- Very specific: line 74
If running *without* a control port, inform the user: *"FilmCraft is currently running without a control port.
- Very specific: line 90
Wait 1–3 seconds, then run filmcraft-cli --bridge 127.0.0.1:50051 inspect.
- Very specific: line 128
Verify: Read sequence_inspect/captions.list.
- Very specific: line 143
Start with: file.newProject, file.import, file.newSequence, timeline.place, timeline.razor, timeline.trim, timeline.slip, timeline.move, …
- Very specific: line 167
Captions are not in
sequence_inspect: Use captions.list; cues carry id, start, end, text.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
FilmCraft — agent operation
FilmCraft is a native Rust video editor (Premiere Pro-class) whose agent interface is built in: every action is a command with an id. Menus, shortcuts, panels, timeline gestures, the CLI, the control channel, the MCP server and the GUI all drive one engine. Verified against 0.10.0–0.13.0 on Windows and Linux.
Setup (agent: run before first use)
Check that FilmCraft CLI is installed and compatible:
filmcraft-cli --version # expect 0.10.x - 0.13.x- If command not found: tell the user "FilmCraft is not installed. Download from https://getartcraft.com/apps/filmcraft"
- Check FILMCRAFT_CONTROL_TOKEN is set for live GUI bridge mode
Machine & environment paths
| Platform | Binary | CLI | Default Data Dir |
| Windows | C:\Program Files\FilmCraft\filmcraft.exe | C:\Program Files\FilmCraft\filmcraft-cli.exe | %LOCALAPPDATA%\FilmCraft |
| Linux | /usr/bin/filmcraft | /usr/bin/filmcraft-cli | ~/.local/share/filmcraft |
| macOS | /Applications/FilmCraft.app/Contents/MacOS/filmcraft | filmcraft-cli (in ~/.local/bin or PATH) | ~/Library/Application Support/filmcraft |
- Log location:
<data-dir>/Logs/filmcraft.log - Control port: loopback only (
--control <port>orFILMCRAFT_CONTROL_PORT, e.g.9876or7991or50051) - Commands: 710 in 42 namespaces
- Effects: 130 video effects, 112 video transitions, 3 audio transitions
Mental model
- A project (
.fcproj, JSON) holds bins and items:Movie,Audio,Image,Sequence,Multi-Camera Source Sequence.project_inspectreturns the tree,activeSequenceand the dirty flag. One sequence is active; commands act on it. - A sequence has
video[]andaudio[]track arrays, each{id, name, items[], transitions[], muted, locked, ...}. A clip is{clip, item, name, start, duration, startFrame, durationFrames, sourceIn, sourceOut, speed, reverse, enabled, link, gainDb, effects[]}— all times in ticks. - Placing a movie creates two linked clips (video + audio) with different
ids and
linkpointing at each other. Selecting one selects both by default. - Time is integer ticks, 254,016,000,000 per second (also 48000×5292).
secondsandframeare snapped to the frame grid;frameandtimecode(e.g."00:00:02:12", or;for drop-frame) map exactly. Preferframewhen you need an exact cut. - A command is
{"id": "timeline.razor", "params": {...}}.command_listfinds ids and parameter docs;command_runexecutes one (undoable);command_batchruns several. Invalid parameter types and unknown commands fail; unknown parameter names are silently ignored (see Pitfalls). - Verify by reading back (
sequence_inspect,project_inspect,captions.list,media.status,jobs.list) or by rendering (render_frame,file.exportFrame). Anullresult means "ran", not "did what you meant".
Two connection modes
| Mode | Start | Use for |
| Headless | filmcraft-cli mcp (--demo, --project p.fcproj, --data-dir d) | no window, batch builds, exports, scripts |
| App bridge | filmcraft --control 50051 + filmcraft-cli mcp --bridge 127.0.0.1:50051 | the real window: UI state, screenshots, clicks, keys, drags, GUI-only commands |
Launching FilmCraft on user request ("起動して" / "start FilmCraft")
When the user asks to start or launch FilmCraft (「FilmCraftを起動して」「立ち上げて」「開いて」「start FilmCraft」):
- Check if already running:
- Windows:
Get-Process filmcraft -ErrorAction SilentlyContinue - Linux / macOS:
pgrep filmcraft - If running, verify if the control port is responsive (
filmcraft-cli --bridge 127.0.0.1:50051 inspect). - If running without a control port, inform the user: "FilmCraft is currently running without a control port. Please save your work and restart it, or allow me to close and relaunch it with
--control 50051."
- Windows:
- Launch with
--control <port>(default:50051) and 64-charFILMCRAFT_CONTROL_TOKEN:- Windows (PowerShell) — use
scripts/launch.ps1to ensure visible desktop window onWinSta0\Default:
(This automatically sets/persistspowershell -File scripts/launch.ps1 -Port 50051FILMCRAFT_CONTROL_TOKEN, configures the port, and launches an interactive task so the GUI is visible to the logged-in user rather than hidden in background session). - Linux:
./scripts/launch.sh 50051 - macOS:
./scripts/launch.sh 50051
- Windows (PowerShell) — use
- Verify the connection:
- Wait 1–3 seconds, then run
filmcraft-cli --bridge 127.0.0.1:50051 inspect. - Once responding, report that FilmCraft is active, listening on port 50051, and ready for live timeline edits and collaborative commands.
- Wait 1–3 seconds, then run
The 17 MCP tools
| Tool | Purpose |
command_list | every command (filter, enabled_only) |
command_run | run one {id, params} |
command_batch | run {steps:[{id,params}], stop_on_error} → {completed, failed, results} |
doc_inspect | project tree + active sequence in one call |
project_inspect | tree, items, active sequence, dirty |
sequence_inspect | active sequence: settings, tracks, clips, transitions, markers |
media_import | import files by absolute path (paths, bin, image_sequence) |
render_frame | PNG at seconds (or playhead), max_side |
render_preview | same as render_frame (bridge: Program monitor) |
ui_inspect | window/UI state (tool, workspace, selection, dialog, playback, elements count) |
ui_elements | on-screen elements with id, label and rect (prefix) |
ui_click | click by id or x,y (button, count, modifiers) |
ui_drag | press–move–release between points or element ids (steps) |
ui_key | key or shortcut (Space, Cmd+Z, Shift+Delete) |
ui_type | type into the focused field |
ui_screenshot | PNG of the window or one panel |
ui_control | any control method: ui.set, ui.menu.list, ui.playback, … |
Resources: filmcraft://document (48 KB JSON: project + sequence) and
filmcraft://commands (192 KB catalog). No prompts.
Standard workflow
- Probe.
project_inspect/doc_inspect; headless starts empty unless--demoor--project.ui_inspectfirst in bridge mode. - Build.
file.newProject→file.import(absolute paths) orfile.importDemoFootage→file.newSequence→timeline.place. - Cut.
playhead.set+timeline.razor,timeline.trim,timeline.slip,timeline.move,edit.clear/edit.rippleDelete. - Style.
effects.apply+effects.setParam;sequence.applyVideoTransition;lumetri.applyPreset;graphics.newText;markers.add;captions.add. - Verify. Read
sequence_inspect/captions.list;render_frameat a telling time and look at the PNG (this catches wrong clips, black frames and missing transitions that no read-back shows). - Export.
file.exportMediawithwait:true(checkofflineMediaand the written file);file.exportInterchangefor NLE round-trips. - Save.
file.saveAs(creates dirs? no — the parent must exist); then re-readproject_inspect.dirty(false after save).
Finding commands
command_list {filter:"razor"} matches id, label, menu and params. filmcraft-cli
commands razor, describe <id> and filmcraft-cli inspect do the same from a
shell. All 701 ids with their parameter docs are in references/commands.md;
verified step-by-step JSON is in references/recipes.md.
Start with: file.newProject, file.import, file.newSequence,
timeline.place, timeline.razor, timeline.trim, timeline.slip,
timeline.move, timeline.select, edit.clear, edit.rippleDelete,
edit.undo, effects.apply, effects.setParam,
sequence.applyVideoTransition, sequence.setTransition, markers.add,
captions.newTrack, captions.add, graphics.newText, file.exportMedia,
file.exportInterchange, file.exportFrame, file.saveAs.
Pitfalls that cost time
- Command params are lenient — unknown keys and some wrong types are
silently dropped.
timeline.trim {seconds:-1}returns{"delta":0}(the key isdelta);timeline.place {seconds:"2"}places at 0;fps:"fast"falls back to 23.976. Some commands do validate (graphics.set,markers.add), so never rely on an error to catch a bad param. Read the param doc, then read the state back. file.newSequenceswitches the active sequence and returns{sequence: id}.sequence.openwants{item: id}— passingsequenceor a clip id errors. After any open/new, re-readsequence_inspect.- Transitions are not on the clip. They live in
sequence_inspect.video[i].transitions[]as{id, effect, from, to, start, duration, align, reverse, params}.sequence.removeTransition {transitions:[id]};sequence.setTransitionedits duration/align/params. - Captions are not in
sequence_inspect. Usecaptions.list; cues carryid, start, end, text.captions.newTracksilently falls back toSubtitlefor any unknown format string. - Never pass a directory to
file.exportMedia. It hangs indefinitely (reproduced twice, >3 min, no output). Use a full file path. - The format wins over the extension.
format:"gif"without.mp4writesout.mp4.gif; ProRes without.mp4writesout.mp4.mov. The result'spathis authoritative. timeline.placewithdurationlonger than the source holds the last frame for the rest of the clip, without warning. Trim with media in mind.range:"inOut"with no marks exports the whole sequence, silently.range:"custom"+startSeconds/endSecondsis the reliable sub-range.jobs.listis a command, not a tool.command_run {id:"jobs.list"};jobs.cancel {job}removes the partial file.wait:falseexports return{job, path, poll, cancel}.- Demo footage is synthetic. Interchange exports (FCPXML/AAF/OMF) of demo
media lose clips; with real on-disk media they round-trip (see
references/formats-and-roundtrip.md). edit.clear(Backspace) leaves a gap;edit.rippleDeletecloses it.sequence.lift/extractneed sequence in/out marks, not a selection.lumetri.applyPresetappends a new Lumetri effect each time instead of replacing the previous look. Remove the old effect or set params directly.- GUI-only commands are invisible to
command_list:window.workspace. {editing,assembly,color,effects,audio},window.workspace.reset,window.toggleFullScreen,app.about. They exist only on the bridge. - HEVC export is unavailable here ("no encoder registered"). H.264, ProRes, DNxHR, MJPEG, MXF, image sequences and audio all work.
prefs.setin a headless session is session-scoped — it did not persist across two--data-dirsessions. Use the GUI for durable preferences.- MCP tool arguments are strict (unknown key → JSON-RPC
-32602; wrong type →isErrorwith a deserialize message), butcommand_run.paramsis passed through untouched.
Reference map
| File | Contents |
references/recipes.md | verified JSON for build, cut, effects, colour, captions, graphics, proxies, multicam, TTS, export, GUI |
references/commands.md | all 701 commands, grouped by namespace, with parameter docs |
references/mcp-and-control.md | MCP details, error shapes, resources, control methods, GUI-only commands |
references/cli.md | filmcraft-cli subcommands, flags, exit codes, offline media, headless jobs |
references/formats-and-roundtrip.md | export matrix + independent validation, interchange round-trips |
references/bugs-and-workarounds.md | every reproduced defect with a minimal reproduction |
references/maintenance.md | re-verify the version, dump commands, refresh this skill |
scripts/probe.sh | MCP handshake + tool count + version |
scripts/dump-commands.sh | regenerate the command catalog |
scripts/smoke-test.sh | build → render → export → independent validation |
Community: https://discord.gg/artcraft · https://getartcraft.com/apps/filmcraft · https://github.com/storytold/filmcraft.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

