Before executing the specific method, read Craft scene commands and parameters, and execute according to the object selection, session, input replacement, and result checking described therein.
Task starting point
First read the footage, confirm the delivery purpose, target size or duration, scope of modification, and required format. Directly adopt reasonable defaults for details that can be determined from the task and footage; only ask about missing conditions that would change the result.
When a visible editor is needed, hand off to the filmcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/filmcraft-skills --skill filmcraft-editor. The currently added skill is a local candidate; before release, use the local companion plugin, and do not treat this installation command as proof of release.
Execution steps
- Choose a reference shot and first assess differences in shooting color and exposure.
- Correct black and white points and white balance shot by shot, then match midtones.
- Finally add a unified style, avoiding using style to mask exposure problems.
- Repeatedly switch between adjacent shots to check.
When matching, explicitly specify the actual target clip; the reference frame must belong to another shot; do not carry over old selections after reopening the project.
Tool implementation
Use command_list to read the current Web engine commands; command_run executes on the visible page, inspect verifies; open_file imports footage, list_files checks exports, and save_project or save_file writes to a new path in the workspace.
First read the actual tool schema, then fill in parameters; use return values for object or document IDs. Queried commands must be available on the current backend. Before saving, choose a new output path and preserve the input. If the required algorithm, format, or command does not exist, state the gap; do not pass off a similar name as the real thing.
Result checking
- Skin tones and neutral objects do not shift abruptly.
- Highlights and shadows are not excessively clipped.
- Preserve per-shot adjustments for rework.
Check the actual content against the user's goals, not just the process exit code. For local edits, inspect local details; for layout tasks, inspect the whole page; for time-based media, inspect the start, end, and key segments. For abnormal results, first check the current project to avoid repeating irreversible operations.
Delivery
Return the editable project, actual derived files, and a brief explanation: what modifications were made, which steps were not executed due to current capabilities, and what requires user judgment. List only files that actually exist and have been checked. If the user subsequently reworks, read this source project and modify locally, preserving accepted content.
Skill store scenario experience
When encountering reference shot matching and style separation, readstore workflow adaptation, and use the corresponding Craft method and actual result checking. Upstream skills are not a runtime dependency.