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 communicates capabilities and when to use the skill, with good specificity around tracked changes, comments, and formatting preservation. Its main weaknesses are the lack of common user-facing trigger terms like 'Word document' or 'Microsoft Word', and the overly broad 'any other document tasks' catch-all that could cause conflicts with other document-related skills.
Suggestions
Add common user trigger terms like 'Word document', 'Microsoft Word', 'Word file', '.doc' to improve discoverability when users use application-name-based language.
Replace the vague 'any other document tasks' with more specific examples 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 scenarios). | 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 file extension. | 2 / 3 |
Distinctiveness Conflict Risk | The phrase 'document tasks' and 'editing content' are somewhat generic and could overlap with PDF skills or general text editing skills. However, the '.docx files' mention and 'tracked changes' help narrow the niche. The broad 'any other document tasks' catch-all increases conflict risk. | 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 Chinese-language agent/MCP section at the top which adds token overhead for optional tooling, and some minor verbosity in explaining concepts Claude already knows (like what a .docx file is). 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 significant tokens and mixes languages unnecessarily.
Remove the sentence explaining what a .docx file is ('A .docx file is essentially a ZIP archive containing XML files...') as 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 tight. | 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 references to detailed documentation files. The redlining workflow includes specific grep verification commands and batch sizing guidance. | 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 specific grep commands to confirm changes. The decision tree at the top clearly routes users to the right workflow. Batch-then-validate feedback loops are present for the most complex (tracked changes) workflow. | 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
3dd3ac0
- 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.