First read the real input, then choose a workflow by the relevant categories below. The example data in the tables does not represent actual business facts. By default, each entry creates a new empty file and does not directly overwrite the original document.
- business: 3 items: project kickoff statement, decision record and candidate option table, business letter with header and footer.
- procedure: 1 item: executable SOP and stop conditions.
- publishing: 2 items: user-facing release notes, two-column internal brief.
- education: 1 item: training handout and standalone exercise page.
- editing: 1 item: edited copy with unified terminology.
Invocation and Session
When the host has opened the embedded editor, use that same MCP session and wait for editor_status to be ready; after reading the host tool schema, execute one by one with run_command {"command":"方法ID","params":{…}} . Tool names and parameters differ due to host adaptation; changes made by a standalone CLI file cannot be called same-screen editing.
Standalone CLI syntax:wordcraft-cli run --cmd <id=JSON> --save output.docx. The value of each --cmd is a single argv parameter consisting of the method ID, an equals sign, and a JSON object. Put the entire set of steps in the same run to avoid losing the cursor, current table, or shape selection. Use the 0.7.0 native CLI command catalog as the observation basis; query the actual version and schema before execution. After saving, reopen in a new process and check the content, formulas, or objects; check export formats separately.
Structured stepsobservable assertions including test inputs;command evidenceproves the method was observed in a fixed runtime, not that the scenario effect 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 the numbering is document structure, body text and section layout are handled separately, and the revised copy retains context, readstore workflow adaptation, and use the corresponding Craft method and actual result checks. Upstream skills are not runtime dependencies.
main development candidate
When using the main candidate with new commands to create native headers and footers, filtered/sorted mail merge, or adjust internal document links, first readmain new workflows and parameter changes. This reference clearly lists version boundaries; the original stable release does not guarantee support.