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 assets, confirm the delivery purpose, target size or duration, modification scope, and required formats. Directly adopt reasonable defaults for details that can be determined from the task and assets; 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 publication.
Execution Steps
- Determine brand colors, font availability, and page margins.
- Design the cover, table of contents, text-and-image pages, charts, and closing page.
- Test the template with long titles, multiple images, and dense tables.
- Organize replaceable placeholder content and usage instructions.
Tool Implementation
Use open_presentation/new_presentation to manage presentations; add_slide, inspect_slide, inspect_document to operate and verify; save_presentation to save.
First read the actual tool schema, then fill in parameters; use the returned values for object or document IDs. Queried commands must be available on the current backend. Before saving, choose a new output path and preserve the input. If a required algorithm, format, or command does not exist, state the gap; do not pass off a similar name as a substitute.
Result Checking
- The template remains usable after font substitution on the target computer.
- Style hierarchy is consistent and editable.
- Do not mistakenly leave sample data in the final delivery.
Check the actual content against the user's goals, not just process exit codes. 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 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 requires user judgment. List only files that actually exist and have been checked. If the user later requests rework, read this source project and modify locally, preserving the content that has already been accepted.