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 includes explicit trigger guidance with a numbered list of use cases. Its main weakness is the absence of the term 'Word' or 'Microsoft Word', which is the most natural way users refer to .docx files, and some generic phrasing ('document tasks') that could cause overlap with other document-handling skills.
Suggestions
Add 'Word' and 'Microsoft Word' as trigger terms since users most naturally refer to .docx files this way (e.g., 'Word documents, Microsoft Word, .docx files').
Replace the vague catch-all 'or 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, analysis, tracked changes, comments, formatting preservation, and text extraction. These are clear, actionable 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 some good terms like '.docx files', 'tracked changes', 'comments', 'documents', but misses common user variations like 'Word', 'Microsoft Word', '.doc', 'word processing'. Users most naturally say 'Word document' rather than 'professional documents'. | 2 / 3 |
Distinctiveness Conflict Risk | The '.docx files' mention helps distinguish it, but phrases like 'document creation' and 'editing content' are quite generic and could overlap with other document-related skills (e.g., PDF, plain text, or general writing 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 with excellent workflow clarity and progressive disclosure. The decision tree effectively routes to the right workflow, and each workflow has clear steps with validation checkpoints. The main weakness is the Chinese-language agent/MCP section at the top which adds token overhead for optional tooling recommendations, and some minor verbosity in explanations that Claude wouldn't need.
Suggestions
Remove or significantly condense the '智能体与 MCP 增强' section — it's optional tooling context that consumes significant tokens and mixes languages unnecessarily
Remove the explanation of what a .docx file is ('essentially a ZIP archive containing XML files') from the Overview 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 rather than core skill instructions. The overview explaining what a .docx file is ('essentially a ZIP archive containing XML files') is mildly redundant for Claude. However, the core workflows are reasonably lean. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout: specific pandoc commands with flags, python script invocations with exact arguments, bash commands for conversion, and even inline XML examples showing good vs bad tracked change patterns. The redlining workflow includes specific grep verification commands. Code examples are copy-paste ready. | 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. Batching strategy with explicit size guidance (3-10 changes) and the 'grep immediately before writing a script' note show awareness of error-prone steps. The editing workflow has unpack→edit→pack with validation. | 3 / 3 |
Progressive Disclosure | The skill serves as a clear overview/router that points to detailed files (docx-js.md, ooxml.md, AGENTS.md) with well-signaled one-level-deep references. Each workflow section tells you exactly which file to read and approximately how long it is (~500 lines, ~600 lines). Content is appropriately split between the overview and referenced 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-data
- Commit
b1a95aa
- 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.