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 modifications, and required format. Directly adopt reasonable defaults for details that can be determined from the task and materials; 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 publication.
Execution Steps
- Confirm the revenue, refunds, taxes, and currency basis.
- Clean the key fields and summarize by period and dimension.
- When calculating year-over-year or period-over-period changes, verify periods of equal length.
- Recalculate totals using detail samples, and generate an overview and an exception list.
Tool Implementation
Use open_workbook/new_workbook to manage workbooks; read_range to inspect, set_cell to edit, execute_command with complete commands; save_workbook to save.
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. Before saving, choose a new output path and keep the input. When 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
- The summary matches the total of the details.
- Refunds and null values are handled according to explicit rules.
- Formula references do not include duplicate total rows.
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 inspect 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 content requires the user's judgment. List only files that actually exist and have been checked. If the user subsequently requests rework, read this session's source project and make local modifications, preserving the content that has already been accepted.