How to Install the docx Skill in Claude Code (2026)

You ask Claude for a project proposal. It hands back a wall of markdown. Now your boss wants it as a Word file by 3pm, so you paste it into Word, fix the headings that came in as # Heading, rebuild the table that arrived as pipes and dashes, add page numbers, and set the title in a bigger font. Twenty minutes gone on formatting a thing that was already written.

The docx skill kills that step. Instead of returning text you have to reshape, Claude produces an actual .docx file with real Word headings, a table of contents, tables, images, and page numbers already in place. You open it and it looks like a document, not a transcript.

This guide covers what the skill does, how to install it in Claude Code, and how to get a finished Word file from a single prompt.

What the docx skill actually is

It's one of Anthropic's official document skills, the same family as pdf, pptx, and xlsx. All four live in one place: github.com/anthropics/skills. The docx one teaches Claude how to read, create, and edit Word files, and it drives Python document tooling under the hood (the python-docx side of things) so the output is a genuine Office file rather than something faked with HTML.

With it installed, Claude can add headings and a table of contents, build tables, drop in images, set page numbers, run find-and-replace across a document, and work with tracked changes and comments. I haven't stress-tested every corner of the tracked-changes support, so treat that feature as capable-but-verify rather than bulletproof.

docx vs copy-paste vs the other document skills

Before you install anything, here's when each option makes sense.

Rule of thumb: if the person receiving it will open it in Word and maybe edit it, use docx. If it's a locked final artifact, reach for pdf. Data and formulas go to xlsx. Slides go to pptx. The skills stack, so a single request can produce a report in Word and its numbers in a spreadsheet. If you're weighing skills against connecting external tools, the difference is covered in MCP servers vs agent skills.

Installing it in Claude Code

Skills in Claude Code are folders. Each one is a directory containing a SKILL.md file that tells Claude what the skill does and when to reach for it. Claude reads those files and pulls in the right skill on its own when your request matches.

Step 1: Get the skill from the repo

Clone Anthropic's skills repo so you have the files locally:

git clone https://github.com/anthropics/skills.git

Inside, look for the document skills. The docx skill is a folder with its own SKILL.md and supporting scripts. Open that SKILL.md and read it before you go further (more on why in the security section below).

Step 2: Put it where Claude Code looks

Claude Code discovers personal skills in a skills directory under your Claude config, with each skill in its own subfolder:

~/.claude/skills/docx/SKILL.md

Copy the docx folder from the cloned repo into ~/.claude/skills/ so the path above exists. On Windows that's the same idea under your user profile (C:\Users\<you>\.claude\skills\docx\).

Anthropic also supports a plugin/marketplace flow, where you add a collection of skills through Claude Code's plugin commands instead of copying folders by hand. Both routes end at the same place: the skill sits somewhere Claude Code scans. The repo README is the source of truth for the exact plugin command, and I'd rather send you there than print a one-liner that might be out of date by the time you read this. Check the README in github.com/anthropics/skills for the current install command.

Step 3: Confirm Claude picked it up

Start or restart Claude Code in your project, then ask it something plain like "which skills do you have available?" or just request a Word document. If the skill loaded, Claude will reference its docx capability when a .docx task comes up. You don't invoke it with a special command. It activates when your ask matches the skill's description.

Step 4: Your first real document

Try a prompt with some substance to it:

> Draft a 3-page project proposal as a .docx. Add a title page with the project name and date, a table of contents, three sections (Overview, Timeline, Budget), and put the budget in a table with columns for Item, Cost, and Notes.

What comes back is a .docx file you can open in Word or Google Docs. The title page is a title page, the contents list links to the sections, and the budget is a real table you can click into and edit, not text pretending to be one.

Step 5: Editing a document you already have

The skill reads existing files too, so you can hand it a Word doc and ask for changes:

> In contract-v2.docx, replace every instance of "Net 30" with "Net 45", then add a signature table at the end with rows for Client and Provider.

Claude runs the find-and-replace and appends the table, keeping the rest of the document intact. Good for the boring edits nobody wants to do by hand across a long agreement.

A few prompts and what they return

A formatted letter:

> Write a resignation letter as a .docx, formal tone, addressed to Sarah Chen, two weeks notice from today, with my name and a signature line at the bottom.

You get a properly laid-out letter file: date, recipient block, body, sign-off, and a signature line, ready to print or attach.

A report with a chart-style table:

> Turn these Q2 numbers into a one-page summary .docx with a heading, a short intro paragraph, and a table of the figures. [paste numbers]

Back comes a tidy one-pager with the numbers in a Word table. If you also want that data as a spreadsheet, the how to install the xlsx skill guide covers the matching workflow.

A template you'll reuse:

> Build a meeting-minutes template .docx with fields for Date, Attendees, Agenda, Decisions, and Action Items, using headings so it's easy to fill in each week.

The result is a reusable skeleton with proper headings, the kind of thing you'd otherwise copy from an old file every Monday.

Where it falls short

The skill is strong on structure and weak on art direction. A few honest limits:

Heavily branded layouts, exact color palettes, custom fonts, and pixel-placed logos still need a human pass in Word. Claude gets you a clean, correct document; it doesn't get you your company's design system.

Very large documents can get slow or unwieldy, and the more complex the formatting, the more worth it is to open the file and skim it before you send it anywhere.

Tracked changes and comments work, but edge cases exist, especially in files that already carry a messy revision history from several editors. Spot-check those.

And the plain rule for anything client-facing: open the generated file and read it. Claude is good, not psychic, and a thirty-second look catches the odd misplaced table or heading that slipped a level.

Only install skills you trust

Here's the part worth slowing down for. Skills can run code on your machine, which is exactly what makes the docx skill useful and also what makes a bad skill dangerous. Treat every skill like software you're installing, because that's what it is.

Two habits keep you safe. First, get skills from a source you actually trust. For the document skills, that's Anthropic's own repo at github.com/anthropics/skills and nowhere else. Second, open the SKILL.md and any scripts before you copy them in, and read what they do. You don't need to be a security researcher; you're just checking that a skill for making Word files isn't quietly reaching for your files or the network. The same caution applies to the how to install the PDF skill setup and any other skill you pick up.

FAQ

Do I need Microsoft Word installed for this to work?

No. The skill builds the .docx file directly using Python document tooling, so it doesn't drive a copy of Word. You can open the result in Word if you have it, or in Google Docs, LibreOffice, or Apple Pages.

Is the docx skill free?

The skill itself is open and free from Anthropic's public repo. You still need Claude Code and a Claude plan to run it, so the cost is whatever your Claude usage costs, not a separate fee for the skill.

Can it edit a document I already have, or only make new ones?

Both. Point it at an existing .docx and ask for find-and-replace, a new table, added sections, or updated headings. It reads the file, makes the change, and saves it back.

Is it safe to install?

It's safe when you get it from Anthropic's official repo and skim the SKILL.md first. The real risk with any skill is installing one from an unknown source, since skills can run code. Stick to trusted sources and you're fine.