Word Document
Automate creation, editing, and verification of Word (.docx) files from your coding agent using OOXML-aware workflows with MCP or native fallbacks.
Overview
word-document is an agent skill most often used in Build (also Validate, Launch) that automates Word (.docx) work through OOXML-compatible flows with MCP or native Office automation and a built-in verification protocol.
Install
npx skills add https://github.com/practicalswan/agent-skills --skill word-documentWhat is this skill?
- 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
- Catalog version 1.2 with Verification Protocol pass/fail checks, one pressure-test scenario, and a measurable success me
- Documents MCP Fallback → Native Automation for Office-style workflows
- OOXML-compatible Word automation guidance tied to current .docx workflows
Adoption & trust: 1 installs on skills.sh; 3 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You need a proper Word file from your agent but ad-hoc edits break styles, OOXML, or stakeholder formatting expectations.
Who is it for?
Solo builders who must deliver or iterate on .docx files (SOWs, specs, reports, one-pagers) from an agent session and want repeatable verification before handoff.
Skip if: Teams that standardize on Markdown-only repos, Google Docs, or PDF-only pipelines where Word is never a required interchange format.
When should I use this skill?
Invoke when the user needs to create, edit, or validate a Word (.docx) file and symptoms include broken formatting, unclear OOXML steps, missing MCP Office access, or no verification before handoff.
What do I get? / Deliverables
You get a verified .docx that passes the skill’s pass/fail checks and opens correctly in Word, with a documented MCP or native automation path for the next edit round.
- Updated or new .docx file that passes the skill Verification Protocol
- Documented automation path used (MCP vs native) for reproducibility
- Verification notes against pass/fail checks and the pressure-test scenario
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Word output is most often produced while building deliverables—specs, handoffs, and client-facing documentation—so the canonical shelf is Build → Docs even though the same skill supports proposals and content elsewhere. Docs subphase covers structured written artifacts in standard formats; .docx generation and OOXML edits are a core documentation deliverable for solo builders shipping with agents.
Where it fits
Turn an approved feature outline into a client-ready scope document in .docx with consistent headings and styles before you commit to the build.
Generate or update internal handoff docs, API summaries, or release notes exported as Word for partners who refuse Markdown.
Produce a polished one-pager or press-style Word asset for email attachments or print-ready distribution.
Refresh a downloadable guide or checklist in .docx for leads without rebuilding the layout by hand in Word.
How it compares
Use this procedural skill for agent-run .docx workflows—not a generic chat paste into Word or a separate desktop macro recorder with no verification steps.
Common Questions / FAQ
Who is word-document for?
It is for solo and indie builders using Claude Code, Cursor, Codex, or similar agents who need reliable Word (.docx) creation and edits as part of shipping docs, scopes, or stakeholder deliverables.
When should I use word-document?
Use it during Build when writing handoff or product docs, during Validate when packaging a scoped proposal or spec in Word, and during Launch or Grow when refreshing downloadable content—any time the required artifact is .docx and you want MCP or native automation plus verificati
Is word-document safe to install?
Treat it like any third-party agent skill: review the Security Audits panel on this Prism page, confirm what filesystem, shell, network, or MCP access your client will grant, and avoid pointing automation at sensitive documents until you have run the skill’s verification checks o
SKILL.md
READMESKILL.md - Word Document
# Changelog ## [2026-04-25] - Version 1.2 Verification Protocol Refresh ### Added - Added a `Verification Protocol` section with skill-specific pass/fail checks, one pressure-test scenario, and a measurable success metric. - Added guidance to leverage native parallel subagent dispatch and 200k+ context windows where available. - Added the shared `MCP Fallback ? Native Automation` section for Office-style workflows. ### Changed - Updated `SKILL.md` frontmatter to `version: "1.2"` and `last_updated: 2026-04-25`. - Reframed activation guidance toward symptom -> action triggers and standardized two-stage review wording where applicable. ## [2026-04-24] - Version 1.1 Refresh ### Changed - Updated the SKILL frontmatter version to `1.1` for the 2026-04-24 catalog refresh. All notable changes to this skill will be documented in this file. ## [2026-04-24] - Skill Refresh ### Changed - Standardized the SKILL frontmatter with version metadata, last-updated date, tags, and a concise catalog description. - Reformatted the portability and MCP guidance with a preferred server line, a copy-paste fallback prompt, and consistent bullet lists. - Added a catalog-standard Anti-Patterns section and refreshed the Related Skills links at the end of the skill. - Added a Tech Stack Target / Version note so Word automation guidance is tied to current OOXML-compatible workflows. ## [2026-04-04] - Cross-Client Portability Refresh ### Changed - Added a standard portability note covering GitHub Copilot, Claude Code, Codex, and Gemini CLI. - Documented the preferred MCP server surface for this skill and a local no-MCP fallback workflow. ### Tested - Validated `SKILL.md` frontmatter, portability sections, and Gemini export readiness with `python scripts/validate-skills.py`. ## [2026-03-09] - Workspace Modernization ### Changed - Rewrote the skill to describe Word MCP access as host-specific instead of assuming stable wrapper commands - Repositioned the local document generator as the fallback path when Word MCP tools are unavailable ## [2026-02-28] - Description Rewrite and Cross-References ### Changed - Rewrote the skill description to concise activation-focused wording - Improved keyword specificity to reduce overlap with related skills ### Added - Added the related-skills cross-reference table ## [2026-02-19] - Word MCP Extraction ### Changed - Split Word workflow guidance out of the former shared office-documents skill into a Word-specific skill - Replaced library-first guidance with MCP-oriented document workflows - Updated activation triggers around `.docx`, Word documents, and Word MCP use cases ### Added - Added Word-specific references, examples, and local document-generation support - Added coverage for document structure, formatting, tables, and review-oriented workflows ### Fixed - Reduced ambiguity between generic office-document handling and Word-specific document tasks # Professional Word Report Generation Example Complete example of generating a multi-section business report using the `docx` npm package. ## Output Structure ``` 1. Title Page — company logo, report title, subtitle, date, author 2. Table of Contents — auto-generated from headings 3. Executive Summary — narrative overview 4. Key Metrics Table — formatted data table with alternating row colors 5. Quarterly Breakdown — detail section with sub-tables 6. Chart Placeholder — described image placeholder 7. Appendix — supplementary data, methodology notes ``` --- ## Style Configuration Reusable style object for consistent branding across reports. ```javascript const REPORT_STYLES = { colors: { primary: "1F4E79", // dark blue primaryLight: "D6E4F0", // light blue background accent: "2E75B6", // medium blue text: "333333", textLight: "666666", headerBg: "1F4E79", headerText: "FFFFFF", altRowBg: "F2F7FB", borderColor: "B4C6E0", success: "28A745", warning: "FFC107", danger: "DC3545", }, fonts: {