Word / DOCX

• You need to create or edit .docx files where styles, numbering, headers, footers, or page layout must be preserved correctly.
• Your document contains tracked changes, comments, or revision metadata and you need minimal, review-safe edits that don't orphan comment anchors or destroy formatting context.
• You're working with fields (tables of contents, page numbers, cross-references, mail merge placeholders) and need the underlying field source edited correctly, not just the cached display value.
• The document must round-trip between Word, LibreOffice, and Google Docs without table drift, broken numbering, or pagination shifts.

• Your task only involves plain text or Markdown and no .docx output is required — a simpler text-handling skill is sufficient.
• You're working with legacy .doc files and have not converted them first; this skill assumes modern OOXML .docx structure.
• You need PDF generation or PDF editing — use a dedicated PDF skill instead.

Treats .docx files as ZIP packages of structured XML parts (document.xml, styles.xml, numbering.xml, relationships, etc.) rather than plain text. This ensures edits respect the underlying document model and don't silently corrupt structure.

Prefers named paragraph and character styles over direct formatting, and extends the document's existing style system instead of layering conflicting inline overrides. Copying content between documents without importing foreign styles and numbering definitions is handled explicitly.

Manages Word's abstractNum/num numbering definitions so list restart, indentation, and continuation behavior works correctly — not just visually, but at the XML level where numbering state actually lives.

Sets margins, orientation, page size, and header/footer content at the section level. Handles first-page and odd/even header variants, and uses proper section breaks rather than manual spacing to avoid pagination drift.

Makes minimal, targeted replacements in review workflows to avoid destroying original formatting context, orphaning comment anchors, or generating noisy revision diffs. Defaults to review-style edits for legal, academic, and business documents unless a full rewrite is explicitly requested.

Checks for common sources of layout drift — table widths, embedded fonts, copied styles, compatibility mode settings — before delivery. Flags documents that may render differently in LibreOffice or Google Docs even when they look correct in Word.

A contract or report with existing tracked changes and comments needs targeted clause edits. The skill makes minimal replacements scoped to the changed span, preserving all surrounding review metadata, bookmarks, and cross-references.

You need to generate a multi-section Word report with consistent heading styles, auto-numbered lists, a table of contents, and proper page headers. The skill builds the document using named styles and correct numbering definitions so the output is editable and stable.

A .docx file looks correct in Word but tables and headers shift when opened in LibreOffice or Google Docs. The skill audits table widths, section breaks, and style definitions, then applies explicit values that survive the round-trip.

A document contains mail merge fields, a table of contents, and cross-references that may have stale cached values. The skill identifies field sources, flags outdated display values, and edits the underlying field instructions rather than the visible text.