docx
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
85
81%
Does it follow best practices?
Impact
91%
1.62xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
77%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly communicates capabilities and includes explicit trigger guidance with a numbered use-case list. Its main weakness is the absence of 'Word' and 'Microsoft Word' as trigger terms, which are the most natural terms users would use when requesting this skill. The catch-all phrase 'any other document tasks' slightly undermines distinctiveness.
Suggestions
Add 'Word', 'Microsoft Word', and '.doc' as trigger terms since these are the most natural terms users would say when needing this skill.
Replace the vague catch-all 'any other document tasks' with more specific triggers or remove it to reduce conflict risk with other document-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: document creation, editing, analysis, tracked changes, comments, formatting preservation, and text extraction. These are clearly defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (document creation, editing, analysis, tracked changes, comments, formatting preservation, text extraction) and 'when' with an explicit numbered list of trigger scenarios ('When Claude needs to work with professional documents (.docx files) for...'). | 3 / 3 |
Trigger Term Quality | Includes '.docx files' and 'documents' as trigger terms, plus action-oriented terms like 'tracked changes' and 'comments'. However, it's missing common user variations like 'Word', 'Word document', 'Microsoft Word', '.doc', which are the most natural terms users would say. | 2 / 3 |
Distinctiveness Conflict Risk | The '.docx files' mention helps distinguish it, but the broad phrase 'any other document tasks' and generic terms like 'document creation' and 'editing content' could overlap with PDF skills, plain text editing skills, or general document skills. Missing 'Word' as a key distinguishing term weakens its niche clarity. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that provides clear decision trees, concrete workflows, and good progressive disclosure to supporting documentation. Its main weakness is some redundancy in the redlining section (batching strategy explained twice) and minor verbosity in the overview explaining what a .docx file is. Overall it's a strong, actionable skill that would effectively guide Claude through document operations.
Suggestions
Remove the duplicate batching strategy explanation in step 4 of the redlining workflow since it's already covered between steps 2 and 3.
Remove the explanatory sentence about .docx files being ZIP archives in the overview—Claude already knows this.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy—the batching strategy and batch groupings are explained twice (in the redlining overview and again in step 4), and the 'MANDATORY - READ ENTIRE FILE' instruction is repeated three times verbatim. Some explanatory text like 'A .docx file is essentially a ZIP archive' explains what Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout (pandoc, unpack/pack scripts, soffice, pdftoppm) with specific flags and options. The redlining workflow includes a detailed XML example showing good vs bad tracked change implementation, and all workflows reference specific tools and files. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps. The redlining workflow includes explicit validation (step 6 with grep verification), feedback loops (batch-then-verify approach), and the decision tree at the top provides clear routing. The editing workflow has unpack→edit→pack with documentation reading as a prerequisite. | 3 / 3 |
Progressive Disclosure | The skill serves as a clear overview with well-signaled one-level-deep references to docx-js.md and ooxml.md for detailed API documentation. Content is appropriately split—the SKILL.md covers workflows and decision-making while detailed library APIs live in referenced files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
7cc63f3
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.