Agent skill

OpenClaw OfficeCLI Bridge

by officecli in officecli/officecli

Generates local PPTX, DOCX, XLSX, report and image files for an OpenClaw agent through officecli agent-bridge, then sends the finished file back to the channel.

MITAuto-check passedDocuments & Office

Install OpenClaw OfficeCLI Bridge

skills CLI
$ npx skills add officecli/officecli --skill openclaw-officecli -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install officecli/officecli openclaw-officecli --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/officecli/officecli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/openclaw-officecli .claude/skills/openclaw-officecli && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
openclaw-officecli
GitHub stars
106
Token cost
~2.2k tokens
SKILL.md length
1,118 words
Files
9
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Generates local PPTX, DOCX, XLSX, report and image files for an OpenClaw agent through officecli agent-bridge, then sends the finished file back to the channel.

  • Works in 12 steps: Run fix-officecli-env.sh before starting… → Run check-officecli-env.sh after the… → Ensure officecli is installed,… → …
  • Generating a PPTX deck, Word document or Excel sheet from a prompt
  • SKILL.md covers Purpose, Trigger Rules, Runtime Contract and Agent Behavior, plus 7 more sections
  • Runs Shell scripts from its folder; calls npm and brew

What it does

This skill lets an OpenClaw agent produce local pptx, docx, xlsx, report and standalone image files when you clearly want a file, such as a five-slide deck, a customer-facing Word document, a budget spreadsheet or a launch image, and then returns the result to the current channel as an attachment. It does not trigger for plain explanations, brainstorming, outlines or analysis with no file deliverable.

Generation goes through officecli agent-bridge, a structured protocol with stdio transport, Content-Length framing, JSON-RPC 2.0 and an office.generate tool, instead of parsing human CLI output. The agent first runs fix-officecli-env.sh and check-officecli-env.sh to refresh the bundle and confirm officecli is installed and reachable, reads the bridge's capabilities, turns your request into a document type, topic, prompt and optional mode, language, style, audience or ratio, and follows task events such as progress, questions, output and completion. Images in decks can be switched off on request, and standalone images use the img type. An uninstall script is included.

When your agent uses it

  • Generating a PPTX deck, Word document or Excel sheet from a prompt
  • Producing a standalone image such as a launch graphic
  • Sending generated Office files back to a chat channel as attachments

Example prompts

  • “Make a five-slide deck about our enterprise collaboration platform.”
  • “Write a customer-facing docx explaining our onboarding steps.”
  • “Create a budget Excel sheet for a small marketing team.”
  • “Generate a launch image for the new release.”

Requirements

  • officecli installed, configured and reachable
  • An OpenClaw agent environment

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

  1. Run fix-officecli-env.sh before starting any bridge session so the skill bundle is refreshed and any missing officecli setup is repaired.
  2. Run check-officecli-env.sh after the repair step.
  3. Ensure officecli is installed, configured, and reachable.
  4. Ensure officecli agent-bridge can be started locally.
  5. Read initialize or capabilities/get before invoking generation, and cache document_generation.pptx.image_support and top-level…
  6. Also cache update; if available=true, use update_command or your own repair flow instead of parsing human CLI update prompts.
  7. Convert the user's natural-language request into
  8. If the user explicitly wants no images for pptx, set enable_images=false; otherwise follow the bridge capability default instead of…
  9. For standalone img, call office.generate with document_type=img; do not call office.render, do not set mode=best, and do not use local…
  10. Use interactive=true by default so the chat can handle follow-up questions.
  11. Use mode=fast by default unless the user explicitly asks for a higher-quality, more iterative workflow and the document type is not img.
  12. On task.question, present the question naturally in the channel and forward the answer via task/respond.

What it can do on your machine

Read from SKILL.md and the folder at commit 3442550. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • npm
    • brew

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

OpenClaw OfficeCLI Bridge loads about 2.2k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 1,118 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from officecli/officecli at commit 3442550, republished under its MIT licence (© officecli). 1,118 words, ~2,225 tokens.

Download SKILL.mdSave it as .claude/skills/openclaw-officecli/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
openclaw-officecli
description
Use when an OpenClaw user clearly wants a local Office or image artifact such as a PPTX, DOCX, XLSX, Report, or IMG, and route the request through officecli agent-bridge instead of parsing human CLI output.

OpenClaw OfficeCLI Skill

Purpose

This skill lets an OpenClaw agent generate local pptx, docx, xlsx, report, and standalone img files through officecli agent-bridge, then send the generated file back to the current channel as an attachment.

Trigger Rules

Trigger when the user clearly wants a file artifact, for example:

  • generate a five-slide PPT about an enterprise collaboration platform
  • write a customer-facing docx for me
  • create a budget excel sheet
  • generate a launch image
  • turn this into slides
  • write a docx for customers

Do not trigger for:

  • pure explanation
  • brainstorming
  • outline-only requests
  • analysis without a file deliverable

Runtime Contract

The skill must use officecli agent-bridge as the local execution protocol.

Do not treat officecli new ... stdout as a protocol.

Always prefer the structured bridge:

  • transport: stdio
  • framing: Content-Length
  • protocol: JSON-RPC 2.0
  • tool: office.generate

Required bridge methods:

  • initialize
  • capabilities/get
  • session/open
  • task/invoke
  • task/respond
  • task/status
  • task/cancel

Primary event types:

  • task.started
  • task.progress
  • task.question
  • task.output
  • task.completed
  • task.failed
  • task.cancelled

Agent Behavior

  1. Run fix-officecli-env.sh before starting any bridge session so the skill bundle is refreshed and any missing officecli setup is repaired.
  2. Run check-officecli-env.sh after the repair step.
  3. Ensure officecli is installed, configured, and reachable.
  4. Ensure officecli agent-bridge can be started locally.
  5. Read initialize or capabilities/get before invoking generation, and cache document_generation.pptx.image_support and top-level image_generation.
  6. Also cache update; if available=true, use update_command or your own repair flow instead of parsing human CLI update prompts.
  7. Convert the user's natural-language request into:
    • document_type
    • topic
    • prompt
    • optional mode
    • optional lang
    • optional style
    • optional audience
    • optional ratio for img
  8. If the user explicitly wants no images for pptx, set enable_images=false; otherwise follow the bridge capability default instead of hard-coding a client default.
  9. For standalone img, call office.generate with document_type=img; do not call office.render, do not set mode=best, and do not use local image provider config.
  10. Use interactive=true by default so the chat can handle follow-up questions.
  11. Use mode=fast by default unless the user explicitly asks for a higher-quality, more iterative workflow and the document type is not img.
  12. On task.question, present the question naturally in the channel and forward the answer via task/respond.
  13. On task.output, read result.file_path and send the file as an attachment in the current channel.
  14. On task.failed, convert the error into a user-friendly message.
  15. On user cancel, send task/cancel.

Runtime Mode Rules

  • use officecli config runtime to inspect the local default runtime mode when the host asks how OfficeCLI is configured
  • use officecli config set-runtime hosted when the host explicitly wants platform-managed hosted generation by default
  • use officecli config set-runtime external when the host wants local/external generation by default
  • hosted mode requires a platform OfficeCLI API key with hosted credits; do not ask users for aigateway keys because those are created and stored by the platform
  • OfficeCLI should be installed through one channel at a time; if the host already has a Homebrew-installed officecli, do not suggest or run npm install -g officecli on top of it

PPT Image Rules

For all OpenClaw agents using this skill:

  • inspect document_generation.pptx.image_support.default_enabled during capability discovery
  • inspect update.available during capability discovery
  • use document_generation.pptx.image_support.disable_flag when explaining how to produce a text-only deck
  • if update.available=true, prefer a structured repair/refresh path and show update_command when the host asks how to update
  • use document_generation.pptx.image_support.config_command and config_fields when the user reports missing images
  • if task.output, task.completed, or task/status includes result_meta.image_support.attention_required=true, surface that immediately in the chat
  • if result_meta.image_support.reason=image_generation_degraded, tell the user the deck was downgraded to a no-image version and they should check image_base_url, image_api_key, and image_model
  • do not rely only on free-form warning strings for client decisions; prefer result_meta
  • do not parse human update prompts from officecli stdout; use bridge capability fields
Show full SKILL.md (508 more words)Show less

Standalone Image Rules

For standalone img requests:

  • inspect top-level image_generation during capability discovery
  • use office.generate with document_type=img
  • pass ratio=square|landscape|portrait when the user asks for a shape; default to square
  • pass one reference_image local path or http/https URL when the user provides a reference image
  • require platform/license config and let the OfficeCLI server control the image provider
  • treat quota by runtime: in external mode one successful standalone image consumes one generation count, while in hosted mode it consumes hosted credits; free image usage has a separate 3-per-day bucket from free document generation
  • keep preview publishing enabled by default when publishing is configured; pass publish=false only for local-only output
  • do not use office.render, local config set-generation image settings, mode=best, source files, or local preview
  • include returned quota or credit balance metadata in the chat message when present

Environment Repair Rules

  • refresh the OpenClaw skill bundle and repair any missing officecli setup on every task by running fix-officecli-env.sh
  • do not refresh an already installed officecli binary unless the host explicitly opts in, for example with OFFICECLI_REFRESH_BINARY=1
  • when the user explicitly asks to uninstall officecli, run uninstall-officecli.sh
  • if the host previously installed with Homebrew and wants to switch to npm, tell them to run brew uninstall officecli/homebrew-officecli/officecli first; if their formula uses the short name, use brew uninstall officecli, then run npm install -g officecli
  • use check-officecli-env.sh as the single readiness probe for binary, config, and bridge
  • use fix-officecli-env.sh as the single repair entrypoint
  • when config is missing, ask only for the missing generation/license values and let the fix script write local config
  • online preview config is required by default so generated files can return publish URLs
  • if the current request is intentionally local-only, set OFFICECLI_SKIP_PUBLISH_SETUP=1 before running the fix script
  • do not try to start agent-bridge until the check script returns ready
  • if refresh or check fails, stop and report the officecli environment error; when repair fails, use the fix script's final structured status as the source of truth, and do not fall back to any other PPT/DOC/XLS generation tool without explicit user approval

Attachment Delivery

When generation succeeds:

  • read task.output.payload.result.file_path
  • upload that file to the current channel
  • include a short note with:
    • document type
    • document name
    • any warnings returned by bridge
    • when present, result_meta.image_support.message

Do not only send a local file path unless attachment upload is impossible on the current channel.

Conversation Policy

  • If document type is missing, ask which file type the user wants.
  • If topic or goal is missing, ask a concise clarifying question.
  • If the bridge emits task.question, relay it instead of inventing your own replacement question.
  • Keep progress updates short and stage-based.
  • do not trigger office.review / office.score automatically after generation unless the user explicitly asks for scoring, review, validation, or quality checking

Local Requirements

Expected local setup:

  • officecli available in PATH, or repairable by fix-officecli-env.sh
  • generation and license config already completed, or repairable by the fix script
  • standalone img requires license config; document/PPT image assets also require generation config
  • OpenClaw agent has permission to:
    • spawn local commands
    • read generated files
    • upload attachments to the active channel

© officecli, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files in skills/openclaw-officecli of officecli/officecli.

  • SKILL.md
  • README.md
  • agent-config.example.yaml
  • check-officecli-env.sh
  • config.example.yaml
  • env-common.sh
  • fix-officecli-env.sh
  • manifest.yaml
  • uninstall-officecli.sh

Open the folder on GitHubat commit 3442550

Compare with similar skills

OpenClaw OfficeCLI Bridge next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

OpenClaw OfficeCLI Bridge compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
OpenClaw OfficeCLI Bridge this skillofficecli/officecli106—~2.2kAutomated safety check: PassMIT
OfficeCLI Document EditingSylinko/Everywhere6.3k8 repos~6.3kAutomated safety check: PassCustom licence
MarkitdownImCa0/just-laws78114 repos~3.2kAutomated safety check: NotesMIT
Office File TransformCherryHQ/cherry-studio52k—~4.7kAutomated safety check: PassAGPL-3.0
MinerU Document Readeropendatalab/MinerU81k—~9.4kAutomated safety check: WarnCustom licence
GenOffice Document CLIgenspark-ai/genoffice8.8k—~19kAutomated safety check: PassApache-2.0

Similar skills

  • OfficeCLI Document Editing

    Sylinko/Everywhere

    Creates, reads, proofreads and edits Word, Excel and PowerPoint files through the officecli command line tool, with no Office installation needed.

    6.3k GitHub starsUsed in 8 repos~6.3k tokens
    Documents & OfficeAuto-check passed
  • Markitdown

    ImCa0/just-laws

    Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.

    781 GitHub starsUsed in 14 repos~3.2k tokens
    Documents & OfficeAuto-check: notes
  • Office File Transform

    CherryHQ/cherry-studio

    Derives new files from a selected part of a spreadsheet, Word document, PDF or slide deck, such as a cell range, paragraph, page or slide, without ever modifying the source file.

    52k GitHub stars~4.7k tokensUpdated today
    Documents & OfficeAuto-check passed
  • MinerU Document Reader

    opendatalab/MinerU

    Reads, OCRs, searches and cites local documents through the mineru CLI, covering PDF, images, Office files, EPUB, HTML and CSV.

    81k GitHub stars~9.4k tokensUpdated yesterday
    Documents & OfficeAuto-check: warnings
  • GenOffice Document CLI

    genspark-ai/genoffice

    Creates, converts, reads and edits real pptx, xlsx, docx and PDF files locally through the genoffice command line.

    8.8k GitHub stars~19k tokensUpdated today
    Documents & OfficeAuto-check passed
  • Docx4j

    plutext/docx4j

    A skill your agent uses when writing Java code that creates, reads or edits Word (.docx), PowerPoint (.pptx) or Excel (.xlsx) files with docx4j — including generating documents, editing existing…

    2.4k GitHub stars~2.5k tokensUpdated yesterday
    Documents & OfficeAuto-check passed

More from officecli/officecli

  • OfficeCLI

    officecli/officecli

    Routes Office document and image tasks to the OfficeCLI tool for creating, editing and converting PPTX, DOCX, XLSX, reports and generated images, after checking it supports the workflow.

    106 GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed

Questions about OpenClaw OfficeCLI Bridge

What does OpenClaw OfficeCLI Bridge do?

Generates local PPTX, DOCX, XLSX, report and image files for an OpenClaw agent through officecli agent-bridge, then sends the finished file back to the channel. This skill lets an OpenClaw agent produce local pptx, docx, xlsx, report and standalone image files when you clearly want a file, such as a five-slide deck, a customer-facing Word document, a budget spreadsheet or a launch image, and then returns the result to the current channel as an attachment. It does not trigger for plain explanations, brainstorming, outlines or analysis with no file deliverable.

When should I use OpenClaw OfficeCLI Bridge?

OpenClaw OfficeCLI Bridge fits situations like: generating a PPTX deck, Word document or Excel sheet from a prompt; producing a standalone image such as a launch graphic; sending generated Office files back to a chat channel as attachments.

How do I install OpenClaw OfficeCLI Bridge in Claude Code?

Run `npx skills add officecli/officecli --skill openclaw-officecli -a claude-code`. Or copy the skill folder (skills/openclaw-officecli in officecli/officecli) into .claude/skills/openclaw-officecli in your project. Claude Code loads it when a task matches its description.

How do I install OpenClaw OfficeCLI Bridge in Codex?

Run `npx skills add officecli/officecli --skill openclaw-officecli -a codex`. Or copy the skill folder (skills/openclaw-officecli in officecli/officecli) into .agents/skills/openclaw-officecli in your project. Codex loads it when a task matches its description.

Can I use OpenClaw OfficeCLI Bridge in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add officecli/officecli --skill openclaw-officecli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openclaw-officecli, .gemini/skills/openclaw-officecli, .github/skills/openclaw-officecli and .opencode/skills/openclaw-officecli in your project.

What does OpenClaw OfficeCLI Bridge need to run?

Going by SKILL.md and its folder, OpenClaw OfficeCLI Bridge needs a shell for the scripts in its folder and the command-line tools its instructions call (npm and brew). Our summary lists: officecli installed, configured and reachable; An OpenClaw agent environment.

Does OpenClaw OfficeCLI Bridge access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is OpenClaw OfficeCLI Bridge safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does OpenClaw OfficeCLI Bridge use?

OpenClaw OfficeCLI Bridge is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does OpenClaw OfficeCLI Bridge use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to OpenClaw OfficeCLI Bridge?

Skills that share tags, products or a category with OpenClaw OfficeCLI Bridge: OfficeCLI Document Editing (Sylinko/Everywhere, 6.3k stars), Markitdown (ImCa0/just-laws, 781 stars), Office File Transform (CherryHQ/cherry-studio, 52k stars) and MinerU Document Reader (opendatalab/MinerU, 81k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OpenClaw OfficeCLI Bridge?

officecli (a GitHub organization) maintains it in officecli/officecli, which has 106 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on August 10, 2026.

Source: officecli/officecli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.