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.28x

Quality

75%

Does it follow best practices?

Impact

100%

1.28x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/data/06-office-docx/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is actionable and reasonably well-organized with concrete commands and a strong redlining verification loop, but it is held back by redundant batching prose, a missing validation checkpoint in the basic editing path, and bundle references that do not exist as actual files.

Suggestions

Add an explicit validation step (e.g., `python ooxml/scripts/validate.py <dir>` or a structural check) between editing and packing in the basic editing workflow, mirroring the redlining verification loop.

De-duplicate the redlining batch-grouping guidance — keep a single 'Batch organization' section and remove the repeated 'Suggested batch groupings' list.

Provide the referenced bundle files (docx-js.md, ooxml.md, AGENTS.md, and the ooxml/scripts/*.py scripts) in the skill bundle, or remove links to files that are not shipped.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and code, but contains redundant prose — the 'Batch organization' list and 'Suggested batch groupings' list in the redlining workflow repeat the same grouping advice, and 'MANDATORY - READ ENTIRE FILE' phrasing recurs three times.	3 / 5
Actionability	Provides executable commands (pandoc, unpack.py/pack.py, soffice, pdftoppm) and a concrete GOOD/BAD XML edit example; minor gaps only where steps defer to 'see ooxml.md' for the actual API.	4 / 5
Workflow Clarity	The redlining workflow has explicit final verification with grep checks, but the basic editing workflow (unpack → edit → pack) lacks an explicit validate checkpoint before packing; per the rubric, missing validation in destructive/batch document manipulation caps this at 3.	3 / 5
Progressive Disclosure	The body is well-structured with one-level-deep markdown references (docx-js.md, ooxml.md, AGENTS.md, ooxml/scripts/*.py), but none of the referenced bundle files actually exist in the bundle (no references/, scripts/, or assets/ directories present), so the signaled navigation points to missing material.	3 / 5
	Total	13 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it is specific, third-person, and clearly answers both what the skill does and when to use it with concrete enumerated triggers. Minor room for improvement only in adding common synonyms like 'Word' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'document creation, editing, and analysis', 'tracked changes, comments, formatting preservation, and text extraction' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (creation/editing/analysis with tracked changes, comments, formatting, extraction) and 'when' via the enumerated 'When Claude needs to work with professional documents (.docx files) for: (1)... (2)... (3)...' trigger clause.	5 / 5
Trigger Term Quality	Includes the natural file extension '.docx files' and phrases like 'creating new documents', 'tracked changes', and 'comments', but misses common synonyms such as 'Word' or 'Word documents' that users often say.	4 / 5
Distinctiveness Conflict Risk	Scoped to '.docx' professional documents with distinct triggers (tracked changes, comments), creating a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: majiayu000/claude-skill-registry
Path: skills/data/06-office-docx/SKILL.md
Commit: 04324c6

Reviewed: about 19 hours 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.