DOCX creation, editing, and analysis
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files).
- Context cost
- 4.8k tokensestimated from the bundle, loaded when it triggers
- Bundle
- 8 files · 19.1 kB1 script among them — read before you run
- Licence
- Proprietary. LICENSE.txt has complete termsfree to use
- Last change
- —no release on file
- Servers it uses
- Noneruns standalone
What it does
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word…
Installed, it changes the agent in these ways.
What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.
And these are the jobs people reach for it for.
Produces one artefact, exactly shaped.
The skill itself
This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.
Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.
What it costs in context
Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.
4.8k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.
A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.
Before and after
The same question, put to the same model twice: once as it comes, and once with these instructions loaded.
No worked example has been published for this skill yet.
The procedure it runs
The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.
These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.
Servers it uses
None. This skill calls no MCP servers at all.
Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.
It writes no files and reaches no network. All it changes is how the model reasons and writes.
Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.
What it will not do
Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.
What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.
What is in the bundle
8 files, 19.1 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to.
- LICENSE.txt1.5 kB
- scripts/__init__.py0.1 kB
- scripts/templates/comments.xml2.6 kB
- scripts/templates/commentsExtended.xml2.6 kB
- scripts/templates/commentsExtensible.xml2.7 kB
- scripts/templates/commentsIds.xml2.6 kB
- scripts/templates/people.xml0.1 kB
- SKILL.md6.9 kB
A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the bundle is 8 files you can review in full before installing. The Proprietary. LICENSE.txt has complete terms licence covers the templates and examples as well as the instructions.
Install
Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.
# DOCX creation, editing, and analysis · 4.8k tokens when loaded
npx mcprush@latest skill add anthropics/docx-creation-editing-and-analysisWrites to .claude/skills/docx-creation-editing-and-analysis/ in the current project. Add --global to put it in your home directory instead, for every project.
Which clients pick it up on their own
A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.
Versions
Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.
- No earlier releases have been published to the marketplace.
Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.
Reviews
Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.
Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.