This skill is responsible for adjusting shot color and using LUTs and color presets with clear licensing. It hands off to skills in the same package by name, can be used when installed alone, and does not read sibling directories. It invokes the fixed released filmcraft-cli and preserves native editing projects.
Trusted Directory Permissions
Old cli.py Project reading and editing forwarded natively also require providing 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, authorized by the user/host, and cannot be inferred 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 independent, explicitly authorized write root; editing native processes is always prohibited from modifying this cache, skill, 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 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. 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, first verify the summary. Return the actual CLI results, the saved native project, required derived outputs, and verification records. Report installation success, command directory existence, and creative task completion separately.
First Use and Public Entry Point
Locate the real directory of the current SKILL.md. Currently supports macOS arm64 and Python 3.11+; the fixed CLI is installed to the user data directory. When existing task authorization covers the necessary dependencies, directly execute this skill's installer without creating a separate approval process.
Set SKILL_DIR to the directory (absolute path) where this SKILL.md actually loaded by the host is located. User-level installations may be located at ~/.agents/skills/filmcraft-cli-color, project-level ones may be located at .agents/skills/filmcraft-cli-color, and plugins may be located in their skills/filmcraft-cli-color or host cache directory; use the actual load path as the standard, do not guess based on the current working directory, and do not search and then 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
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 explains startup parameters.
Scenario Operations
Verify this scenario's inputs, native project, target objects, version, and output boundaries. According to Scenario Guide select the current command, save an independent checkpoint, and then execute; after completion, reopen the native project and check the actual output and non-target content.
describe <id> Verify parameters, then use exec <id> <JSON> or run <JSONL>; write commands must be saved in the same batch or used with --save-as。
Verify the workspace and the LUT source; compare sampled frames before and after rendering—do not treat writing parameters as correct color.
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; for derived format loss read exchange report。
Verification and recovery
A non-zero command exit does not count as completion; the actual saved project, export, dimensions, and media decoding need to be inspected. Mark timeout results as unknown; check the original task/project first; do not automatically replay edits. Existing native workflows support save-as revisions; when the corresponding project summary does not match, refuse to overwrite.
On-demand reference and handoff
- actual command evidence: observations for pinned versions, used only as routing and parameter reference; live results take priority; disabled items are not executed.
- workflow contract: composition operations, native saving, dependency collection, and revisions.
- When installation/diagnostics are needed, hand off to filmcraft-cli-setup; full task routing is handed off 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.
Full native command usage
The current skill includes parameter descriptions and same-session entry points for the complete catalog, and is not limited by the creative template whitelist. Read complete usage guide, query on demand command reference; 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, and retain return value references and step-by-step receipts; semantic errors or timeouts must not be passed off as success. Catalog coverage and direct native use do not mean that all commands, GUI, delivery, or Art orchestration have been accepted.
The complete workflow command gateway is in usage instructions. The version and artifact digest of the pinned CLI 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 pinned desktop installation; installation, startup, and actual GUI editing are verified separately.
Complete attribution commands are listed by command family in categorized usage list, and each item can be viewed through this skill's commands.py describe for parameters; the general CLI list also retains all commands not assigned to specialized skills.
For tasks in this skill, 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。
If 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.
For same-target execution contention and interruption registration, see this skill's execution registration; skill source dev.29 includes 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 each plan sequentially, sharing the same FilmCraft instance; exit only when the task ends. A single run still retains the original compatible behavior.