This skill is responsible for exporting preview frames, final cuts, exchange files, and output verification. Handoff with same-package skills is by name; it can be used when installed alone and does not read sibling directories. It invokes the fixed released filmcraft-cli and preserves the native editing project.
Trusted directory permissions
Old cli.py natively forwarded project reading and editing also require an independent root parameter before -- ; only exact version/help/no-project-directory queries are compatible with old invocations. Model downloads must separately use --model-maintenance, see this skill's execution permissions。
Public workflow.py and commands.py run must explicitly provide --read-root READ_DIRECTORY --write-root WRITE_DIRECTORY(repeatable); the root must be an existing canonical real directory, from user/host authorization, and cannot be derived from plans or material metadata. Plans, materials, and source deliverables must be located under the read root; deliverables and their parent directories must be located under the write root.--runtime-home is the installation maintenance directory and must be located under an independently and explicitly authorized write root; editing native processes is always prohibited from modifying this cache, skills, registration inputs, and source projects. Current root-isolated execution supports macOS headless; desktop entry points must simultaneously isolate the signed application and MCP client owned by this session, exposing only the allocated loopback control port. External bridges whose isolation cannot be confirmed are explicitly rejected. The low-level Python test API is not a public authorization entry point. For detailed boundaries, see execution permissions。
Inputs and deliverables
Inputs are the user-confirmed task, materials, project or object, output directory, and modification scope; when an existing project is needed, verify the summary first. Return the actual CLI results, the saved native project, the required derived outputs, and the verification records. Installation success, command directory existence, and creative task completion are reported separately.
First-time use and public entry points
Locate the real directory of the current SKILL.md. Currently supports macOS arm64, Python 3.11+; the fixed CLI is installed to the user data directory. When existing task authorization covers the necessary dependencies, execute this skill's installer directly without creating a separate approval process.
Set SKILL_DIR to the directory (absolute path) containing this SKILL.md actually loaded by the host. User-level installations may be located at ~/.agents/skills/filmcraft-cli-export, project-level ones may be located at .agents/skills/filmcraft-cli-export, and plugins may be located in their skills/filmcraft-cli-export or host cache directory; the actual loaded path prevails, do not guess based on the current working directory, and do not search and arbitrarily select a duplicate version. The skill directory and the CLI user data installation directory are two independent locations.
: "${SKILL_DIR:?请先设置为本 SKILL.md 的实际所在目录}"
python3 -I -B "$SKILL_DIR/scripts/bootstrap.py"
python3 -I -B "$SKILL_DIR/scripts/cli.py" -- --version
python3 -I -B "$SKILL_DIR/scripts/cli.py" -- commands --json
CLI argv after -- , the native subcommand must come first. Installation parameters go before the separator;--runtime-home can isolate the cache. Stop when locked artifact digest verification fails, the installation is corrupted, or the platform is unsupported; do not modify PATH and do not perform floating upgrades. The native help entry point is help; the launcher's own --help only describes launch parameters.
Scenario operations
Verify this scenario's inputs, native project, target object, version, and output boundaries. According to scenario guide , select the current command, save an independent checkpoint, then execute; after completion, reopen the native project and check the actual output and non-target content.
describe <id> verify the parameters, then use exec <id> <JSON> or run <JSONL>; write commands must be saved in the same batch or used with --save-as。
After the native export completes, decode and check dimensions, frame rate, duration, and audio tracks, and record exchange losses.
Native composition and source project revisions use this skill's built-in scripts/workflow.py; read Workflow Contract, templates are in this skill's examples. Modify only authorized objects; native projects and dependency assets are preserved; derived-format loss is read from the Exchange Report。
Verification and Recovery
A non-zero command exit is not considered complete; you need to inspect the actual saved project, export, dimensions, and media decoding. Mark timeout results as unknown; check the original task/project first; do not automatically replay edits. Existing native workflows support Save As revisions; refuse to overwrite when the corresponding project summary does not match.
On-Demand Reference and Handoff
- Actual Command Evidence: fixed-version observations, for routing and parameter reference only; real-time results take priority; disabled items are not executed.
- Workflow Contract: composition operations, native saving, dependency collection, and revisions.
- Hand off to filmcraft-cli-setupwhen installation/diagnostics require it, and hand off full task routing to filmcraft-use; when the skill is missing, use
npx skills add full-aigc-skills/filmcraft-skills --skill <skill-name>. Do not load other skills via adjacent file paths.
This skill does not provide a fictitious login interface; local headless does not require a cloud account. Full GUI, cross-editor fidelity, and creative quality are stated according to actual evidence.
Full Native Command Usage
The current skill includes the parameter documentation and in-session entry points for the full catalog, not subject to the creative template allowlist. Read the Full Usage Guide, and query the Command Referenceas needed; each instruction has a skill route, prior observations, and acceptance status.
: "${READ_ROOT:?Set READ_ROOT to an existing independently authorized directory}"
: "${RUNTIME_HOME:?Set RUNTIME_HOME to an existing independently authorized directory}"
: "${SKILL_DIR:?Set SKILL_DIR to an existing independently authorized directory}"
: "${WRITE_ROOT:?Set WRITE_ROOT to an existing independently authorized directory}"
python3 -I -B "$SKILL_DIR/scripts/commands.py" list --filter QUERY
python3 -I -B "$SKILL_DIR/scripts/commands.py" describe COMMAND_ID
python3 -I -B "$SKILL_DIR/scripts/commands.py" run "$SKILL_DIR/examples/commands-advanced.json" --output /absolute/new-command-result --runtime-home "$RUNTIME_HOME" --read-root "$SKILL_DIR" --read-root "$READ_ROOT" --write-root "$WRITE_ROOT" --write-root "$RUNTIME_HOME"
Before executing new entry points, check the actual registry and current executable status, retain return value references and step-by-step receipts; do not pass off semantic errors or timeouts as success. Catalog coverage and direct native use do not mean all instructions, GUI, delivery, or Art orchestration have been accepted.
The full workflow command gateway is in the Usage Instructions. For the fixed CLI, the version and artifact digests are based on this skill's built-in scripts/runtime.lock.json ; the skill package version is based on the corresponding release tag. Independent installation re-verification and full command-by-command acceptance are recorded separately; release does not replace acceptance.
For GUI tasks, you may first use this skill's built-in Fixed Desktop Installation; installation, startup, and actual GUI editing are verified separately.
Full attribution commands are listed by command family in the Categorized Usage List; each item's parameters can be viewed through this skill's commands.py describe ; the general CLI list also retains all commands not assigned to specialized skills.
For this skill's tasks, first read the Specialized Task Templates, and execute according to the corresponding inputs, first task, failure boundaries, local revisions, and verification. When combining across capabilities, then read the Full Business Scenarios。
On installation failure, read the First-Use Diagnostics, and use the receipt to locate the current skill's own setup entry point; handle installation failures and native invocation failures separately.
For competing execution on the same target and interruption registration, see this skill's Execution Registration; skill source dev.29 includes the implementation, and plugin fixed-installation acceptance is recorded separately.
For consecutive operations, prefer this skill's built-in Task-Level Session: start once, check, save, and rework plan by plan, sharing the same FilmCraft instance; exit only when the task ends. A single run still retains the original compatible behavior.