Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking described therein.
Task starting point
First read the materials and confirm the delivery purpose, target size or duration, modification scope, and required format. Directly adopt reasonable defaults for details that can be determined from the task and materials; only ask about missing conditions that would change the result.
When a visible editor is needed, hand it over 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 installation command as proof of publication.
Execution steps
- Sort out real selling points and select wide shots, detail shots, and usage shots.
- Arrange the order from problem to solution and control the amount of information in each segment.
- Add accurate specification text and moderate transitions.
- Match the music beats and check the closing call-to-action information.
Explicitly open the source material and set the actual in/out points before insertion; the CLI's source.open, source in/out points, and source.insert must be executed in the same run. After insertion, adapt the aspect ratio using the actually returned clip ID and preserve the full frame; for parameter and return value replacement, see the above method manual.
Tool implementation
Use command_list to read the current Web engine commands; command_run executes on the visible page, inspect verifies; open_file imports materials, list_files checks exports, and save_project or save_file writes to a new path in the workspace.
Read the actual tool schema first, then fill in the 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 similar name as a substitute.
Result checking
- Do not fabricate product performance or test results.
- The model numbers in the text and visuals are consistent.
- Deliver an editable project and platform-size outputs.
Check the actual content against the user's goals, not just the process exit code. For local edits, view local details; for layout tasks, view the entire page; for time-based media, view the start, end, and key segments. For abnormal results, check the current project first to avoid repeatedly performing 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 needs the user's judgment. List only files that actually exist and have been checked. If the user later requests rework, read this source project and make local modifications, preserving the accepted content.