Markdown Exporter
bowenliang123/markdown-exporter
Convert Markdown text to DOCX, PPTX, XLSX, PDF, PNG, SVG, HTML, IPYNB, MD, CSV, JSON, JSONL, XML files, and extract code blocks in Markdown to Python, Bash,JS and etc files.
Unpacks a .docx or .pptx into pretty-printed XML, lets you make small targeted edits, and repacks it into a file Office will open.
Install Office Open XML Utilities
$ npx skills add pipeshub-ai/pipeshub-ai --skill office-utils -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pipeshub-ai/pipeshub-ai office-utils --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pipeshub-ai/pipeshub-ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils .claude/skills/office-utils && rm -rf skills-srcUse ~/.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/
Install the "office-utils" agent skill from https://github.com/pipeshub-ai/pipeshub-ai/tree/main/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils into .claude/skills/office-utils/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "office-utils", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pipeshub-ai/pipeshub-ai/tree/main/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utilsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pipeshub-ai/pipeshub-ai --skill office-utils -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pipeshub-ai/pipeshub-ai office-utils --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pipeshub-ai/pipeshub-ai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils .agents/skills/office-utils && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "office-utils" agent skill from https://github.com/pipeshub-ai/pipeshub-ai/tree/main/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils into .agents/skills/office-utils/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "office-utils", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pipeshub-ai/pipeshub-ai --skill office-utils -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pipeshub-ai/pipeshub-ai office-utils --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pipeshub-ai/pipeshub-ai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils .cursor/skills/office-utils && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "office-utils" agent skill from https://github.com/pipeshub-ai/pipeshub-ai/tree/main/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils into .cursor/skills/office-utils/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "office-utils", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pipeshub-ai/pipeshub-ai.git --path backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pipeshub-ai/pipeshub-ai --skill office-utils -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pipeshub-ai/pipeshub-ai office-utils --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pipeshub-ai/pipeshub-ai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils .gemini/skills/office-utils && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "office-utils" agent skill from https://github.com/pipeshub-ai/pipeshub-ai/tree/main/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils into .gemini/skills/office-utils/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "office-utils", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pipeshub-ai/pipeshub-ai office-utilsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pipeshub-ai/pipeshub-ai --skill office-utils -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pipeshub-ai/pipeshub-ai.git skills-src && mkdir -p .github/skills && cp -r skills-src/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils .github/skills/office-utils && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "office-utils" agent skill from https://github.com/pipeshub-ai/pipeshub-ai/tree/main/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils into .github/skills/office-utils/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "office-utils", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pipeshub-ai/pipeshub-ai --skill office-utils -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pipeshub-ai/pipeshub-ai office-utils --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pipeshub-ai/pipeshub-ai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils .opencode/skills/office-utils && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "office-utils" agent skill from https://github.com/pipeshub-ai/pipeshub-ai/tree/main/backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils into .opencode/skills/office-utils/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "office-utils", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
office-utils- GitHub stars
- 3.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 507 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Unpacks a .docx or .pptx into pretty-printed XML, lets you make small targeted edits, and repacks it into a file Office will open.
- Works in 3 steps: Unpack: python… → Edit: make targeted edits to the… → Repack: python…
- Fixing a validation error in generated Word or PowerPoint markup
- SKILL.md covers Overview, Quick Reference, Workflow and Common pitfalls, plus 1 more section
- Runs Python scripts from its folder; calls python
What it does
A .docx or .pptx file is a ZIP archive of XML parts, so it can be edited directly: unpack, change the XML text, repack. No LibreOffice or other converter is needed. The skill ships two Python scripts, scripts/unpack.py and scripts/pack.py, and is meant to be called from a subprocess in your sandbox.
Unpacking pretty-prints every XML file with one element per line, so edits are readable and diffable, and it writes _unpack_manifest.json to record the original entry order and compression. pack.py reads that manifest so re-zipping does not reorder parts, which some Office readers dislike. The guidance is to make the smallest possible edit, such as one attribute or one run of text, rather than rewriting a whole XML subtree. The docx and pptx skills already use this internally for editing existing files, so you load it directly only for hand-editing the XML, such as fixing a validation error in generated markup. The excerpt is cut off after the edit step.
When your agent uses it
- Fixing a validation error in generated Word or PowerPoint markup
- Making one small targeted edit to a docx or pptx without regenerating it
- Inspecting the XML parts inside an Office file
- Repacking an edited XML tree into a file Office will open
Example prompts
- “Unpack presentation.pptx, change the title text on the first slide, and repack it.”
- “Open the document.xml inside report.docx and find why Word reports a validation error.”
- “Pack the unpacked folder back into contract.docx.”
Requirements
- Python to run scripts/unpack.py and scripts/pack.py
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Unpack: python skills/office-utils/scripts/unpack.py presentation.pptx unpacked/. This extracts every part into unpacked/, pretty-printing…
- Edit: make targeted edits to the relevant XML file(s) under unpacked/ (e.g. unpacked/word/document.xml, unpacked/ppt/slides/slide1.xml)…
- Repack: python skills/office-utils/scripts/pack.py unpacked/ output.pptx. This re-zips using the manifest's original entry order, and…
What it can do on your machine
Read from SKILL.md and the folder at commit 18d929a. 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 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Office Open XML Utilities loads about 1.1k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 507 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from pipeshub-ai/pipeshub-ai at commit 18d929a, republished under its Apache-2.0 licence (© pipeshub-ai). 507 words, ~1,145 tokens.
Download SKILL.mdSave it as
.claude/skills/office-utils/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- office-utils
- description
- Low-level support skill for hand-editing the raw XML inside a .docx or .pptx file (both formats are just ZIP archives of XML parts). Use this directly only when you need to unpack, inspect, or repack Open XML yourself — for example fixing a validation error in generated markup, or making one small targeted edit without regenerating a whole document from scratch. The docx and pptx skills already use this internally for their 'edit an existing file' workflow, so you rarely need to load this on its own.
Office Open XML utilities
Overview
A .docx or .pptx file is a ZIP archive containing a tree of XML parts (word/document.xml, ppt/slides/slide1.xml, relationship files, content-type manifests, ...). Editing it directly means: unpack the ZIP, edit the XML text, repack the ZIP. No LibreOffice or other converter is required for this — it is pure zipfile + text editing.
Note on language: the docx/pptx/xlsx/pdf skills default to Node (docx/pptxgenjs/exceljs/pdfkit) for creating a file from scratch, per this environment's Node-first policy for office-document generation. This skill stays Python: it's invoked by writing a subprocess call from your sandbox program (whichever coding tool runs it), and the Python invocation (python skills/office-utils/scripts/unpack.py ...) is guaranteed to resolve the same way across every sandbox backend, whereas the TypeScript runtime's binary (tsx) is installed per-sandbox and its exact invocation differs across backends — not worth the portability risk for a script that's about editing XML, not about which language "creates" the file.
Quick Reference
| Task | Command |
|---|---|
| Unpack a file to a directory tree | python skills/office-utils/scripts/unpack.py <file.docx|pptx> <out_dir/> |
| Repack a directory tree back to a file | python skills/office-utils/scripts/pack.py <out_dir/> <file.docx|pptx> |
Workflow
- Unpack:
python skills/office-utils/scripts/unpack.py presentation.pptx unpacked/. This extracts every part intounpacked/, pretty-printing every.xmlfile (one element per line) so edits are readable and diffable. A_unpack_manifest.jsonfile records the original entry order and compression —pack.pyreads it back so re-zipping doesn't accidentally change part ordering, which some Office readers are picky about. - Edit: make targeted edits to the relevant XML file(s) under
unpacked/(e.g.unpacked/word/document.xml,unpacked/ppt/slides/slide1.xml). Prefer the smallest possible edit — a single attribute or run of text — over rewriting a whole XML subtree, so you're less likely to break sibling elements you didn't intend to touch. - Repack:
python skills/office-utils/scripts/pack.py unpacked/ output.pptx. This re-zips using the manifest's original entry order, and validates that every.xmlpart is still well-formed (parses cleanly) before writing the final file — if any part is malformed, it fails loudly with the offending file name and line instead of silently producing a corrupt document.
Show full SKILL.md (176 more words)Show less
Common pitfalls
- Don't reorder ZIP entries. Some parsers (notably older Office/PowerPoint) are sensitive to
[Content_Types].xmland_rels/.relsbeing near the start of the archive.pack.py's manifest-driven ordering exists specifically to avoid this — don't hand-roll your own zipping. - Keep relationship IDs (
r:id) consistent. If you add a new part (e.g. an image), you must add both a<Relationship>entry in the owning part's_rels/*.relsfile AND a reference to that same ID from the XML that uses it. Adding one without the other produces a file that "opens" but shows a broken-image icon or corruption warning. - Escape XML special characters (
&,<,>) in any text you insert into a<w:t>/<a:t>run — a raw ampersand will make the part invalid XML and fail the pack-time validation. - This skill has no way to render a preview. Visual verification (rendering the file to an image) requires LibreOffice, which is not available in this environment yet — verify structurally (does it still parse? do the relationship IDs still resolve?) rather than visually.
Dependencies
Pure Python standard library (zipfile, xml.dom.minidom, json) — no packages to install.
© pipeshub-ai, Apache-2.0. 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 2 other files (scripts) in backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils of pipeshub-ai/pipeshub-ai.
- SKILL.md
- scripts/pack.py
- scripts/unpack.py
Open the folder on GitHubat commit 18d929a
Compare with similar skills
Office Open XML Utilities 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Office Open XML Utilities this skillpipeshub-ai/pipeshub-ai | 3.8k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Markdown Exporterbowenliang123/markdown-exporter | 272 | 1 repos | ~5.3k | Automated safety check: Pass | Apache-2.0 | |
| Markdown ConverterTeam-Commonly/commonly | 1.4k | — | ~557 | Automated safety check: Pass | Apache-2.0 | |
| Doclingzhuzhaoyun/Molio | 433 | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Ambiguity Reportlawve-ai/awesome-legal-skills | 847 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Document ConverterBlackBeltTechnology/pi-agent-dashboard | 315 | — | ~999 | Automated safety check: Pass | MIT |
Similar skills
Markdown Converter
Team-Commonly/commonly
Convert binary documents (PDF, DOCX, XLSX, PPTX, HTML, EPUB, images) to clean LLM-friendly Markdown using Microsoft's markitdown Python tool.
Docling
zhuzhaoyun/Molio
PRIMARY skill for converting .pdf, .docx, .pptx, .xlsx, .doc, .ppt, .xls, images, and audio/video files (.mp3, .wav, .m4a, .mp4, .mov, etc.) to Markdown.
Ambiguity Report
lawve-ai/awesome-legal-skills
Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable.
Document Converter
BlackBeltTechnology/pi-agent-dashboard
Convert documents bidirectionally via the pi-doc-engine facade: ingest PDF/DOCX/PPTX/XLSX to provenance-stamped Markdown (with OCR), and produce templated DOCX/PDF from Markdown with diagrams, TOC…
Exam Ingest
ZeKaiNie/universal-examprep-skill
从学生上传的课件/大纲/老师勾的重点/真题，一键初始化并验证备考工作区：解析 PDF、DOCX、PPTX、 XLSX、常见独立图片与 txt/md，建立分章节 LLM Wiki、标准题库、结构化接管队列与进度状态；仅在 Python 确实无法运行时 明确降级为手动写盘。当工作区尚未建立、资料发生变化、或建库 readiness 被阻断时使用。
More from pipeshub-ai/pipeshub-ai
All 9 skills in this repoPipesHub Excel Spreadsheet Builder
pipeshub-ai/pipeshub-ai
Creates and edits .xlsx workbooks with real Excel formulas rather than hardcoded computed values, defaulting to exceljs in TypeScript with a static formula-safety check.
PDF Generation, Forms and Extraction
pipeshub-ai/pipeshub-ai
Picks the right library for generating a new PDF, filling an existing PDF form, or extracting text and tables, defaulting to Node where possible.
PowerPoint Deck Builder
pipeshub-ai/pipeshub-ai
Creates new PowerPoint decks with pptxgenjs in TypeScript, reads existing decks with python-pptx, and applies a design-quality checklist so every slide has real visual hierarchy.
Verified Data Analysis with pandas
pipeshub-ai/pipeshub-ai
Loads, cleans, aggregates and joins tabular data with pandas under a verification rule: every number reported must be one that the code actually printed.
Chart Type Selection Guide
pipeshub-ai/pipeshub-ai
Picks the right chart type for a data question and applies readability rules like axis labels, colorblind palettes and legend restraint.
Word Document Creation And Editing
pipeshub-ai/pipeshub-ai
Routes a Word document request to the right approach: a TypeScript library for new files, XML editing for existing ones, and plain reading only.
Related
Works with
Categories
Questions about Office Open XML Utilities
What does Office Open XML Utilities do?
Unpacks a .docx or .pptx into pretty-printed XML, lets you make small targeted edits, and repacks it into a file Office will open. pptx file is a ZIP archive of XML parts, so it can be edited directly: unpack, change the XML text, repack. No LibreOffice or other converter is needed.
When should I use Office Open XML Utilities?
Office Open XML Utilities fits situations like: fixing a validation error in generated Word or PowerPoint markup; making one small targeted edit to a docx or pptx without regenerating it; inspecting the XML parts inside an Office file; repacking an edited XML tree into a file Office will open.
How do I install Office Open XML Utilities in Claude Code?
Run `npx skills add pipeshub-ai/pipeshub-ai --skill office-utils -a claude-code`. Or copy the skill folder (backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils in pipeshub-ai/pipeshub-ai) into .claude/skills/office-utils in your project. Claude Code loads it when a task matches its description.
How do I install Office Open XML Utilities in Codex?
Run `npx skills add pipeshub-ai/pipeshub-ai --skill office-utils -a codex`. Or copy the skill folder (backend/python/app/agents/agent_loop/skills/builtin_packs/office-utils in pipeshub-ai/pipeshub-ai) into .agents/skills/office-utils in your project. Codex loads it when a task matches its description.
Can I use Office Open XML Utilities 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 pipeshub-ai/pipeshub-ai --skill office-utils -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/office-utils, .gemini/skills/office-utils, .github/skills/office-utils and .opencode/skills/office-utils in your project.
What does Office Open XML Utilities need to run?
Going by SKILL.md and its folder, Office Open XML Utilities needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python to run scripts/unpack.py and scripts/pack.py.
Does Office Open XML Utilities access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Office Open XML Utilities 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Office Open XML Utilities use?
Office Open XML Utilities is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Office Open XML Utilities use?
About 1.1k tokens (SKILL.md is roughly 4.6k 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 Office Open XML Utilities?
Skills that share tags, products or a category with Office Open XML Utilities: Markdown Exporter (bowenliang123/markdown-exporter, 272 stars), Markdown Converter (Team-Commonly/commonly, 1.4k stars), Docling (zhuzhaoyun/Molio, 433 stars) and Ambiguity Report (lawve-ai/awesome-legal-skills, 847 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Office Open XML Utilities?
pipeshub-ai (a GitHub organization) maintains it in pipeshub-ai/pipeshub-ai, which has 3,825 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 10, 2026.
Source: pipeshub-ai/pipeshub-ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.