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
88
81%
Does it follow best practices?
Impact
100%
1.28xAverage score across 3 eval scenarios
Passed
No known issues
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 enumerates capabilities and provides explicit trigger conditions via a numbered list. Its main weaknesses are the lack of 'Word' or 'Microsoft Word' as trigger terms (which users would naturally say) and the overly broad catch-all 'any other document tasks' which could cause conflicts with other document-related skills.
Suggestions
Add 'Word', 'Microsoft Word', '.doc', and 'Word document' as trigger terms since users commonly refer to these files by application name rather than just 'documents' or '.docx'.
Narrow the catch-all phrase 'any other document tasks' to something more specific like 'any other .docx document tasks' to reduce conflict risk with PDF, text, or other document-type 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' (explicit numbered trigger scenarios: creating new documents, modifying content, working with tracked changes, adding comments, plus a catch-all for other document tasks). | 3 / 3 |
Trigger Term Quality | Includes '.docx files', 'documents', 'tracked changes', 'comments', but misses common user variations like 'Word document', 'Word file', '.doc', 'Microsoft Word', or 'DOCX'. Users frequently refer to these by the application name rather than the generic term 'documents'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'documents' is quite broad and could overlap with PDF skills, plain text editing, or other document-related skills. While '.docx files' adds specificity, the phrase 'any other document tasks' at the end significantly broadens the scope and increases conflict risk. Adding 'Word' or 'Microsoft Word' would help distinguish it more clearly. | 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 with excellent workflow clarity and progressive disclosure. The decision tree, detailed redlining workflow with validation steps, and clear references to supporting files are strong points. The main weaknesses are the verbose Chinese-language agent/MCP section at the top (which may not be relevant to all users and adds token overhead) and some unnecessary explanatory text that Claude doesn't need.
Suggestions
Remove or significantly condense the Chinese-language agent/MCP section at the top, or move it to a separate file, as it adds ~15 lines of optional tooling recommendations before the core content.
Remove the explanatory sentence 'A .docx file is essentially a ZIP archive containing XML files and other resources that you can read or edit' from the overview—Claude already knows this.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content. The Chinese-language agent/MCP section at the top adds significant tokens for what amounts to optional tooling recommendations. The overview paragraph explaining what a .docx file is ('essentially a ZIP archive containing XML files') is unnecessary for Claude. However, the core workflows are reasonably lean. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout (pandoc, unpack/pack scripts, soffice, pdftoppm) with specific flags and arguments. The redlining workflow includes a detailed good/bad XML example showing exactly how to implement minimal tracked changes. References to external files (ooxml.md, docx-js.md) are clearly signaled for detailed API patterns. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps and explicit validation checkpoints. The redlining workflow includes a final verification step with grep commands to confirm changes. The decision tree at the top clearly routes users to the correct workflow. Batching strategy with feedback loops (test each batch before moving on) is well-articulated. | 3 / 3 |
Progressive Disclosure | The skill serves as a clear overview with well-signaled one-level-deep references to ooxml.md, docx-js.md, and AGENTS.md. Core workflows are summarized in the main file with detailed documentation delegated to separate files. The decision tree provides excellent navigation for choosing the right workflow. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- majiayu000/claude-skill-registry-data
- Commit
6770aaa
- 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.