DOCX Skill
When to use
- Read or review DOCX content where layout matters (tables, diagrams, pagination).
- Create or edit DOCX files with professional formatting.
- Validate visual layout before delivery.
Workflow
- Prefer visual review (layout, tables, diagrams).
- If
soffice and pdftoppm are available, convert DOCX -> PDF -> PNGs.
- Or use
scripts/render_docx.py (requires pdf2image and Poppler).
- If these tools are missing, install them or ask the user to review rendered pages locally.
- Use
python-docx for edits and structured creation (headings, styles, tables, lists).
- After each meaningful change, re-render and inspect the pages.
- If visual review is not possible, extract text with
python-docx as a fallback and call out layout risk.
- Keep intermediate outputs organized and clean up after final approval.
Temp and output conventions
- Use
tmp/docs/ for intermediate files; delete when done.
- Write final artifacts under
output/doc/ when working in this repo.
- Keep filenames stable and descriptive.
Dependencies (install if missing)
Prefer uv for dependency management.
Python packages:
uv pip install python-docx pdf2image
If uv is unavailable:
python3 -m pip install python-docx pdf2image
System tools (for rendering):
# macOS (Homebrew)
brew install libreoffice poppler
# Ubuntu/Debian
sudo apt-get install -y libreoffice poppler-utils
If installation isn't possible in this environment, tell the user which dependency is missing and how to install it locally.
Environment
No required environment variables.
Rendering commands
DOCX -> PDF:
soffice -env:UserInstallation=file:///tmp/lo_profile_$$ --headless --convert-to pdf --outdir $OUTDIR $INPUT_DOCX
PDF -> PNGs:
pdftoppm -png $OUTDIR/$BASENAME.pdf $OUTDIR/$BASENAME
Bundled helper:
python3 scripts/render_docx.py /path/to/file.docx --output_dir /tmp/docx_pages
Quality expectations
- Deliver a client-ready document: consistent typography, spacing, margins, and clear hierarchy.
- Avoid formatting defects: clipped/overlapping text, broken tables, unreadable characters, or default-template styling.
- Charts, tables, and visuals must be legible in rendered pages with correct alignment.
- Use ASCII hyphens only. Avoid U+2011 (non-breaking hyphen) and other Unicode dashes.
- Citations and references must be human-readable; never leave tool tokens or placeholder strings.
Final checks
- Re-render and inspect every page at 100% zoom before final delivery.
- Fix any spacing, alignment, or pagination issues and repeat the render loop.
- Confirm there are no leftovers (temp files, duplicate renders) unless the user asks to keep them.
When NOT to Use
1---2name: openai-doc3description: Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks. Originally from OpenAI's curated skills catalog.4---56# DOCX Skill78## When to use9- Read or review DOCX content where layout matters (tables, diagrams, pagination).10- Create or edit DOCX files with professional formatting.11- Validate visual layout before delivery.1213## Workflow141. Prefer visual review (layout, tables, diagrams).15 - If `soffice` and `pdftoppm` are available, convert DOCX -> PDF -> PNGs.16 - Or use `scripts/render_docx.py` (requires `pdf2image` and Poppler).17 - If these tools are missing, install them or ask the user to review rendered pages locally.182. Use `python-docx` for edits and structured creation (headings, styles, tables, lists).193. After each meaningful change, re-render and inspect the pages.204. If visual review is not possible, extract text with `python-docx` as a fallback and call out layout risk.215. Keep intermediate outputs organized and clean up after final approval.2223## Temp and output conventions24- Use `tmp/docs/` for intermediate files; delete when done.25- Write final artifacts under `output/doc/` when working in this repo.26- Keep filenames stable and descriptive.2728## Dependencies (install if missing)29Prefer `uv` for dependency management.3031Python packages:32```33uv pip install python-docx pdf2image34```35If `uv` is unavailable:36```37python3 -m pip install python-docx pdf2image38```39System tools (for rendering):40```41# macOS (Homebrew)42brew install libreoffice poppler4344# Ubuntu/Debian45sudo apt-get install -y libreoffice poppler-utils46```4748If installation isn't possible in this environment, tell the user which dependency is missing and how to install it locally.4950## Environment51No required environment variables.5253## Rendering commands54DOCX -> PDF:55```56soffice -env:UserInstallation=file:///tmp/lo_profile_$$ --headless --convert-to pdf --outdir $OUTDIR $INPUT_DOCX57```5859PDF -> PNGs:60```61pdftoppm -png $OUTDIR/$BASENAME.pdf $OUTDIR/$BASENAME62```6364Bundled helper:65```66python3 scripts/render_docx.py /path/to/file.docx --output_dir /tmp/docx_pages67```6869## Quality expectations70- Deliver a client-ready document: consistent typography, spacing, margins, and clear hierarchy.71- Avoid formatting defects: clipped/overlapping text, broken tables, unreadable characters, or default-template styling.72- Charts, tables, and visuals must be legible in rendered pages with correct alignment.73- Use ASCII hyphens only. Avoid U+2011 (non-breaking hyphen) and other Unicode dashes.74- Citations and references must be human-readable; never leave tool tokens or placeholder strings.7576## Final checks77- Re-render and inspect every page at 100% zoom before final delivery.78- Fix any spacing, alignment, or pagination issues and repeat the render loop.79- Confirm there are no leftovers (temp files, duplicate renders) unless the user asks to keep them.80## When NOT to Use8182<!-- TODO: review -->83
tools-only