docx

Create, edit, and redline Word documents with tracked changes and comments.

112|26|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/Yambr/openwebui-computer-use-community --skill docx-yambr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docx
Source: https://github.com/Yambr/openwebui-computer-use-community/tree/main/skills/public/docx
Command: npx skills add https://github.com/Yambr/openwebui-computer-use-community --skill docx-yambr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires defusedxml, lxml, and includes scripts (resource) components.

What problem does it solve?

This skill automates the creation, modification, and review of Word documents (.docx), preserving formatting, applying tracked changes, and managing comments to streamline professional document workflows.

Core Features & Use Cases

  • Document creation and templating: Generate new Word docs from templates while preserving formatting and styles.
  • Editing and redlining: Apply tracked changes, comments, and redlines to existing documents.
  • Workflow automation: Integrate with packing/unpacking and validation to produce ready-to-share documents.

Quick Start

Create a new Word document from a template, apply tracked changes, and export it as a final DOCX.

Frequently Asked Questions about docx

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Word document creation while preserving formatting and styles?

Automating Word document creation involves using OOXML tooling to generate .docx files from templates while ensuring original formatting and styles are fully preserved throughout the editing process.

Can I apply tracked changes and redlining to existing .docx files programmatically?

Yes, tracked changes and redlining can be applied to existing Word documents programmatically by utilizing the Document class, which manages modifications, inserts comments, and tracks revisions for review workflows.

Does this Word document automation approach work with lxml and defusedxml?

Yes, this Word document automation approach relies on the lxml and defusedxml dependencies to safely parse, manipulate, and validate OOXML structures before packaging the final .docx file.

What is the best way to validate and package final Word documents for sharing?

The best way to validate and package final Word documents is through the included pack and unpack workflow, which verifies OOXML structures and compiles the output into a ready-to-share .docx file.

Are there limitations when modifying OOXML structures for tracked changes in Word?

Limitations when modifying OOXML structures for tracked changes depend on correct usage of the Document class and lxml; improper unpacking or validation can result in corrupted .docx packaging or lost formatting.