Before executing specific methods, read Craft Scene Commands and Parameters, and follow the object selection, session, input replacement, and result checking described therein.
Task Starting Point
First read the source material and confirm the delivery purpose, target size or duration, scope of modification, and required formats. For details that can be determined from the task and source material, adopt reasonable defaults directly; 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; use the local companion plugin before release, and do not treat this install command as proof of publication.
Execution Steps
- Confirm the target platform specifications and the source material frame rate.
- Check the sequence start and end, black frames, missing media, and silent tracks.
- First export a short sample to verify encoding, then export the complete file.
- Reopen the file and check the start and end, total duration, audio-video sync, and clarity.
Tool Implementation
Use command_list to read the current Web engine commands; command_run executes on the visible page, inspect verifies; open_file imports source material, 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. Choose a new output path before saving and preserve the input. If the required algorithm, format, or command does not exist, state the gap; do not pass off a similarly named one as a substitute.
Result Checking
- Do not treat successful task submission as completed encoding.
- No unexpected stretching, speed changes, or black bars.
- Retain the project and the list of dependent source materials.
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 and end and key segments. For abnormal results, first check the current project to avoid repeatedly performing irreversible operations.
Delivery
Return the editable project, the actual derived files, and a brief explanation: what modifications were made, which steps were not executed due to current capabilities, and what the user needs to judge. List only files that actually exist and have been checked. If the user requests rework afterward, read this source project and make local modifications, preserving the content already accepted.