OfficeCLI vs univer
Office suite built for AI agents: one binary, no Office install, creates, reads and edits Word, Excel and PowerPoint, and renders them to HTML/PNG so the agent can see what it made. Ships as a skill. — versus — Office SDK for embedding spreadsheets, docs, slides, bases and PDFs in your own product — canvas rendering, formula engine, plugins and one Facade API across browser and Node.js.
Both let agents create and edit Word/Excel/PowerPoint-class documents; officecli is a single binary plus skill for file output, Univer a full embeddable SDK with live rendering and collaboration.
| OfficeCLI | univer | |
|---|---|---|
| Stars | 32k | 23k |
| Forks | 2.2k | 1.9k |
| Language | C# | TypeScript |
| License | Apache-2.0 | Apache-2.0 |
| Last activity | 5 days ago | yesterday |
| Topics | skills, ocr | office, data |
| Curated connections | 4 | 2 |
OfficeCLI — the curator's take
When an agent has to *produce* a .docx, .xlsx or .pptx rather than merely read one: `officecli install` puts the binary on PATH and drops the skill into every coding agent it finds (Claude Code, Cursor, Windsurf, Copilot), `officecli watch deck.pptx` gives a live browser preview, and the built-in renderer closes the render → look → fix loop that makes generated documents actually acceptable. 30k stars, Apache-2.0, single C# binary on every platform. NOT for extraction pipelines — if you only need text and tables out of Office files, a converter is lighter — and NOT a document design system: it executes edits, it doesn't know what a good slide is.
univer — the curator's take
Pick it when you're building a product where people and agents edit real spreadsheets and docs side by side — embeddable, runs server-side too, composable via plugins. Overkill if your agent only needs to emit an .xlsx or .docx: officecli does that from one binary. Read the Open Source vs Pro section before committing — not every capability in the product family ships in this repo.