$ show iOfficeAI/OfficeCLI
OfficeCLI is a cross-platform CLI application written in C#/.NET that creates, reads, and mutates OOXML Office documents (Word .docx, Excel .xlsx, PowerPoint .pptx) without requiring Microsoft Office. It is explicitly engineered as an agent-facing tool: every document element is addressable through a uniform path syntax (e.g. /slide[1]/shape[2]), all commands emit structured JSON with error codes and suggestions, and it ships AI-skill files for Claude/Copilot/Cursor/Codex, an MCP server, plus Python and Node SDKs. The core operation model is a batch command language: documents are mutated by replayable JSON items (add/set/remove/get) executed atomically through the CLI or over a named pipe to a resident process. Architecturally the repo is a single .NET binary (embedded runtime) with a CommandBuilder layer, a DocumentHandlerFactory dispatching to three large partial-class handlers (WordHandler, ExcelHandler, PowerPointHandler), and a shared Core layer containing chart-to-SVG rendering, a formula evaluator implementing 350+ Excel functions with statistical distributions, pivot table construction, Mermaid diagram parsing, OOXML theme/table-style resolution, HTML/PNG/SVG preview rendering, and a plugin protocol for foreign-format dump-readers and exporters. Security is taken seriously: SsrfGuard validates remote fetch targets, HyperlinkUriValidator allowlists URI schemes, XmlTextValidator and DocumentLimits guard against decompression bombs and DOM sprawl, and AtomicPackageWriter prevents torn file writes. Quality is strong but carries real maintenance debt. The code demonstrates deep OOXML craftsmanship - schema-order-correct XML insertion, exact EMU unit round-trips, Lanczos-based gamma functions, and curated chart-style galleries. However, handlers are split across dozens of partial-class files that evolved from former god methods, the property API is stringly-typed (props dictionaries parsed per key), examples must be maintained in parallel shell and Python twins, and the tool deliberately tolerates 'UNSUPPORTED props' warnings (exit code 2), which can mask incomplete feature coverage. The best reuse targets are the self-contained Core utilities rather than the format handlers. The project is actively maintained with multi-platform CI publishing to npm and PyPI.
The LLM identified 5 files worth highlighting for reuse:
Exact round-trip conversion between EMU, cm, in, pt, and px including paired-dimension formatting. Self-contained pure C# utility with no internal dependencies; directly extractable into any OOXML, layout, or print-pipeline project that must parse and re-emit measurements without precision loss.
Server-side request forgery guard for remote resource fetching: resolves hostnames, validates connect-time IPs against private/link-local ranges before any request proceeds, and bounds reads. Demonstrates non-obvious security engineering for document tools that accept URLs for images, OLE payloads, or remote templates; reusable wherever user-supplied URLs are fetched.
High-precision mathematical primitives for Excel-compatible distributions: Lanczos log-gamma, regularized incomplete gamma/beta, erf/erfc, and inverse normal CDF. Implemented with continued-fraction iteration and Newton refinement rather than naive approximations. Self-contained numerical core reusable in any statistics or finance engine needing accurate distribution functions.
Crash-safe persistence for OOXML packages: writes to a temp file, flushes, then atomically renames into place so a killed process can never leave a torn .docx/.xlsx/.pptx. Small, dependency-free pattern applicable to any application persisting binary documents or archives.
Managed subprocess driver for plugin executables: line-based stdout/stderr callbacks, heartbeat detection, idle-timeout watchdog with process-tree kill, and protocol version gating. Language-agnostic and reusable for any host/plugin system that must supervise external converters or workers without leaking processes.