Before executing specific methods, read Craft scenario commands and parameters, and execute according to object selection, sessions, input replacement, and result checking therein.
Task starting point
First read the materials, confirm the delivery purpose, target size or duration, scope of modification, and required formats. 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; use the local companion plugin before release, and do not treat this install command as proof of publication.
Execution steps
- Keep the original draft, and mark the core information of each page and duplicate content that can be removed.
- Rebuild the heading hierarchy and alignment grid, and split overly dense pages.
- Unify chart colors and annotations, and reduce meaningless decoration.
- Check facts and numbers page by page against the original draft.
Tool implementation
Use open_presentation/new_presentation to manage presentations; 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. Choose a new output path before saving, and keep the input. If a required algorithm, format, or command does not exist, explain the gap; do not pass off a similar name as the real thing.
Result checking
- No information is lost, and order changes have a reasonable narrative.
- Font sizes, contrast, and chart labels are readable.
- Deliver the new version and a description of the main adjustments.
Check the actual content against the user's goals, not just the process exit code. For local edits, view local details; for layout tasks, view the whole page; for time-based media, view the start and end and key segments. For abnormal results, first check the current project to avoid repeatedly executing irreversible operations.
Delivery
Return the editable project, actual derived files, and a brief description: 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 later requests rework, read this source project and modify it locally, preserving the content that has been accepted.