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
Quality
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 well-structured description that clearly articulates capabilities and provides explicit trigger scenarios. The main weaknesses are missing common user terms like 'Word' or 'Word document' and some generic language ('document tasks') that could cause skill selection conflicts with other document-handling skills.
Suggestions
Add common trigger terms users would naturally say: 'Word', 'Word document', 'Microsoft Word', '.doc'
Replace the generic 'any other document tasks' with more specific triggers to reduce conflict risk with other document skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'document creation, editing, and analysis', 'tracked changes, comments, formatting preservation, and text extraction'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (comprehensive document creation, editing, analysis with tracked changes, comments, formatting, extraction) AND when (explicit numbered list of trigger scenarios: creating, modifying, tracked changes, comments, document tasks). | 3 / 3 |
Trigger Term Quality | Includes '.docx files' and 'documents' but misses common variations users might say like 'Word', 'Word document', 'doc file', or 'Microsoft Word'. The technical term 'tracked changes' is good but coverage is incomplete. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'documents' and 'professional documents' is somewhat generic and could overlap with PDF skills or other document-handling skills. The '.docx' specification helps but 'document tasks' is broad enough to cause potential conflicts. | 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 actionability. The decision tree, batched change strategy, and verification steps demonstrate thoughtful design for complex document operations. The main weakness is some unnecessary content (Chinese section, basic explanations) that could be trimmed for better token efficiency.
Suggestions
Remove or relocate the Chinese '智能体与 MCP 增强' section - it adds ~15 lines of content that could be in a separate file or removed entirely if not essential
Remove the explanation that '.docx file is essentially a ZIP archive containing XML files' - Claude already knows this
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like the Chinese agent/MCP enhancements that add bulk without clear actionable value. The overview explaining what a .docx file is ('essentially a ZIP archive') is unnecessary context Claude already knows. | 2 / 3 |
Actionability | Provides fully executable commands and code examples throughout - pandoc commands, Python scripts for pack/unpack, bash commands for conversion, and concrete XML patterns for tracked changes. The good/bad example for minimal edits is particularly actionable. | 3 / 3 |
Workflow Clarity | Excellent workflow structure with clear decision tree, numbered steps for each workflow, explicit validation steps (final verification with grep), and feedback loops for batch processing. The redlining workflow includes comprehensive checkpoints and batching strategy. | 3 / 3 |
Progressive Disclosure | Well-organized with clear overview pointing to detailed files (docx-js.md, ooxml.md, AGENTS.md). References are one level deep and clearly signaled with file sizes noted. Content is appropriately split between quick-reference commands and detailed documentation. | 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
- Commit
6213d1a
- 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.