Before executing the specific method, read Craft scenario commands and parameters, and follow the object selection, session, input replacement, and result checking described therein.
Task starting point
First read the assets, and confirm the delivery purpose, target size or duration, modification scope, and required formats. 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 it to the vectorcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/vectorcraft-skills --skill vectorcraft-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 publication.
Execution steps
- Verify values, units, baselines, and ordering.
- Choose bar, line, or grouped charts that match the data relationships, and preserve proportions.
- Create separate groups for axes, legends, and labels, and establish styles.
- Check long labels, negative numbers, and extreme values, then export.
Tool implementation
Use open_file/run_command to manage graphics, inspect_document to check objects; draw_shape or run_command to edit, save_file to save, screenshot to view.
First read the actual tool schema, then fill in the parameters; use the returned values for object or document IDs. The queried commands must be available on the current backend. Choose a new output path before saving, and keep the input. If the required algorithm, format, or command does not exist, state the gap; do not pass off a similar name as the real thing.
Result checking
- Axis ticks and area encoding are accurate.
- Do not truncate important baselines in a way that misleads readers.
- Keep value descriptions and editable objects.
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 whole 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, 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 later requests rework, read this source project and make local modifications, preserving the accepted content.