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. 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 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
- Organize by shooting batch, and first exclude files that cannot be decoded.
- Check for out-of-focus, closed eyes, severe shake, and duplicate compositions; mark them rather than deleting them directly.
- Among similar photos, choose the version with better expression and details.
- Generate a selected set and a to-be-processed list.
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. After open_file requests import, check the library again; output is written back to the workspace through 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 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.
Result checking
- Do not misjudge a low-exposure preview as a reject.
- Do not delete the original photos; keep ratings and culling reasons.
- The number of selected items matches the set contents.
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 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 requires user 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 content that has already been accepted.