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 it over 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
- First split the copy semantically, and set the reading duration.
- Arrange the entrance order by phrase, and control displacement and opacity.
- Use a small amount of easing to form rhythm, and avoid a different effect for each character.
- Check readability according to the actual playback speed.
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 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. 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
- The text content is accurate, and punctuation is complete.
- Movement will not cause unreadability or go outside the safe area.
- Deliver editable text and the animation project.
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, check the current project first 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 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 encountering the need to first ensure comprehension before arranging animation, readStore workflow adaptation, and use the corresponding Craft method and actual result checking. Upstream skills are not used as runtime dependencies.