| name | office-desktop |
| description | Use when the user asks about Microsoft Office files on disk from Innate Desktop (not inside Word/Excel/PowerPoint) — "find my .docx about X", "what's in this spreadsheet", "summarize this report.docx", "pull the text out of this deck". Here there are no office_* tools; work the files on disk and hand rich editing back to the Office side panel. |
| license | MIT |
| metadata | {"category":"office-routing","primary-interface":"file tools on disk (read/triage) + handoff to the Office side panel"} |
| triggers | ["Word","Excel","PowerPoint","docx","xlsx","pptx","spreadsheet","document","文档","表格","演示文稿"] |
Office files from Innate Desktop
You are in Innate Desktop, not inside Word/Excel/PowerPoint. There are no
office_* tools here — those drive a live document inside the Office side
panel. From Desktop you act on the files as they sit on disk.
.docx, .xlsx, and .pptx are OOXML — a zip archive of XML parts. That
shapes what's easy and what isn't.
What works well from Desktop
- Find / list Office files by name, folder, or recency using your file
tools.
- Read the text for summarizing or Q&A: unzip the file and read the text
parts —
word/document.xml (Word), xl/sharedStrings.xml + the
xl/worksheets/*.xml (Excel), ppt/slides/*.xml (PowerPoint). The XML is
verbose; extract the visible text, ignore the markup. If the user has a
converter on PATH (pandoc, textutil on macOS, libreoffice --headless),
prefer it for clean text.
- Convert / export with such a tool when the user wants Markdown, plain
text, CSV, or PDF out of an Office file.
What to hand off, not hack
Do not try to make rich, formatting-preserving edits by hand-editing the
OOXML — it's brittle and easy to corrupt. When the user wants to edit a Word
doc, build a spreadsheet with formulas, or author a deck:
- Tell them to open the file in Word/Excel/PowerPoint and use the Innate side
panel there, where the
office_* tools edit the live document safely
(tracked changes, formulas that recalculate, real layout placeholders).
- You can still help prepare the content (draft the text, outline the deck,
compute the numbers) for them to drop in, or via the side panel.
Working style
- Confirm the file path before reading or converting; don't guess which file
"this report" is when several match — ask.
- Reading/extracting is safe; writing or overwriting an Office file on disk is
not casual — confirm with the user first, and never clobber the original
without saying so.
- Frame your help around the user's document task, not zip/XML mechanics.
