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 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
- List formula cells and key summaries, and identify error values.
- Check adjacent formula patterns, and locate breaks and unexpected constants.
- Verify whether absolute references, cross-sheet references, and newly added rows are included in the range.
- Manually calculate key results with a small sample, then fix.
Tool implementation
Use open_workbook/new_workbook to manage workbooks; read_range to check, set_cell to edit, execute_command to use complete commands; save_workbook to save.
First read the actual tool schema, then fill in parameters; use return values for object or document IDs. Queried commands must be available in 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 check
- Changes in key totals before and after the fix are explainable.
- Do not mechanically change legitimate differences into identical formulas.
- After saving, recalculate and check for circular references and error values.
Check the actual content against the user's goal, 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 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 content that has been accepted.