First read the actual input, then select a workflow by the relevant categories below. The example data in the tables does not represent actual business facts. Each item creates a new empty file by default and does not overwrite the original draft directly.
- report: 2 items: a one-page management metric brief, and a risk four-quadrant reporting page.
- decision: 1 item: an editable option comparison table.
- diagram: 1 item: an approval-step flowchart.
- data: 1 item: an actual-versus-plan trend chart.
- presentation: 2 items: a problem-and-result narrative for a product demo, and handoff-ready speaker notes.
- education: 1 item: training Q&A with hidden answer pages.
Invocation and session
When the host has the embedded editor open, use that same MCP session and wait for editor_status to be ready; after reading the host tool schema, execute item by item with run_command {"command":"方法ID","params":{…}} . Tool names and parameters differ depending on host adaptation; file changes made by the standalone CLI cannot be called same-canvas editing.
Standalone CLI syntax:deckcraft-cli run --cmd <id=JSON> --save output.deckcraft. The value of each --cmd is one argv argument made up of the method ID, an equals sign, and a JSON object. Put the entire step group in the same run to avoid losing the cursor, current table, or shape selection. When combining multiple scenarios, run file.newonly once, skip the newDocumentOnly:true step in the remaining workflows, and start from slide.new ; when adding notes to an existing page, use the actual page index and do not create an example page. The comparison table and trend chart can be merged into one presentation this way, keeping each page's own notes. Use the 0.7.0 native CLI command catalog as the observation basis; query the actual version and schema before executing. After saving, reopen in a new process and check the content, formulas, or objects; check export formats separately.
Structured stepswith observable assertions including test input;Command evidenceproves the method was observed in a fixed runtime, not that the scenario outcome has been accepted.Sources and licensesrecords the referenced GitHub workflow facts; the body text and parameter examples are original adaptations, and no external Office scripts were executed.
Skill store scenario experience
When you need to support a demo narrative with evidence, compare options in a structured way, and check the script and visible pages separately, readStore workflow adaptation, and use the corresponding Craft method and actual-result checks. Upstream skills are not a runtime dependency.
main template and reuse
When using a starter template in the main candidates or inserting a specified page from a brand document, readmain new workflow and catalog changes. CLI help has changed to human-readable text; use the current MCP method for structured discovery.
Comparison table in-depth operations
When you need an explicit table ID, full column widths, source notes, and to edit cells after reading back the PPTX, hand it to the deckcraft-option-comparison skill. Standalone install:npx skills add full-aigc-skills/deckcraft-skills --skill deckcraft-option-comparison. This entry deepens the existing comparison table scenario and does not add a separate scenario count; it is provided as a pre-release with the companion plugin under development.