Before executing specific methods, 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, modification scope, 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 publication.
Execution steps
- Determine the learning objectives and the audience's baseline, and split into short chapters.
- Pair each concept with an example, then arrange exercises.
- Put long passages of script into speaker notes or a separate document, and make the pages highlight diagrams.
- Check exercise answers, chapter pacing, and font size.
Tool implementation
Use open_presentation/new_presentation to manage the presentation; 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 return values for object or document IDs. Queried commands must be available on the current backend. Choose a new output path before saving, and preserve the input. When required algorithms, formats, or commands do not exist, state the gap; do not pass off a similar name as the real thing.
Result checking
- Exercises correspond to the objectives, and answers are correct.
- Examples are readable, and charts can be understood without relying on verbal explanation.
- Deliver editable courseware and exercise instructions.
Check the actual content against the user's goals, not just the process exit code. For partial edits, inspect the partial 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 description: what modifications were made, which steps were not executed due to current capabilities, and what needs user judgment. List only files that actually exist and have been checked. If the user subsequently requests rework, read this source project and modify it locally, preserving the content that has been accepted.