| name | Msoffice |
| description | Create MS Word and PowerPoint documents on any topic. USE WHEN user wants: documents, reports, word docs, presentations, slides, powerpoint, decks. |
MS Office Document Generator
Creates professional Word (.docx) and PowerPoint (.pptx) documents.
Workflow Selection
| User Intent | Workflow | Output |
|---|
| "document", "report", "word", "write up" | Templates/Word.md | .docx |
| "presentation", "slides", "powerpoint", "deck" | Templates/PowerPoint.md | .pptx |
Quick Reference
Tool Location: ~/.claude/Skills/MSOffice/Tools/generate.py
Python Interpreter: ~/.claude/Skills/MSOffice/venv/bin/python
Output Directory: ~/Downloads/ (for review before delivery)
Usage Pattern
- Understand the user's topic and document requirements
- Research the topic if needed (use Research skill for comprehensive content)
- Structure content into the appropriate JSON format — build the COMPLETE JSON in your thinking before running any command
- Generate document using the CLI tool — pass the FULL content in a single command
- Verify the command completed successfully (exit code 0, file exists)
- Inform user of file location
⚠️ CRITICAL: Preventing Truncation
JSON content passed via --content must be fully complete before execution. Never truncate or abbreviate content mid-generation.
For Word documents: Include ALL sections with full prose text. Minimum for business reports: executive summary, findings (numbered), metrics/KPIs, actions (with owner + due date), conclusion.
For PowerPoint: Include ALL slides fully defined. Minimum for business presentations: title, agenda, problem, solution, financials/ROI, risks, recommendation, next steps (8+ slides). MANDATORY: Write the COMPLETE JSON for ALL slides as a visible code block in your response, count the slides to confirm 8+, verify no slide is truncated mid-content, THEN execute the command. Never start the command until every slide object is fully closed with }.
If content is large: Write the entire JSON structure in your response first as a code block, verify it is complete, THEN execute the command with that exact content. Do not run the command with placeholder or abbreviated content.
Document Delivery
Files are saved to ~/Downloads/ by default. User can:
- Access locally on Mac
- Download via Kai Mobile App (browse to ~/Downloads/, tap file, download)
CLI Usage
~/.claude/Skills/MSOffice/venv/bin/python ~/.claude/Skills/MSOffice/Tools/generate.py \
--type word \
--title "Document Title" \
--content '{"sections": [...]}' \
--output ~/Downloads/filename.docx
~/.claude/Skills/MSOffice/venv/bin/python ~/.claude/Skills/MSOffice/Tools/generate.py \
--type powerpoint \
--title "Presentation Title" \
--content '{"slides": [...]}' \
--output ~/Downloads/filename.pptx
Examples
Example 1 — Business report (Word)
User: "Write a report on Q2 sales performance"
→ Routes to Templates/Word.md, generates ~/Downloads/Q2-Sales-Report.docx with executive summary, findings, KPIs, actions, and conclusion sections.
Example 2 — Investor deck (PowerPoint)
User: "Create a pitch deck for our new product"
→ Routes to Templates/PowerPoint.md, generates ~/Downloads/pitch-deck.pptx with 10+ slides: title, problem, solution, market size, traction, financials, team, next steps.
Example 3 — Policy document (Word)
User: "Draft an IT security policy document"
→ Routes to Templates/Word.md, generates ~/Downloads/IT-Security-Policy.docx with numbered policy sections, sub-headings, and owner/review-date fields.
