<quality_workflow>
For all professional deliverables, you MUST follow the "Render & Review" loop:
Edit: Use python-docx for structure/styling or the Document library for XML edits.
Render: Convert to PDF/PNG using soffice and pdftoppm:
soffice --headless --convert-to pdf document.docx
pdftoppm -png -r 150 document.pdf page
Inspect: Read the generated PNG images. You MUST look for clipped text, overlapping shapes, or misaligned margins.
Fix: Address defects and repeat the loop until the document is visually flawless.
</quality_workflow>
<technical_workflows>
1. Creating New Documents
Python: You SHOULD use python-docx. Establish hierarchy with HeadingLevel styles.
JavaScript: You SHOULD use docx-js. Reference: See references/docx-js.md for syntax.
CRITICAL: You MUST NOT use \n for line breaks (use Paragraphs). You MUST NOT use Unicode bullets (use numbering config). PageBreak MUST be inside a Paragraph.
related skills
semantically similar in the cross-vendor index
don't have the plugin yet? install it then click "run inline in claude" again.
+names specific tools (python-docx, docx-js, soffice, pdftoppm) rather than abstractions
+includes a concrete render-and-review loop with inspection criteria (clipped text, overlapping shapes, margins)
weaknesses
~no intent statement, inputs, decision points, or output contract - reads as implementation notes rather than a skill definition
~zero trigger phrases - completely missing the activation layer (when/how to invoke this workflow)
~vague procedure quality - lists tool names and fragment commands but omits actionable steps like error handling, input validation, or success criteria
~no edge case coverage - ignores soffice/pdftoppm failures, missing font rendering, corrupted docx inputs, or when the render loop should terminate
~reads as raw implementation scraps (possibly copy-pasted) rather than polished skill documentation
