Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking therein.
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
- Determine the matching key and one-to-many relationships, and standardize date and amount precision.
- Separately mark left-table-only, right-table-only, and common records.
- For common records, verify amounts, quantities, and status.
- Summarize the reasons for differences, and retain the original details and matching results.
Verify original keys as text, and after establishing a non-numeric prefix index in a confirmed blank auxiliary column, count quantities to avoid 001 and 1 being merged by COUNTIF; only a unique match can extract the amount; unmatched, duplicate keys, and missing primary keys should each retain their status, and you must not rely only on the first VLOOKUP result.
Tool implementation
Use open_workbook/new_workbook to manage workbooks; read_range to inspect, set_cell to edit, execute_command to use complete commands; save_workbook to save.
First read the actual tool schema, then fill in the 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 retain the input. If 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
- Duplicate keys must not be silently overwritten.
- Amount differences take explicit rounding rules into account.
- The totals on both sides and the total difference can be reconciled.
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, 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, retaining the content that has already been accepted.