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 off to the deckcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/deckcraft-skills --skill deckcraft-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
- Organize this week's results according to the goals, distinguishing completed, in progress, and blocked items.
- Present metric changes using a consistent basis, and retain the comparison period.
- Write issues as impact, cause, and next-step actions.
- Finally, list owners and timing, and check the amount of information on each page.
Tool Implementation
Use open_presentation/new_presentation to manage the presentation; use add_slide, inspect_slide, and inspect_document to operate and verify; use save_presentation 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 preserve the input. If the required algorithm, format, or command does not exist, explain the gap; do not pass off a similar name as a substitute.
Result Checking
- Numbers are consistent with the source data.
- Do not substitute activity counts for business results.
- Action items are specific and traceable, with no clipping within the page.
Check the actual content against the user's goals, not just the process exit code. For partial edits, inspect partial details; for layout tasks, inspect the full 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 content requires the user's judgment. List only files that actually exist and have been checked. If the user subsequently requests rework, read this source project and make partial modifications, preserving the content already accepted.