officecli

officecli

Use the local binary at ~/.local/bin/officecli.

First Check

Before using the tool:

command -v officecli
officecli --version

If officecli is missing from PATH, use the absolute path:

$HOME/.local/bin/officecli --version

Strategy

Prefer this progression:

1. L1 read: view, get, query, validate
2. L2 DOM edit: set, add, remove, move, swap, batch
3. L3 raw XML: raw, raw-set, add-part

Always add --json when structured output helps.

Help System

When unsure about element names, paths, or properties, run help instead of guessing:

officecli pptx set
officecli pptx set shape
officecli pptx set shape.fill
officecli docx add
officecli xlsx get

Core Commands

officecli create <file>
officecli view <file> <mode>
officecli get <file> <path> --depth N
officecli query <file> <selector>
officecli set <file> <path> --prop key=value
officecli add <file> <parent> --type <type> --prop key=value
officecli remove <file> <path>
officecli move <file> <path> --to <parent> --index N
officecli swap <file> <path1> <path2>
officecli validate <file>
officecli batch <file>
officecli raw <file> <part>
officecli raw-set <file> <part> --xpath "..." --action replace --xml '<xml/>'

Performance

For 3 or more operations on one file, prefer resident mode:

officecli open file.docx
officecli set file.docx ...
officecli add file.docx ...
officecli close file.docx

For many edits, prefer batch mode:

cat <<'EOF' | officecli batch file.xlsx
[
  {"command":"set","path":"/Sheet1/A1","props":{"value":"Name","bold":"true"}}
]
EOF

Validation

Before considering the document done:

officecli view file.docx issues
officecli validate file.docx

For large files, use targeted reads:

officecli view file.docx text --max-lines 100
officecli view file.xlsx text --start 1 --end 40 --cols A,B,C
officecli view file.pptx text --start 1 --end 5

Specialized Skills