This skill is responsible for creating, opening, and saving fcproj and organizing sequences and bins. Hand off to skills in the same package 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
Legacy cli.py project reading and editing forwarded natively also require an independent root parameter before -- ; only exact version/help/no-project directory queries remain compatible with legacy 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, authorized by the user/host, and must not be derived from plans or material metadata. Plans, materials, and source deliverables must be located under the read root, and 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; the native editing process is always prohibited from modifying this cache, the skill, registration inputs, and the source project. 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 assigned 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. See details of the boundaries in Execution Permissions。
Inputs and Deliverables
The inputs are the user-confirmed task, materials, project or object, output directory, and modification scope; when an existing project is required, verify the summary first. Return the actual CLI results, the saved native project, the required derived outputs, and verification records. Installation success, command directory existence, and completion of the creative task are reported separately.
First Use and Public Entry Point
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 and do not create a separate approval process.
Set SKILL_DIR to the directory (absolute path) of this SKILL.md actually loaded by the host. User-level installations may be located at ~/.agents/skills/filmcraft-cli-project, project-level ones may be located at .agents/skills/filmcraft-cli-project, and plugins may be located in their skills/filmcraft-cli-project or host cache directory; the actual loaded path prevails, do not guess based on the current working directory, and do not search and arbitrarily choose a duplicate version. The skill directory and the CLI's 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
In 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 startup parameters.
Scenario Operations
Verify this scenario's inputs, native project, target objects, version, and output boundaries. Follow Scenario Guide to select the current command, save an independent checkpoint, then execute; after completion, reopen the native project and check the actual outputs 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。
Before saving the original project, verify the summary; save as a new project and do not overwrite the user's parallel modifications.
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. Only modify authorized objects; retain the native project and dependency assets; for derived format loss read exchange report。
Verification and recovery
A non-zero command exit does not count as completion; you need to inspect the actually saved project, export, dimensions, and media decoding. Mark timeout results as unknown, check the original task/project first, and do not automatically replay edits. The existing native workflow supports save-as revision; refuse to overwrite when the corresponding project summary does not match.
On-demand reference and handoff
- Actual command evidence: observed at a pinned version, used only as routing and parameter reference; real-time results take precedence, and disabled items are not executed.
- workflow contract: composition operations, native saving, dependency collection, and revision.
- Hand off to filmcraft-cli-setupwhen installation/diagnostics are needed, and hand off complete task routing to filmcraft-use; when a 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.
Complete native command usage
The current skill's built-in complete directory parameter descriptions and same-session entry points are not restricted by the creative template whitelist. Read complete usage guide, and query command referenceas needed; each instruction has a skill route, prerequisite observation, 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 a new entry point, 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. Directory coverage and direct native use do not mean all instructions, GUI, delivery, or Art orchestration have been accepted.
The complete workflow command gateway is in usage instructions. For the pinned CLI, the version and artifact summary 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.
GUI tasks can first use this skill's built-in pinned desktop installation; installation, launch, and actual GUI editing are verified separately.
Complete attributed commands are listed by command family in categorized usage list, and 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 specialized task templates, and execute according to the corresponding inputs, first task, failure boundaries, local revisions, and verification. When combining across capabilities, then read complete business scenarios。
When installation fails, read first-use diagnostics, and use the receipt to locate the current skill's own setup entry point; handle installation failure and native invocation failure separately.
Execution contention for the same target and interruption registration are in this skill's execution registration; skill source dev.29 collects the implementation, and plugin pinned 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 its original compatible behavior.