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
87
Quality
85%
Does it follow best practices?
Impact
91%
1.62xAverage score across 3 eval scenarios
Discovery
85%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 strong skill description that clearly articulates capabilities and provides explicit trigger conditions through a numbered use-case list. The main weakness is the trigger term coverage, which relies heavily on '.docx' without including common synonyms like 'Word document' or 'Microsoft Word' that users naturally use.
Suggestions
Add common trigger term variations: 'Word document', 'Word file', 'Microsoft Word', '.doc' to improve discoverability when users use these natural phrases
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction.' These are clear, 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 use cases: creating, modifying, tracked changes, comments, and 'any other document tasks'). | 3 / 3 |
Trigger Term Quality | Includes '.docx files' and 'professional documents' but misses common variations users might say like 'Word document', 'Word file', 'Microsoft Word', or 'doc'. The trigger terms are somewhat limited. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to .docx files specifically, with distinct features like tracked changes and comments that differentiate it from generic document or PDF skills. The explicit file extension creates a clear niche. | 3 / 3 |
Total | 11 / 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 guides Claude to the right workflow, and the redlining workflow includes proper validation checkpoints and batching strategies. Minor verbosity in the overview section and some explanatory text that Claude doesn't need slightly reduce token efficiency.
Suggestions
Remove the explanatory sentence 'A .docx file is essentially a ZIP archive containing XML files and other resources that you can read or edit' - Claude already knows this.
Consider condensing the 'Workflow Decision Tree' section into a more compact format, as some of the conditional logic could be expressed more tersely.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation (e.g., 'A .docx file is essentially a ZIP archive containing XML files' is something Claude knows). The decision tree and workflow sections are well-organized but could be tighter in places. | 2 / 3 |
Actionability | Provides fully executable commands and code examples throughout - pandoc commands, Python scripts, bash commands for conversion. The tracked changes example shows both bad and good patterns with concrete XML. Copy-paste ready. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflows with clear sequencing and validation. The redlining workflow includes explicit verification steps (grep checks, markdown conversion for verification), batching strategy with specific guidance (3-10 changes), and a final verification checklist. | 3 / 3 |
Progressive Disclosure | Clear overview structure with well-signaled one-level-deep references to docx-js.md and ooxml.md. Content is appropriately split between the main skill file (workflows, decision tree) and detailed reference files. Navigation is explicit with file paths and line counts. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.