Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, sessions, input replacement, and result checking described therein.
Task Starting Point
First read the footage, and 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 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; before release, use the local companion plugin, and do not treat this installation command as proof of release.
When the subtitles are known to be uniformly early or delayed, readconstant offset and precise export, execute the companion script, and verify the new project and SRT/VTT.
Execution Steps
- Confirm the subtitle source and language, and proofread names and numbers.
- Break lines by semantics, and control the number of characters per screen and dwell time.
- Align in and out points, and avoid misreading caused by crossing shots.
- Check the platform safe area, and export the subtitle file or burned-in version.
Tool Execution
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 the 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. When the required algorithm, format, or command does not exist, state the gap; do not pass off a similar name as a substitute.
Result Checking
- When there is no ASR capability, do not claim that automatic transcription has been performed.
- The timeline has no overlaps, missing lines, or obvious delays.
- The delivered subtitles correspond to the video version.
Check the actual content against the user's goal, 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, the actual derived files, and a brief explanation: what modifications were made, which steps were not executed due to current capabilities, and what content requires the user's judgment. List only files that actually exist and have been checked. If the user subsequently requests rework, read this source project and make local modifications, preserving the accepted content.
Skill Store Scenario Experience
When delivering subtitles based on actual dialogue, readStore workflow adaptation, use the corresponding Craft method and check the actual results. Upstream skills are not a runtime dependency.