Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
practicalswan avatar

Word Document

  • 673 installs
  • 7 repo stars
  • Updated August 2, 2026
  • practicalswan/agent-skills

word-document is a Claude agent skill at version 1.2 that automates creation, editing, and verification of Word .docx files using OOXML-aware workflows with MCP or native automation fallbacks for developers producing Off

About

word-document is a practicalswan/agent-skills skill at version 1.2 (last updated 2026-04-25) for automating Microsoft Word .docx files from a coding agent. The skill follows OOXML-aware workflows to create, edit, and verify documents, with an MCP Fallback to Native Automation pattern when Office MCP servers are unavailable. Version 1.2 added a Verification Protocol with skill-specific pass/fail checks, one pressure-test scenario, and a measurable success metric, plus guidance for parallel subagent dispatch on 200k+ context windows. Developers reach for word-document when users need programmatic .docx generation, structured edits, or post-edit validation instead of manual Word macros. Symptom-to-action triggers and two-stage review wording standardize how agents confirm document integrity before handoff.

  • OOXML-compatible Word (.docx) automation for agent-driven create/edit workflows
  • MCP Fallback → Native Automation path when Office MCP servers are unavailable
  • Verification Protocol with skill-specific pass/fail checks, one pressure-test scenario, and a measurable success metric
  • Guidance to use native parallel subagent dispatch and large context windows where the host supports them
  • Symptom → action activation triggers plus standardized two-stage review wording

Word Document by the numbers

  • 673 all-time installs (skills.sh)
  • +9 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #141 of 688 Office & Documents skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/practicalswan/agent-skills --skill word-document

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs673
repo stars7
Security audit3 / 3 scanners passed
Last updatedAugust 2, 2026
Repositorypracticalswan/agent-skills

How do you automate Word docx creation from a coding agent?

Automate creation, editing, and verification of Word (.docx) files from your coding agent using OOXML-aware workflows with MCP or native fallbacks.

Who is it for?

Developers automating Word report generation or structured .docx edits who need OOXML correctness checks and MCP-to-native fallback paths.

Skip if: Developers who only need plain Markdown README files, Excel spreadsheets, or PDF-only output without Word OOXML structure.

When should I use this skill?

The user asks to create, edit, or verify a Word .docx file, Office document, or OOXML-based report from an agent.

What you get

Verified .docx files with OOXML-correct structure and documented pass/fail verification results.

  • verified .docx file
  • verification pass/fail report

By the numbers

  • Skill version 1.2 last updated 2026-04-25
  • Verification Protocol includes one pressure-test scenario and measurable success metric

Files

SKILL.mdMarkdownGitHub ↗

Word Document Workflows

Tech Stack Target / Version: Word desktop or python-docx automation with current OOXML-compatible workflows.

Use this skill when .docx layout and document structure matter, not just the raw text.

  • Leverage native parallel subagent dispatch and 200k+ context windows where available.

Current MCP Reality

Microsoft publicly documents a Word MCP server in the Microsoft 365 Agents Toolkit preview, but tool availability still depends on the host. In GitHub Copilot you may see Word-specific tools; in other clients they may be missing. If direct Word MCP access is unavailable, use the included local script workflow.

Activation Conditions

Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.

  • Creating or editing .docx reports, memos, or structured deliverables
  • Applying headings, tables, images, or styles
  • Reviewing or extracting document structure
  • Preparing Word output before a later PDF conversion

Practical Workflow

1. Confirm whether the client exposes Word MCP capabilities. 2. Start with structure: title, headings, sections, tables. 3. Apply styling consistently only after the structure is right. 4. Validate comments, footnotes, and references before export. 5. Use the local generator script when MCP access is unavailable.

MCP Fallback – Native Automation

When MCP is unavailable, use native automation: python-docx for .docx, direct OOXML inspection for unsupported structures, and PDF export checks when layout matters. Preserve styles, tables, headers, footers, comments, tracked-change expectations, and metadata, then reopen or parse the document before claiming success.

Anti-Patterns

  • Writing for the author instead of the reader: It bakes in unstated context and leaves the actual audience unsure what to do next.
  • Skipping concrete examples or commands: Abstract guidance is easy to approve and hard to apply correctly.
  • Letting links, screenshots, or versions drift: Polished formatting does not help if the instructions are no longer true.

Verification Protocol

Before claiming "skill applied successfully":

1. Pass/fail: The Word Document artifact type, target format, and required output fidelity are stated before editing. 2. Pass/fail: MCP availability is checked and the native automation fallback path is named when MCP is absent. 3. Pass/fail: The produced file or formula is opened, parsed, rendered, or otherwise validated locally. 4. Pressure-test scenario: Apply the workflow to a file with formatting, metadata, or conversion edge cases and verify nothing important is lost. 5. Success metric: Zero unverified document claims; the artifact itself is the evidence.

Document Checklist

  • [ ] Heading hierarchy is clear
  • [ ] Tables are readable and consistently styled
  • [ ] Comments or review notes are intentional
  • [ ] Placeholder text is removed
  • [ ] The final document was re-opened or otherwise verified after generation

References & Resources

Documentation

  • DOCX Formatting Reference - Practical formatting notes and document structure guidance

Scripts

  • DOC Template Generator - Local fallback for generating Word-ready document structures

Examples

  • Report Generation Example - Example report workflow for .docx output

<!-- PORTABILITY:START -->

Cross-Client Portability

This skill is written to stay usable across GitHub Copilot, Claude Code, Codex, and Gemini CLI.

  • GitHub Copilot: keep the folder in a Copilot-visible skill or plugin path, or wrap the workflow as project instructions if the host does not support portable skill folders directly.
  • Claude Code: keep the folder in a local skills directory or a compatible plugin or marketplace source.
  • Codex: install or sync the folder into $CODEX_HOME/skills/<skill-name> and restart Codex after major changes.
  • Gemini CLI: this repository generates a project command named /skills:word-document from this skill. Rebuild commands with python scripts/export-gemini-skill.py word-document and then run /commands reload inside Gemini CLI.

<!-- PORTABILITY:END -->

<!-- MCP:START -->

MCP Availability And Fallback

Preferred MCP Server: Word Document MCP

  • Fallback prompt: "Use the Word Document Workflows skill without MCP. Rely on the local SKILL.md, bundled references or scripts, and manual verification. Show the exact commands, evidence, and final checks you used before concluding."
  • Use python-docx, Word desktop, or document export scripts when the MCP surface is unavailable.
  • Re-open or render the document locally so formatting, comments, and pagination are verified before delivery.

<!-- MCP:END -->

Related Skills

  • documentation-authoring: Use it when the workflow also needs drafting structured technical or product documents.
  • documentation-patterns: Use it when the workflow also needs reusable documentation structures and templates.
  • documentation-quality: Use it when the workflow also needs documentation review standards and quality gates.
  • documentation-verification: Use it when the workflow also needs final documentation validation before publishing.

Related skills

How it compares

Pick word-document for agent-driven .docx with OOXML verification; use draw-io when the deliverable is architecture diagrams rather than Word reports.

FAQ

What file format does word-document target?

word-document automates Microsoft Word .docx files using OOXML-aware workflows. Agents can create new documents, apply structured edits, and run verification checks before delivering the final file.

What changed in word-document version 1.2?

word-document version 1.2 added a Verification Protocol with pass/fail checks, one pressure-test scenario, a measurable success metric, and MCP Fallback to Native Automation guidance for Office-style workflows.

Does word-document work without an Office MCP server?

word-document includes an MCP Fallback to Native Automation section so agents can still create and verify .docx files when Office MCP tooling is unavailable, following the same OOXML workflow steps.

Is Word Document safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Office & Documentsworkflownotes

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.