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 'when to use' guidance with numbered scenarios. 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 phrase 'any other document tasks' which could cause conflicts with other document-related skills.
Suggestions
Add 'Word', 'Microsoft Word', and '.doc' as trigger terms since users naturally refer to these documents by application name rather than just 'documents' or '.docx'.
Replace the vague catch-all 'any other document tasks' with more specific capabilities or remove it to reduce conflict risk with other document-handling 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 explicit triggers ('When Claude needs to work with professional documents (.docx files) for:' followed by numbered use cases). | 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 often 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. Missing 'Word' as a distinguishing keyword hurts distinctiveness. | 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, strong actionability through concrete commands and examples, and good progressive disclosure via external reference files. The main weakness is the verbose Chinese-language agent/MCP section at the top which consumes significant tokens for optional recommendations, and some minor explanations of concepts Claude already knows. Overall, it's a high-quality skill that effectively guides complex document manipulation tasks.
Suggestions
Remove or significantly condense the '智能体与 MCP 增强' section — it's optional tooling context that consumes many tokens and could be moved to a separate file like AGENTS.md
Remove the sentence explaining what a .docx file is ('A .docx file is essentially a ZIP archive containing XML files...') since 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, and the overview paragraph explaining what a .docx file is ('essentially a ZIP archive containing XML files') is something Claude already knows. The core workflows are reasonably lean. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout (pandoc, unpack/pack scripts, soffice, pdftoppm), specific code examples for tracked changes (good vs bad XML patterns), and clear tool references. The redlining workflow includes detailed implementation guidance with grep verification patterns and batch strategies. | 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 right workflow, and the batching strategy includes feedback loops (test each batch before moving to next). | 3 / 3 |
Progressive Disclosure | The skill serves as a clear overview with well-signaled one-level-deep references to docx-js.md, ooxml.md, and AGENTS.md. Content is appropriately split between the overview (workflow decisions, key commands) and detailed reference files. Navigation is straightforward with the decision tree at the top. | 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.