documentslisted

Create, edit, redline, and comment on `.docx`, Word, and Google Docs-targeted document artifacts inside the container, with a strict render-and-verify workflow. Use `render_docx.py` to generate page PNGs (and optional PDF) for visual QA, then iterate until layout is flawless before delivering the final document.
andrewr303/claude-codex-plugin-lab · ★ 0 · Data & Documents · score 60

Install: claude install-skill andrewr303/claude-codex-plugin-lab

# Documents Skill (Read • Create • Edit • Redline • Comment) Use this skill when you need to create or modify `.docx`, Word, or Google Docs-targeted document artifacts **in this container environment** and verify them visually. ## Tools + Contract - Use Codex workspace dependencies for docx artifact work: resolve them through the workspace dependency loader or runtime skill, then treat the returned Node/Python runtimes and package directory as authoritative. Do not use system `node`, system `python`, global npm packages, or repo-local installs. - For document creation and deterministic OOXML edits, it is still acceptable to use the bundled Python/OOXML helper scripts in this skill package when the JS surface is incomplete. - Run any builder or helper file from a writable workspace or temp directory, not from the managed dependency directory itself. - Final user-facing responses should describe only the requested document result and link only to the final `.docx`, Word, or Google Docs deliverable unless the user explicitly asks for QA intermediates. ## Google Docs-targeted output For a net-new Google Docs request, create and visually verify a local `.docx` with this skill first. The native Google Docs deliverable must then be produced by the Google Drive plugin's document import action, `mcp__codex_apps__google_drive_import_document`, with `upload_mode: "native_google_docs"`. Before rendering or importing any Google Docs-targeted DOCX, run the deterministic title san