OfficeCLI Skill Installation for AI Agents: Complete Setup Guide

AI agents can install and use OfficeCLI in one command by loading the published skill file from https://officecli.ai/SKILL.md, which auto-detects the binary, runs the platform-specific install script, and registers the tool with the agent's MCP discovery protocol.

OfficeCLI is a single-binary, AI-native CLI that grants agents full read/write control over Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) documents without requiring Microsoft Office or runtime dependencies. This guide covers the complete OfficeCLI skill installation for AI agents, from the one-line setup to practical command examples drawn directly from the source repository.

How the OfficeCLI Skill Works for AI Agents

The skill installation follows a four-stage protocol defined in SKILL.md at the root of the iOfficeAI/OfficeCLI repository.

Stages of skill activation:

1. Detection — checks whether officecli exists on the system PATH
2. Installation — executes the one-liner curl or PowerShell script to fetch the native binary
3. Registration — exposes all commands through the Model Context Protocol (MCP) for tool discovery
4. Enablement — allows JSON-friendly output via the --json flag on every command

The skill file is published at https://officecli.ai/SKILL.md and consumed directly by compatible agent frameworks.

One-Line Installation Commands

When an AI agent processes the skill, it executes the appropriate install script based on the detected platform. These commands are embedded in SKILL.md under the install section.

macOS and Linux

curl -fsSL https://d.officecli.ai/install.sh | bash

Windows (PowerShell)

irm https://d.officecli.ai/install.ps1 | iex

After execution, the agent verifies installation by running officecli --version. If the PATH has not refreshed, the skill recommends opening a new terminal session.

OfficeCLI Architecture for Agent Operations

The skill exposes a three-layer command hierarchy that agents use to manipulate documents with increasing precision. This architecture is documented in README.md under "Three-Layer Architecture."

Layer	Purpose	Key Commands	Skill Reference
L1 — Read	Semantic document views and exports	view, get, query	Generates outlines, stats, HTML, and PNG previews
L2 — DOM	Structured element manipulation	add, set, remove, move, swap, batch	Documented in SKILL.md section "## L2: DOM Operations"

| L3 — Raw XML | Direct OOXML fallback | raw, raw-set, add-part | Used when L2 cannot express a required change | | Resident Mode | In-memory document for low latency | open, close, save | Auto-flushes on idle; eliminates I/O per command | | MCP Server | JSON-RPC exposure for agents | mcp | Enables agent calls without shell execution |

Key Architectural Strengths

• Zero-dependency binary — the .NET runtime is statically linked, so agents never install separate frameworks
• Built-in rendering engine — generates HTML and PNG from OOXML without external tools
• Native formula evaluation — over 350 Excel functions compute on write, no Excel required
• Template merge syntax — {{key}} substitution for repeated document generation
• Round-trip serialization — dump exports to replayable JSON; batch re-applies for agent learning

Practical Code Examples for AI Agents

Once the OfficeCLI skill installation for AI agents completes, the agent can emit commands targeting any layer of the architecture.

Create and Style a PowerPoint Presentation

officecli create deck.pptx
officecli add deck.pptx / --type slide \
    --prop title="Q4 Report" \
    --prop background=1A1A2E
officecli add deck.pptx '/slide[1]' --type shape \
    --prop text="Revenue grew 25%" \
    --prop x=2cm --prop y=5cm \
    --prop font=Arial --prop size=24 --prop color=FFFFFF

This demonstrates L2 DOM operations: create initializes the file, add appends a slide, and a second add inserts a positioned text shape with styling properties.

Build an Excel Tracker with Formulas and Named Ranges

officecli create tracker.xlsx
officecli set tracker.xlsx /Sheet1/A1 --prop value="Name"
officecli set tracker.xlsx /Sheet1/B1 --prop value="Score"
officecli set tracker.xlsx /Sheet1/B2 --prop value="Alice"
officecli set tracker.xlsx /Sheet1/B3 --prop value="Bob"
officecli set tracker.xlsx /Sheet1/B4 --prop formula="AVERAGE(B2:B3)"
officecli add tracker.xlsx / --type namedrange \
    --prop name="ScoreRange" \
    --prop ref="Sheet1!$B$2:$B$3"

The agent sets values, injects a native formula, and creates a named range for programmatic reference in subsequent operations.

Live Preview for Iterative Document Development

officecli create report.docx
officecli add report.docx /body --type paragraph \
    --prop text="Executive Summary" --prop style=Heading1
officecli watch report.docx

The watch command launches http://localhost:26315 with auto-refresh, enabling the agent to render, inspect, and fix layout issues in a visual feedback loop.

Batch-Apply Cell Updates for Performance

cat <<'EOF' | officecli batch data.xlsx --json
[
  {"command":"set","path":"/Sheet1/A2","props":{"value":"Jan"}},
  {"command":"set","path":"/Sheet1/B2","props":{"value":42000,"numFmt":"$#,##0"}},
  {"command":"set","path":"/Sheet1/A3","props":{"value":"Feb"}},
  {"command":"set","path":"/Sheet1/B3","props":{"value":45000,"numFmt":"$#,##0"}}
]
EOF

The heredoc prevents shell expansion of ! and $. The batch executes atomically, making it ideal for high-throughput agent workflows.

Generate HTML for Visual Verification

officecli view report.docx html -o /tmp/report.html

The agent can then open /tmp/report.html in a headless browser to validate layout before finalizing the document.

Key Source Files for Agent Integration

Understanding these files helps agents and developers verify the skill contract and extend functionality.

File	Purpose	Location in Repository
SKILL.md	The canonical skill definition consumed by agents	https://github.com/iOfficeAI/OfficeCLI/blob/main/SKILL.md
README.md	Comprehensive command reference and architecture guide	https://github.com/iOfficeAI/OfficeCLI/blob/main/README.md
src/officecli/officecli.csproj	.NET project file for the self-contained binary	src/officecli/officecli.csproj
npm/lib/install-binary.js	Platform detection and binary download logic for npm installs	npm/lib/install-binary.js
skills/officecli-xlsx/SKILL.md	Specialized skill for Excel-centric financial and dashboard tasks	skills/officecli-xlsx/SKILL.md
plugins/plugin-protocol.md	MCP JSON-RPC specification for tool exposure	plugins/plugin-protocol.md
install.sh / install.ps1	Cross-platform install scripts referenced by the skill	root of repository
examples/	Runnable Bash and Python demonstrations	examples/ directory

The skill file at SKILL.md is the primary contract. It defines available commands, their parameters, and the installation protocol that agents execute automatically.

MCP Server Mode for Direct Agent Integration

For agents that support the Model Context Protocol, OfficeCLI can expose all commands via JSON-RPC instead of shell execution:

officecli mcp

This starts an MCP server that agents query for available tools and invoke with structured parameters. The protocol specification lives in plugins/plugin-protocol.md according to the repository structure.

MCP mode eliminates shell parsing overhead and provides schema-validated command discovery, making it the preferred integration path for sophisticated agent frameworks.

Summary

• OfficeCLI skill installation for AI agents completes in one command by loading https://officecli.ai/SKILL.md
• The skill auto-installs the zero-dependency binary via curl or PowerShell scripts
• Three-layer architecture (L1 Read / L2 DOM / L3 Raw XML) provides graduated control over documents
• JSON output (--json) and MCP server mode enable programmatic agent integration
• Resident mode (open/close/save) and batch operations optimize for agent throughput
• Built-in rendering and formula engines eliminate external dependencies

Frequently Asked Questions

What platforms support the OfficeCLI skill installation?

The skill supports macOS, Linux, and Windows through platform-specific install scripts in install.sh and install.ps1. The binary is self-contained with the .NET runtime embedded, so no separate framework installation is required on any supported platform.

How does an AI agent discover available OfficeCLI commands?

After installation, the skill registers with the agent's MCP-compatible tool discovery protocol. Agents can also run officecli --help or officecli <command> --help for human-readable documentation, or query the MCP server for JSON-schema descriptions of each command.

Can agents use OfficeCLI without installing the binary locally?

No—the skill currently requires the native binary on the agent's execution host. However, the one-line install scripts handle detection, download, and PATH configuration automatically. Future versions may support containerized or remote execution modes based on repository development.

What file formats can agents manipulate after skill installation?

OfficeCLI supports full read/write operations on Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) files. The built-in engines handle OOXML parsing, formula evaluation, and rendering without requiring Microsoft Office or other external software.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}