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
Install with Tessl CLI
npx tessl i github:ComposioHQ/awesome-claude-skills --skill docxOverall
score
92%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.25xAgent success when using this skill
Validation for skill structure
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 description that clearly articulates specific capabilities and provides explicit trigger conditions through a numbered list. The main weakness is the trigger term coverage, which relies on '.docx' but omits the more common user term 'Word' or 'Word document' that users would naturally use when requesting help.
Suggestions
Add common user terms like 'Word', 'Word document', 'Microsoft Word', or 'doc' to improve trigger term coverage for how users naturally describe these files.
| 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 trigger scenarios: creating, modifying, tracked changes, comments, document tasks). | 3 / 3 |
Trigger Term Quality | Includes '.docx files' and 'professional documents' but misses common user terms like 'Word', 'Word document', 'doc file', or 'Microsoft Word' that users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to '.docx files' and 'professional documents' with specific features like tracked changes and comments that distinguish it from generic document or PDF skills. | 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 actionability. The decision tree provides clear guidance for choosing the right approach, and the redlining workflow demonstrates sophisticated understanding of validation and batching. Minor verbosity in the overview section and some explanatory content Claude already knows prevent a perfect conciseness score.
Suggestions
Remove the explanation 'A .docx file is essentially a ZIP archive containing XML files and other resources' - Claude already knows this
Tighten the overview paragraph to focus only on the workflow decision tree without restating what .docx files are
| 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. The bash commands for pandoc, pack/unpack scripts, and the XML examples are copy-paste ready with specific syntax and options explained. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflows with clear sequencing. The redlining workflow includes explicit validation steps (final verification with grep), batching strategy with specific guidance (3-10 changes), and feedback loops for error recovery. | 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 and detailed reference files, with explicit instructions to read those files completely. | 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.
- 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.