StackMap
Subscribe

anydoc vs OfficeCLI

Rust library converting Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV and PDF to clean Markdown in single-digit milliseconds — Node/Python/WASM bindings, CLI, and an agent skill. — versus — 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.

The curated verdict

Both handle Word/PowerPoint/Excel for agents. anydoc converts them to Markdown in single-digit milliseconds — read-only; OfficeCLI reads, writes and renders them. If the file is input, anydoc; if it's the deliverable, OfficeCLI.

anydocOfficeCLI
Stars20k30k
Forks1.2k2.1k
LanguageRustC#
LicenseMITApache-2.0
Last activity8 days ago2 days ago
Topicsocrskills, ocr
Curated connections63

anydoc — the curator's take

The right scope discipline: structural conversion only, brutally fast, one consistent Markdown out regardless of input — and the WASM demo means files never leave the machine. Ships as an agent skill, so agents read office docs without a service. When NOT: scanned pages — there is no OCR in it (that's Firecrawl's hosted Parse upsell), so image-heavy PDFs come back empty; for layout-model parsing of messy documents you still want the heavyweight pipelines.

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.