word-document
Build a real, formatted Word (.docx) document — headings, styles, tables, TOC-ready. Use when asked to produce a Word doc, a .docx, a formatted report/contract/proposal/letter as an actual file (not markdown). Produces an actual .docx via a generated python-docx script with proper heading styles, body text, tables, and page structure. Requires a code-execution environment (Claude Code, the API code tool, or Claude.ai).
npx skills add mohitagw15856/pm-claude-skills --skill word-document --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Word Document Skill When someone needs an actual `.docx` — a report, proposal, contract, or formal letter they'll edit in Word — markdown won't do. This skill produces a real Word file by **writing and running a `python-docx` script**: proper heading styles (so the navigation pane and a TOC work), clean body text, tables, and page structure — a document that looks authored, not exported. > **Environment:** produces a binary file, so it needs code execution — **Claude Code**, the > **API code-execution tool**, or **Claude.ai**. In the browser playground, the existing Word/PDF export > turns any skill's markdown into a document; this skill is for a built-to-spec `.docx`. ## Required Inputs Ask for these only if they aren't already provided: - **Document type** — report, proposal, contract, SOP, letter, whitepaper — and its purpose/audience. - **The content** — the material (or a brief to expand), and the required sections/structure. - **Formatting needs** — headings/TOC, tables, numbered clauses (contracts), a cover page, letterhead/brand. - **Length & tone**. ## Process 1. **Outline the structure** — the section hierarchy (H1/H2/H3), and where tables or numbered clauses go. Confir
- Required Inputs
- Process
- Output Format
- Quality Checks
- Anti-Patterns
- Based On
- Programmatic Helper
Markdown-lite → Word (#/##/### headings, - bullets, 1. numbered, **bold**, *italic*)
python3 scripts/docx_tool.py create out.docx --text-file doc.md
Fill {{placeholders}} through an existing .docx (body, headers, footers) —
handles Word splitting a placeholder across formatting runs
python3 scripts/docx_tool.py fill template.docx out.docx --values '{"client":"Acme","date":"2026-07-03"}'
Verify what a .docx actually says (plain-text extraction)
python3 scripts/docx_tool.py extract out.docxWhat does the word-document skill do?
Build a real, formatted Word (.docx) document — headings, styles, tables, TOC-ready. Use when asked to produce a Word doc, a .docx, a formatted report/contract/proposal/letter as an actual file (not markdown). Produces an actual .docx via a generated python-docx script with proper heading styles, body text, tables, and page structure. Requires a code-execution environment (Claude Code, the API code tool, or Claude.ai).
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill word-document --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.