This skill is responsible for checking existing audio/video, image, and asset references, and importing and collecting or relinking assets. 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 the native editing project.
Trusted directory permissions
Legacy cli.py Native forwarded project reading and editing also require an independent root parameter before -- ; only exact version/help/no-project-directory queries are compatible with legacy invocation. 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 asset metadata. Plans, assets, 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 are always prohibited from modifying this cache, skill, registration inputs, and 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, and only open 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, assets, 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 verification records. Installation success, command directory existence, and creative task completion are reported separately.
First-time 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, directly execute this skill's installer without creating a separate approval process.
Set SKILL_DIR to the directory (absolute path) where the host actually loads this SKILL.md . User-level installations may be located at ~/.agents/skills/filmcraft-cli-media, project-level may be located at .agents/skills/filmcraft-cli-media, plugins may be located in their skills/filmcraft-cli-media or host cache directory; use the actual loaded 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'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 be placed first. Installation parameters go before the separator;--runtime-home can isolate the cache. Stop when locking the artifact digest 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 object, 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 the parameters, then use exec <id> <JSON> or run <JSONL>; write commands must be saved in the same batch or used with --save-as。
probe checks streams, frame rates, and audio tracks; after moving assets, relink according to the summary, and do not replace based solely on matching names.
Native composition and source project revision use this skill's built-in scripts/workflow.py; read the workflow contract, whose template is in this skill's examples. Modify only authorized objects, retain the native project and dependent assets, and for derived format loss read the exchange report。
Verification and recovery
A nonzero command exit does not count as completion; the actual saved project, exports, dimensions, and media decoding need to be inspected. Mark timeout results as unknown, check the original task/project first, and do not automatically replay edits. The existing native workflow supports saving a revision; refuse to overwrite when the corresponding project summary does not match.
On-demand reference and handoff
- Actual command evidence: observed at pinned versions, used only as routing and parameter reference; live results take precedence, and disabled items are not executed.
- Workflow contract: composition operations, native saving, dependency collection, and revision.
- When installation/diagnostics are needed, hand off to filmcraft-cli-setup; 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.
For workspace segmented asset consumption candidates, see segmented assets. Pinned release and Art integration still await acceptance, and candidate handoff must not be treated as a complete five-plugin delivery.
Full native command usage
The current skill includes parameter descriptions for the complete catalog and same-session entry points, and is not subject to the creative template allowlist. Read the full usage guide, and consult the command referenceas needed; each instruction has a skill route, prerequisite 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 a new entry point, check the real 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 instructions, GUI, delivery, or Art orchestration have been accepted.
For the full workflow command gateway, see usage instructions. The pinned CLI 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 per-command acceptance are recorded separately, and 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.
Full attribution commands are listed by command family in the categorized usage list; each item's parameters can be viewed via 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 template, and execute according to the corresponding inputs, first task, failure boundaries, local revision, and verification. When combining across capabilities, then read the complete business scenarios。
When installation fails, read the first-use diagnostics, and use the receipt to locate the setup entry point of the current skill itself; installation failures and native call failures are handled separately.
For competing executions targeting the same goal and interruption registration, see this skill's execution registration; The skill source dev.29 includes the implementation; plugin fixed-installation acceptance is recorded separately.
For continuous operations, prioritize using 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.