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.
1---2name: doc3description: Cross-platform DOCX reading, creation, and editing with python-docx and rendered visual checks. Use when native Microsoft Word automation is unavailable or unnecessary. On Windows, prefer docx-win for layout-sensitive edits, tracked changes, fields, or Word-to-PDF verification.4---567# DOCX Skill89## When to use10- Read or review DOCX content where layout matters (tables, diagrams, pagination).11- Create or edit DOCX files with professional formatting.12- Validate visual layout before delivery.1314## Workflow151. Prefer visual review (layout, tables, diagrams).16 - If `soffice` and `pdftoppm` are available, convert DOCX -> PDF -> PNGs.17 - Or use `scripts/render_docx.py` (requires `pdf2image` and Poppler).18 - If these tools are missing, install them or ask the user to review rendered pages locally.192. Use `python-docx` for edits and structured creation (headings, styles, tables, lists).203. After each meaningful change, re-render and inspect the pages.214. If visual review is not possible, extract text with `python-docx` as a fallback and call out layout risk.225. Keep intermediate outputs organized and clean up after final approval.2324## Temp and output conventions25- Use `tmp/docs/` for intermediate files; delete when done.26- Write final artifacts under `output/doc/` when working in this repo.27- Keep filenames stable and descriptive.2829## Dependencies (install if missing)30Prefer `uv` for dependency management.3132Python packages:33```34uv pip install python-docx pdf2image35```36If `uv` is unavailable:37```38python3 -m pip install python-docx pdf2image39```40System tools (for rendering):41```42# macOS (Homebrew)43brew install libreoffice poppler4445# Ubuntu/Debian46sudo apt-get install -y libreoffice poppler-utils47```4849If installation isn't possible in this environment, tell the user which dependency is missing and how to install it locally.5051## Environment52No required environment variables.5354## Rendering commands55DOCX -> PDF:56```57soffice -env:UserInstallation=file:///tmp/lo_profile_$$ --headless --convert-to pdf --outdir $OUTDIR $INPUT_DOCX58```5960PDF -> PNGs:61```62pdftoppm -png $OUTDIR/$BASENAME.pdf $OUTDIR/$BASENAME63```6465Bundled helper:66```67python3 scripts/render_docx.py /path/to/file.docx --output_dir /tmp/docx_pages68```6970## Quality expectations71- Deliver a client-ready document: consistent typography, spacing, margins, and clear hierarchy.72- Avoid formatting defects: clipped/overlapping text, broken tables, unreadable characters, or default-template styling.73- Charts, tables, and visuals must be legible in rendered pages with correct alignment.74- Use ASCII hyphens only. Avoid U+2011 (non-breaking hyphen) and other Unicode dashes.75- Citations and references must be human-readable; never leave tool tokens or placeholder strings.7677## Final checks78- Re-render and inspect every page at 100% zoom before final delivery.79- Fix any spacing, alignment, or pagination issues and repeat the render loop.80- Confirm there are no leftovers (temp files, duplicate renders) unless the user asks to keep them.
steven65026502