Before executing the specific method, read Craft scene commands and parameters, and execute according to the object selection, session, input replacement, and result checking described therein.
Task Starting Point
First read the footage, confirm the delivery purpose, target size or duration, scope of modification, and required format. Details that can be determined from the task and footage 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
- First confirm that the camera format can be decoded correctly, and compare preview colors with actual rendered colors.
- Start with white balance and exposure, then recover highlights and shadows.
- Adjust curves and local contrast, avoiding halos and amplification of noise in dark areas.
- Finally crop and lightly sharpen, then export a reference image.
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 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 a substitute.
Result Checking
- Stop when colors are abnormal; do not use post-processing to forcibly correct incorrect decoding.
- Skin, neutral colors, and highlight details look natural.
- Preserve non-destructive development parameters and the original file.
Check the actual content against the user's goals, not just the process exit code. For local edits, inspect local details; for layout tasks, inspect the entire page; for time-based media, inspect 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 requests rework, read this source project and make local modifications, preserving the content that has already been accepted.