This skill is responsible for organizing existing voiceover and music, gain, mixing, and audio-video sync. 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 providing 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 must not be derived from plans or asset metadata. Plans, assets, and source deliverables must be located under a read root, and deliverables and their parent directories must be located under a 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, skills, registration inputs, and source projects. Current root-isolated execution supports macOS headless; the desktop entry point 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
The 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, required derived outputs, and verification records. Report installation success, command directory existence, and completion of the creative task 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 an existing task authorization covers the necessary dependencies, directly execute this skill's installer and do not create a separate approval process.
Set SKILL_DIR to the directory containing this actually loaded SKILL.md (absolute path). User-level installation may be located at ~/.agents/skills/filmcraft-cli-audio, project-level may be located at .agents/skills/filmcraft-cli-audio, and plugins may be located in its skills/filmcraft-cli-audio 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
After the CLI argv -- , the native subcommand must come 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, 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 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 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 combined with --save-as。
Use user-provided or authorized voices; this skill does not promise voice generation. Decode the finished output and verify the audio track, start time, and synchronization.
Native composition and source project revisions use this skill's built-in scripts/workflow.py; read the workflow contract, with templates in this skill's examples. Modify only authorized objects; preserve the native project and dependent assets; for derived-format loss, read the interchange report。
Verification and Recovery
A nonzero 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: fixed-version observations, 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.
- When installation/diagnostics are needed, hand off to filmcraft-cli-setup; for full task routing, hand off 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 through adjacent file paths.
This skill does not provide a fictitious login interface; local headless does not require a cloud account. Complete GUI, cross-editor fidelity, and creative quality are stated based on actual evidence.
Complete native commands use
The current skill includes parameter descriptions for the complete directory and same-session entry points, and is not limited by the creative template allowlist. Read the complete usage guide, and query 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 actual registry and current executable status, and 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.
For the complete workflow command gateway, see the usage instructions. For the fixed CLI version and artifact digest, use this skill's built-in scripts/runtime.lock.json as the standard; 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 is not a substitute for 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.
Complete attributed 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 template, and execute according to the corresponding inputs, first task, failure boundaries, partial revisions, and verification. When combining across capabilities, then read the complete business scenarios。
If installation fails, 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 same-target execution contention and interruption registration, see this skill's execution registration; the skill source dev.29 includes the implementation, and plugin fixed-installation acceptance is recorded separately.
For continuous 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 is finished. A single run still retains the original compatible behavior.