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

1.62x

Quality

81%

Does it follow best practices?

Impact

91%

1.62x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

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, highly actionable skill that covers multiple DOCX workflows with clear decision routing and concrete examples. Its main weakness is some redundancy in repeated instructions (especially the mandatory file-reading directive and batching strategy explanation) and a minor unnecessary explanation of what .docx files are. The progressive disclosure and workflow clarity are excellent, with proper validation steps and clear references to supporting documentation.

Suggestions

Remove the redundant batching strategy explanation in step 4 since it's already covered in the overview before the workflow steps, or consolidate into a single location.

Consolidate the three identical 'MANDATORY - READ ENTIRE FILE' instructions into a single note at the top or a convention statement, rather than repeating verbatim in each workflow.

Dimension	Reasoning	Score
Conciseness	Generally efficient but has some redundancy: the batching strategy is explained twice (in the redlining overview and again in step 4), the 'MANDATORY - READ ENTIRE FILE' instruction is repeated three times verbatim, and some explanations like what a .docx file is are unnecessary for Claude. The decision tree and workflow sections are well-structured but could be tighter.	2 / 3
Actionability	Provides concrete, executable commands throughout (pandoc, unpack/pack scripts, soffice, pdftoppm), specific XML examples showing good vs bad tracked change patterns, clear tool choices for each scenario, and copy-paste ready code. The redlining workflow example with RSID preservation is particularly actionable.	3 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with numbered steps, validation checkpoints (step 6 final verification with grep checks), and feedback loops (batch-then-verify approach, 'fix and re-validate' implicit in batching). The decision tree at the top clearly routes to the right workflow. The redlining workflow includes explicit verification steps with concrete grep commands.	3 / 3
Progressive Disclosure	Excellent structure with a clear overview and decision tree up front, then detailed workflows below. References to external files (docx-js.md, ooxml.md) are well-signaled with descriptions of content and approximate line counts. Content is appropriately split between the overview SKILL.md and detailed reference files, with one-level-deep references.	3 / 3
	Total	11 / 12 Passed

Description

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 provides explicit trigger conditions via a numbered list. Its main weakness is the absence of the term 'Word' or 'Microsoft Word', which are the most natural terms users would use when requesting help with .docx files, and the overly broad catch-all 'any other document tasks' which could cause conflicts with other document-related skills.

Suggestions

Add 'Word', 'Microsoft Word', and '.doc' as trigger terms since these are the most natural ways users refer to .docx documents.

Replace the vague catch-all 'any other document tasks' with more specific triggers 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 with tracked changes, comments, formatting preservation, text extraction) and 'when' (explicit numbered trigger scenarios for when Claude should use this skill).	3 / 3
Trigger Term Quality	Includes '.docx files', 'documents', 'tracked changes', 'comments', but misses common user variations like 'Word', 'Word document', 'Microsoft Word', '.doc', which are the most natural terms users would say.	2 / 3
Distinctiveness Conflict Risk	The '.docx files' mention helps distinguish it, but 'document creation, editing, and analysis' and 'any other document tasks' are broad enough to potentially conflict with PDF skills or general document skills. Missing 'Word' as a key distinguishing term weakens distinctiveness.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: davepoon/buildwithclaude
Commit: 8c53c59

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.