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. Directly adopt reasonable defaults for details that can be determined from the task and assets; 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
- Confirm the duration, frame size, and transparent background requirements, and import the vector or high-resolution logo.
- Set up the composition and safe area, and design the main motion using position, scale, or opacity.
- Adjust the keyframe easing, and leave enough readable hold time for the logo.
- Check the start, peak, and end frame by frame, and output the preview and target format.
Tool implementation
Use command_list to read the current Web engine commands; the id and params of command_run correspond to the actual execute interface; inspect checks the frame, save_project saves the new project path, and save_file retrieves the generated virtual file.
First read the actual tool schema, then fill in the parameters; use the return values for object or document IDs. The queried commands must be available on the current backend. Before saving, choose a new output path and keep the input. When the required algorithm, format, or command does not exist, explain the gap, and do not pass off a similar name as the real thing.
Result checking
- The logo proportions remain unchanged, and the motion is not abrupt.
- The transparent background requirement actually preserves alpha.
- The project contains editable layers and keyframes.
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, end, and key segments. For abnormal results, first check the current project 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 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 make local modifications, preserving the accepted content.
Skill store scenario experience
When encountering a purposeful logo entrance, readstore workflow adaptation, and use the corresponding Craft method and actual result checking. Upstream skills are not used as runtime dependencies.