Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking described therein.
Task starting point
First read the materials and confirm the delivery purpose, target size or duration, scope of modification, and required format. For details that can be determined from the task and materials, adopt reasonable defaults directly; only ask about missing conditions that would change the result.
When a visible editor is needed, hand off to the gridcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/gridcraft-skills --skill gridcraft-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
- Define the audience, key metrics, and refresh frequency.
- Keep the detail data sheet and create summary and display sheets.
- Choose a small number of intuitive charts and unify units, periods, and colors.
- Check the display with empty data, extreme values, and newly added categories.
Tool implementation
Use open_workbook/new_workbook to manage workbooks; use read_range to check and set_cell to edit; use execute_command with complete commands; use save_workbook to save.
Read the actual tool schema first, then fill in parameters; use returned 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 a required algorithm, format, or command does not exist, state the gap; do not pass off a similar name as a substitute.
Result checking
- Write the metric definitions clearly.
- Chart ranges change with the data, and hidden-row rules are explicit.
- If pivot or dynamic chart capabilities are missing, deliver a maintainable static summary and explain.
Check the actual content against the user's goals, not just the process exit code. For local edits, check local details; for layout tasks, check the entire page; for time-based media, check the start, end, and key segments. For abnormal results, check the current project first to avoid repeating 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 modify locally, preserving the accepted content.