Before executing the specific method, read Craft Scene Commands and Parameters, and execute according to the object selection, session, input replacement, and result checking within.
Task Starting Point
First read the assets, confirm the delivery purpose, target size or duration, modification scope, and required format. Details that can be determined from the task and assets should directly adopt reasonable defaults; only ask about missing conditions that would change the result.
When a visible editor is needed, hand off to the effectcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/effectcraft-skills --skill effectcraft-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
- Verify the output size, frame rate, duration, and transparency requirements.
- Confirm the work range and audio start and end, and disable test layers.
- Render a short segment first to check the effect, then render the full range.
- Reopen the output to check the first and last frames, duration, and alpha channel.
Tool Implementation
Use command_list to read the current Web engine commands; command_run's id and params correspond to the actual execute interface; inspect checks the image, save_project saves the new project path, and save_file retrieves the generated virtual file.
Read the actual tool schema first, then fill in the parameters; use the return values for object or document IDs. The queried commands must be available on the current backend. Choose a new output path before saving, and keep the input. If the required algorithm, format, or command does not exist, explain the gap; do not pass off a similar name as the real thing.
Image sequence delivery follows the native Craft Scene Commands and Parameters native render parameters and verifies the actual frame count and size; a successful project save-as does not mean it has been exported.
Result Checking
- Only check the actual file after the render task is complete.
- Do not treat a preview frame as a complete video.
- If output fails, keep the project and error information, and avoid rerunning without basis.
Check the actual content against the user's goal, not just the process exit code. For local edits, check local details; for layout tasks, check the whole page; for time-based media, check the start and end and key segments. For abnormal results, check the current project first to avoid repeating 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 requires the user's judgment. List only files that actually exist and have been checked. If the user subsequently reworks it, read this source project and modify it locally, preserving the accepted content.
Skill Store Scenario Experience
When editable projects and renders are accepted separately, readStore Workflow Adaptation, and use the corresponding Craft methods and actual result checking. Upstream skills are not runtime dependencies.