← Back to Skills Marketplace
binbin

Docx Cn 1.0.1

by Beta · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
151
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install docx-cn-1-0-1
Description
Word 文档处理 | Word Document Processing. 创建、读取、编辑 Word 文档 | Create, read, edit Word documents. 支持 .docx 格式、格式化、表格、图片 | Supports .docx format, formatting, tables...
README (SKILL.md)

DOCX creation, editing, and analysis

Overview

A .docx file is a ZIP archive containing XML files.

Quick Reference

Task Approach
Read/analyze content pandoc or unpack for raw XML
Create new document Use docx-js - see Creating New Documents below
Edit existing document Unpack → edit XML → repack - see Editing Existing Documents below

Converting .doc to .docx

Legacy .doc files must be converted before editing:

python scripts/office/soffice.py --headless --convert-to docx document.doc

Reading Content

# Text extraction with tracked changes
pandoc --track-changes=all document.docx -o output.md

# Raw XML access
python scripts/office/unpack.py document.docx unpacked/

Converting to Images

python scripts/office/soffice.py --headless --convert-to pdf document.docx
pdftoppm -jpeg -r 150 document.pdf page

Accepting Tracked Changes

To produce a clean document with all tracked changes accepted (requires LibreOffice):

python scripts/accept_changes.py input.docx output.docx

Creating New Documents

Generate .docx files with JavaScript, then validate. Install: npm install -g docx

Setup

const { Document, Packer, Paragraph, TextRun, Table, TableRow, TableCell, ImageRun,
        Header, Footer, AlignmentType, PageOrientation, LevelFormat, ExternalHyperlink,
        TableOfContents, HeadingLevel, BorderStyle, WidthType, ShadingType,
        VerticalAlign, PageNumber, PageBreak } = require('docx');

const doc = new Document({ sections: [{ children: [/* content */] }] });
Packer.toBuffer(doc).then(buffer => fs.writeFileSync("doc.docx", buffer));

Validation

After creating the file, validate it. If validation fails, unpack, fix the XML, and repack.

python scripts/office/validate.py doc.docx

Page Size

// CRITICAL: docx-js defaults to A4, not US Letter
// Always set page size explicitly for consistent results
sections: [{
  properties: {
    page: {
      size: {
        width: 12240,   // 8.5 inches in DXA
        height: 15840   // 11 inches in DXA
      },
      margin: { top: 1440, right: 1440, bottom: 1440, left: 1440 } // 1 inch margins
    }
  },
  children: [/* content */]
}]

Common page sizes (DXA units, 1440 DXA = 1 inch):

Paper Width Height Content Width (1" margins)
US Letter 12,240 15,840 9,360
A4 (default) 11,906 16,838 9,026

Landscape orientation: docx-js swaps width/height internally, so pass portrait dimensions and let it handle the swap:

size: {
  width: 12240,   // Pass SHORT edge as width
  height: 15840,  // Pass LONG edge as height
  orientation: PageOrientation.LANDSCAPE  // docx-js swaps them in the XML
},
// Content width = 15840 - left margin - right margin (uses the long edge)

Styles (Override Built-in Headings)

Use Arial as the default font (universally supported). Keep titles black for readability.

const doc = new Document({
  styles: {
    default: { document: { run: { font: "Arial", size: 24 } } }, // 12pt default
    paragraphStyles: [
      // IMPORTANT: Use exact IDs to override built-in styles
      { id: "Heading1", name: "Heading 1", basedOn: "Normal", next: "Normal", quickFormat: true,
        run: { size: 32, bold: true, font: "Arial" },
        paragraph: { spacing: { before: 240, after: 240 }, outlineLevel: 0 } }, // outlineLevel required for TOC
      { id: "Heading2", name: "Heading 2", basedOn: "Normal", next: "Normal", quickFormat: true,
        run: { size: 28, bold: true, font: "Arial" },
        paragraph: { spacing: { before: 180, after: 180 }, outlineLevel: 1 } },
    ]
  },
  sections: [{
    children: [
      new Paragraph({ heading: HeadingLevel.HEADING_1, children: [new TextRun("Title")] }),
    ]
  }]
});

Lists (NEVER use unicode bullets)

// ❌ WRONG - never manually insert bullet characters
new Paragraph({ children: [new TextRun("• Item")] })  // BAD
new Paragraph({ children: [new TextRun("\u2022 Item")] })  // BAD

// ✅ CORRECT - use numbering config with LevelFormat.BULLET
const doc = new Document({
  numbering: {
    config: [
      { reference: "bullets",
        levels: [{ level: 0, format: LevelFormat.BULLET, text: "•", alignment: AlignmentType.LEFT,
          style: { paragraph: { indent: { left: 720, hanging: 360 } } } }] },
      { reference: "numbers",
        levels: [{ level: 0, format: LevelFormat.DECIMAL, text: "%1.", alignment: AlignmentType.LEFT,
          style: { paragraph: { indent: { left: 720, hanging: 360 } } } }] },
    ]
  },
  sections: [{
    children: [
      new Paragraph({ numbering: { reference: "bullets", level: 0 },
        children: [new TextRun("Bullet item")] }),
      new Paragraph({ numbering: { reference: "numbers", level: 0 },
        children: [new TextRun("Numbered item")] }),
    ]
  }]
});

// ⚠️ Each reference creates INDEPENDENT numbering
// Same reference = continues (1,2,3 then 4,5,6)
// Different reference = restarts (1,2,3 then 1,2,3)

Tables

CRITICAL: Tables need dual widths - set both columnWidths on the table AND width on each cell. Without both, tables render incorrectly on some platforms.

// CRITICAL: Always set table width for consistent rendering
// CRITICAL: Use ShadingType.CLEAR (not SOLID) to prevent black backgrounds
const border = { style: BorderStyle.SINGLE, size: 1, color: "CCCCCC" };
const borders = { top: border, bottom: border, left: border, right: border };

new Table({
  width: { size: 9360, type: WidthType.DXA }, // Always use DXA (percentages break in Google Docs)
  columnWidths: [4680, 4680], // Must sum to table width (DXA: 1440 = 1 inch)
  rows: [
    new TableRow({
      children: [
        new TableCell({
          borders,
          width: { size: 4680, type: WidthType.DXA }, // Also set on each cell
          shading: { fill: "D5E8F0", type: ShadingType.CLEAR }, // CLEAR not SOLID
          margins: { top: 80, bottom: 80, left: 120, right: 120 }, // Cell padding (internal, not added to width)
          children: [new Paragraph({ children: [new TextRun("Cell")] })]
        })
      ]
    })
  ]
})

Table width calculation:

Always use WidthType.DXAWidthType.PERCENTAGE breaks in Google Docs.

// Table width = sum of columnWidths = content width
// US Letter with 1" margins: 12240 - 2880 = 9360 DXA
width: { size: 9360, type: WidthType.DXA },
columnWidths: [7000, 2360]  // Must sum to table width

Width rules:

  • Always use WidthType.DXA — never WidthType.PERCENTAGE (incompatible with Google Docs)
  • Table width must equal the sum of columnWidths
  • Cell width must match corresponding columnWidth
  • Cell margins are internal padding - they reduce content area, not add to cell width
  • For full-width tables: use content width (page width minus left and right margins)

Images

// CRITICAL: type parameter is REQUIRED
new Paragraph({
  children: [new ImageRun({
    type: "png", // Required: png, jpg, jpeg, gif, bmp, svg
    data: fs.readFileSync("image.png"),
    transformation: { width: 200, height: 150 },
    altText: { title: "Title", description: "Desc", name: "Name" } // All three required
  })]
})

Page Breaks

// CRITICAL: PageBreak must be inside a Paragraph
new Paragraph({ children: [new PageBreak()] })

// Or use pageBreakBefore
new Paragraph({ pageBreakBefore: true, children: [new TextRun("New page")] })

Table of Contents

// CRITICAL: Headings must use HeadingLevel ONLY - no custom styles
new TableOfContents("Table of Contents", { hyperlink: true, headingStyleRange: "1-3" })

Headers/Footers

sections: [{
  properties: {
    page: { margin: { top: 1440, right: 1440, bottom: 1440, left: 1440 } } // 1440 = 1 inch
  },
  headers: {
    default: new Header({ children: [new Paragraph({ children: [new TextRun("Header")] })] })
  },
  footers: {
    default: new Footer({ children: [new Paragraph({
      children: [new TextRun("Page "), new TextRun({ children: [PageNumber.CURRENT] })]
    })] })
  },
  children: [/* content */]
}]

Critical Rules for docx-js

  • Set page size explicitly - docx-js defaults to A4; use US Letter (12240 x 15840 DXA) for US documents
  • Landscape: pass portrait dimensions - docx-js swaps width/height internally; pass short edge as width, long edge as height, and set orientation: PageOrientation.LANDSCAPE
  • Never use \ - use separate Paragraph elements
  • Never use unicode bullets - use LevelFormat.BULLET with numbering config
  • PageBreak must be in Paragraph - standalone creates invalid XML
  • ImageRun requires type - always specify png/jpg/etc
  • Always set table width with DXA - never use WidthType.PERCENTAGE (breaks in Google Docs)
  • Tables need dual widths - columnWidths array AND cell width, both must match
  • Table width = sum of columnWidths - for DXA, ensure they add up exactly
  • Always add cell margins - use margins: { top: 80, bottom: 80, left: 120, right: 120 } for readable padding
  • Use ShadingType.CLEAR - never SOLID for table shading
  • TOC requires HeadingLevel only - no custom styles on heading paragraphs
  • Override built-in styles - use exact IDs: "Heading1", "Heading2", etc.
  • Include outlineLevel - required for TOC (0 for H1, 1 for H2, etc.)

Editing Existing Documents

Follow all 3 steps in order.

Step 1: Unpack

python scripts/office/unpack.py document.docx unpacked/

Extracts XML, pretty-prints, merges adjacent runs, and converts smart quotes to XML entities (“ etc.) so they survive editing. Use --merge-runs false to skip run merging.

Step 2: Edit XML

Edit files in unpacked/word/. See XML Reference below for patterns.

Use "Claude" as the author for tracked changes and comments, unless the user explicitly requests use of a different name.

Use the Edit tool directly for string replacement. Do not write Python scripts. Scripts introduce unnecessary complexity. The Edit tool shows exactly what is being replaced.

CRITICAL: Use smart quotes for new content. When adding text with apostrophes or quotes, use XML entities to produce smart quotes:

\x3C!-- Use these entities for professional typography -->
\x3Cw:t>Here’s a quote: “Hello”\x3C/w:t>
Entity Character
‘ ‘ (left single)
’ ’ (right single / apostrophe)
“ “ (left double)
” ” (right double)

Adding comments: Use comment.py to handle boilerplate across multiple XML files (text must be pre-escaped XML):

python scripts/comment.py unpacked/ 0 "Comment text with & and ’"
python scripts/comment.py unpacked/ 1 "Reply text" --parent 0  # reply to comment 0
python scripts/comment.py unpacked/ 0 "Text" --author "Custom Author"  # custom author name

Then add markers to document.xml (see Comments in XML Reference).

Step 3: Pack

python scripts/office/pack.py unpacked/ output.docx --original document.docx

Validates with auto-repair, condenses XML, and creates DOCX. Use --validate false to skip.

Auto-repair will fix:

  • durableId >= 0x7FFFFFFF (regenerates valid ID)
  • Missing xml:space="preserve" on \x3Cw:t> with whitespace

Auto-repair won't fix:

  • Malformed XML, invalid element nesting, missing relationships, schema violations

Common Pitfalls

  • Replace entire \x3Cw:r> elements: When adding tracked changes, replace the whole \x3Cw:r>...\x3C/w:r> block with \x3Cw:del>...\x3Cw:ins>... as siblings. Don't inject tracked change tags inside a run.
  • Preserve \x3Cw:rPr> formatting: Copy the original run's \x3Cw:rPr> block into your tracked change runs to maintain bold, font size, etc.

XML Reference

Schema Compliance

  • Element order in \x3Cw:pPr>: \x3Cw:pStyle>, \x3Cw:numPr>, \x3Cw:spacing>, \x3Cw:ind>, \x3Cw:jc>, \x3Cw:rPr> last
  • Whitespace: Add xml:space="preserve" to \x3Cw:t> with leading/trailing spaces
  • RSIDs: Must be 8-digit hex (e.g., 00AB1234)

Tracked Changes

Insertion:

\x3Cw:ins w:id="1" w:author="Claude" w:date="2025-01-01T00:00:00Z">
  \x3Cw:r>\x3Cw:t>inserted text\x3C/w:t>\x3C/w:r>
\x3C/w:ins>

Deletion:

\x3Cw:del w:id="2" w:author="Claude" w:date="2025-01-01T00:00:00Z">
  \x3Cw:r>\x3Cw:delText>deleted text\x3C/w:delText>\x3C/w:r>
\x3C/w:del>

Inside \x3Cw:del>: Use \x3Cw:delText> instead of \x3Cw:t>, and \x3Cw:delInstrText> instead of \x3Cw:instrText>.

Minimal edits - only mark what changes:

\x3C!-- Change "30 days" to "60 days" -->
\x3Cw:r>\x3Cw:t>The term is \x3C/w:t>\x3C/w:r>
\x3Cw:del w:id="1" w:author="Claude" w:date="...">
  \x3Cw:r>\x3Cw:delText>30\x3C/w:delText>\x3C/w:r>
\x3C/w:del>
\x3Cw:ins w:id="2" w:author="Claude" w:date="...">
  \x3Cw:r>\x3Cw:t>60\x3C/w:t>\x3C/w:r>
\x3C/w:ins>
\x3Cw:r>\x3Cw:t> days.\x3C/w:t>\x3C/w:r>

Deleting entire paragraphs/list items - when removing ALL content from a paragraph, also mark the paragraph mark as deleted so it merges with the next paragraph. Add \x3Cw:del/> inside \x3Cw:pPr>\x3Cw:rPr>:

\x3Cw:p>
  \x3Cw:pPr>
    \x3Cw:numPr>...\x3C/w:numPr>  \x3C!-- list numbering if present -->
    \x3Cw:rPr>
      \x3Cw:del w:id="1" w:author="Claude" w:date="2025-01-01T00:00:00Z"/>
    \x3C/w:rPr>
  \x3C/w:pPr>
  \x3Cw:del w:id="2" w:author="Claude" w:date="2025-01-01T00:00:00Z">
    \x3Cw:r>\x3Cw:delText>Entire paragraph content being deleted...\x3C/w:delText>\x3C/w:r>
  \x3C/w:del>
\x3C/w:p>

Without the \x3Cw:del/> in \x3Cw:pPr>\x3Cw:rPr>, accepting changes leaves an empty paragraph/list item.

Rejecting another author's insertion - nest deletion inside their insertion:

\x3Cw:ins w:author="Jane" w:id="5">
  \x3Cw:del w:author="Claude" w:id="10">
    \x3Cw:r>\x3Cw:delText>their inserted text\x3C/w:delText>\x3C/w:r>
  \x3C/w:del>
\x3C/w:ins>

Restoring another author's deletion - add insertion after (don't modify their deletion):

\x3Cw:del w:author="Jane" w:id="5">
  \x3Cw:r>\x3Cw:delText>deleted text\x3C/w:delText>\x3C/w:r>
\x3C/w:del>
\x3Cw:ins w:author="Claude" w:id="10">
  \x3Cw:r>\x3Cw:t>deleted text\x3C/w:t>\x3C/w:r>
\x3C/w:ins>

Comments

After running comment.py (see Step 2), add markers to document.xml. For replies, use --parent flag and nest markers inside the parent's.

CRITICAL: \x3Cw:commentRangeStart> and \x3Cw:commentRangeEnd> are siblings of \x3Cw:r>, never inside \x3Cw:r>.

\x3C!-- Comment markers are direct children of w:p, never inside w:r -->
\x3Cw:commentRangeStart w:id="0"/>
\x3Cw:del w:id="1" w:author="Claude" w:date="2025-01-01T00:00:00Z">
  \x3Cw:r>\x3Cw:delText>deleted\x3C/w:delText>\x3C/w:r>
\x3C/w:del>
\x3Cw:r>\x3Cw:t> more text\x3C/w:t>\x3C/w:r>
\x3Cw:commentRangeEnd w:id="0"/>
\x3Cw:r>\x3Cw:rPr>\x3Cw:rStyle w:val="CommentReference"/>\x3C/w:rPr>\x3Cw:commentReference w:id="0"/>\x3C/w:r>

\x3C!-- Comment 0 with reply 1 nested inside -->
\x3Cw:commentRangeStart w:id="0"/>
  \x3Cw:commentRangeStart w:id="1"/>
  \x3Cw:r>\x3Cw:t>text\x3C/w:t>\x3C/w:r>
  \x3Cw:commentRangeEnd w:id="1"/>
\x3Cw:commentRangeEnd w:id="0"/>
\x3Cw:r>\x3Cw:rPr>\x3Cw:rStyle w:val="CommentReference"/>\x3C/w:rPr>\x3Cw:commentReference w:id="0"/>\x3C/w:r>
\x3Cw:r>\x3Cw:rPr>\x3Cw:rStyle w:val="CommentReference"/>\x3C/w:rPr>\x3Cw:commentReference w:id="1"/>\x3C/w:r>

Images

  1. Add image file to word/media/
  2. Add relationship to word/_rels/document.xml.rels:
\x3CRelationship Id="rId5" Type=".../image" Target="media/image1.png"/>
  1. Add content type to [Content_Types].xml:
\x3CDefault Extension="png" ContentType="image/png"/>
  1. Reference in document.xml:
\x3Cw:drawing>
  \x3Cwp:inline>
    \x3Cwp:extent cx="914400" cy="914400"/>  \x3C!-- EMUs: 914400 = 1 inch -->
    \x3Ca:graphic>
      \x3Ca:graphicData uri=".../picture">
        \x3Cpic:pic>
          \x3Cpic:blipFill>\x3Ca:blip r:embed="rId5"/>\x3C/pic:blipFill>
        \x3C/pic:pic>
      \x3C/a:graphicData>
    \x3C/a:graphic>
  \x3C/wp:inline>
\x3C/w:drawing>

Dependencies

  • pandoc: Text extraction
  • docx: npm install -g docx (new documents)
  • LibreOffice: PDF conversion (auto-configured for sandboxed environments via scripts/office/soffice.py)
  • Poppler: pdftoppm for images
Usage Guidance
This skill appears to actually implement .docx/.pptx/.xlsx unpacking, editing, validation, and packing — that part is coherent. Before installing or running it, consider: - Required tools: The skill expects LibreOffice (soffice), pandoc, pdftoppm, the docx npm package (docx-js), and gcc — but the skill metadata declares no required binaries. Ensure you only run it on machines where you trust those tools and understand they will be invoked. - Runtime compilation & LD_PRELOAD: The soffice helper writes a small C source file to the temp directory, compiles a shared object with gcc, and uses LD_PRELOAD for a socket shim. Compiling and preloading native code at runtime raises risk (can execute native operations and affect process behavior). If you don't want that, avoid using the functions that trigger the shim or run in an environment where AF_UNIX works so the shim isn't needed. - LibreOffice macro: The skill writes a StarBasic macro into a LibreOffice profile under /tmp to accept tracked changes and then calls soffice to run it. Macros can execute actions within LibreOffice; inspect the macro (it's visible in the repository) and run in an isolated environment if you have sensitive files. - Run in a sandbox: Test the skill on non-sensitive documents in an isolated environment (VM or container) first. Check that the temp files (/tmp/libreoffice_docx_profile and the compiled lo_socket_shim.so) are acceptable for your security posture and are removed if desired. - Verify provenance: The LICENSE states Anthropic but the source/homepage are unknown and owner metadata doesn't match that license header; consider whether you trust this package origin before use. If you need to proceed: review the soffice shim source and the macro content, confirm which external binaries will be invoked, and prefer running these scripts in a disposable environment (or adapt them to avoid runtime compilation and macro writes).
Capability Analysis
Type: OpenClaw Skill Name: docx-cn-1-0-1 Version: 1.0.0 The skill bundle contains a high-risk mechanism in `scripts/office/soffice.py` that performs runtime compilation of a C shim and utilizes `LD_PRELOAD` to hook system calls (socket, accept, close). While documented as a compatibility workaround for sandboxed environments where Unix sockets are restricted, the use of runtime compilation and library injection is a significant security risk and a technique commonly associated with evasion. Additionally, `scripts/accept_changes.py` executes LibreOffice macros from `/tmp`, and `scripts/office/validators/base.py` uses `lxml` for XML parsing without explicit protections against XML External Entity (XXE) attacks.
Capability Assessment
Purpose & Capability
The name, description, SKILL.md, and included Python scripts all focus on creating, reading, editing, and validating .docx/.pptx/.xlsx files — this aligns with the stated purpose. However, the skill fails to declare several required external tools and binaries (soffice/LibreOffice, pandoc, npm docx package, pdftoppm, and gcc for the shim) even though both SKILL.md and the code expect them. That mismatch is unexpected and should be remedied or called out to users.
Instruction Scope
Runtime instructions (SKILL.md) and the included scripts operate on user-supplied Office files and unpacked directories (expected). But the code also: (1) writes a LibreOffice macro into a user profile directory and invokes soffice to execute it; (2) may compile and LD_PRELOAD a C shim at runtime to work around AF_UNIX socket restrictions. Both actions go beyond simple file-editing guidance and introduce behavior that affects the runtime environment and executes compiled native code.
Install Mechanism
There is no install spec (no external downloads), which keeps install risk low. However, the included office/soffice module generates C source into the temp directory and invokes gcc to build a shared object at runtime, then uses LD_PRELOAD. Runtime compilation/execution of native code is higher risk than pure Python/JS and should be considered carefully.
Credentials
The skill does not request any environment variables, credentials, or external config paths in its metadata. The file operations and temp-file usage in the scripts are proportionate to document processing. Still, the skill writes to /tmp (e.g., macro profile, compiled shim) and sets LD_PRELOAD for subprocesses it launches; those are environment-affecting actions that are not reflected in the declared requirements.
Persistence & Privilege
always:false and no cross-skill configuration changes. The skill does create files under /tmp (a LibreOffice profile path and a compiled .so shim) and writes a LibreOffice macro into that profile; these artifacts can persist across runs until cleaned and could affect subsequent LibreOffice invocations if reused. This is not permanent system-wide installation but is more than ephemeral in-memory activity.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install docx-cn-1-0-1
  3. After installation, invoke the skill by name or use /docx-cn-1-0-1
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of docx-cn with comprehensive documentation for Word (.docx) document processing. - Supports creating, reading, and editing .docx files, including formatting, tables, and images. - Provides step-by-step guides and code samples for document generation using docx-js (JavaScript). - Covers best practices for styling, lists, tables, images, page setup, and tracked changes. - Includes command-line utilities and common troubleshooting strategies for DOCX file compatibility.
Metadata
Slug docx-cn-1-0-1
Version 1.0.0
License MIT-0
All-time Installs 2
Active Installs 2
Total Versions 1
Frequently Asked Questions

What is Docx Cn 1.0.1?

Word 文档处理 | Word Document Processing. 创建、读取、编辑 Word 文档 | Create, read, edit Word documents. 支持 .docx 格式、格式化、表格、图片 | Supports .docx format, formatting, tables... It is an AI Agent Skill for Claude Code / OpenClaw, with 151 downloads so far.

How do I install Docx Cn 1.0.1?

Run "/install docx-cn-1-0-1" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Docx Cn 1.0.1 free?

Yes, Docx Cn 1.0.1 is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Docx Cn 1.0.1 support?

Docx Cn 1.0.1 is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Docx Cn 1.0.1?

It is built and maintained by Beta (@binbin); the current version is v1.0.0.

💬 Comments