Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking within.
Task Starting Point
First read the materials, confirm the delivery purpose, target size or duration, modification scope, and required format. Details that can be determined from the task and materials 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 lightcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/lightcraft-skills --skill lightcraft-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
- Confirm the delivery set, purpose, and size rules.
- Select quality and format according to purpose, and retain the original images and development parameters.
- First export one image to check color, sharpening, and watermark position.
- After batch export, verify the count, file names, and decodability.
Tool Implementation
Use command_run to call the actual LightCraft command interface, and inspect to query library.info. The current Web version has no real-time command_list; only call verified version commands. open_file requests import, then check the library; output is written back to the workspace via browser export.
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 retain the input. If the required algorithm, format, or command does not exist, explain the gap; do not pass off a similar name as a substitute.
Result Checking
- Do not change proportions due to scaling.
- List color anomalies, empty files, and failed items separately.
- The Web version library also needs to be exported via a backup command; browser storage cannot be treated as workspace files.
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, first check the current project to avoid repeatedly executing 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 make local modifications, retaining the accepted content.