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

78%

Does it follow best practices?

Impact

91%

1.62x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/docx/SKILL.md

Quality

Content

63%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.

A well-structured, largely actionable skill with a clear decision tree and thoughtful tracked-changes guidance (batching, minimal-edit principle, final verification). Its weaknesses are duplicated batching/boilerplate text, deferred core API examples, no pre-pack XML validation loop, and references that point to files absent from the provided bundle while the real scripts/ files go undocumented.

Suggestions

Deduplicate the batch-grouping guidance (step 2 'Batch organization' vs step 4 'Suggested batch groupings') and the thrice-repeated 'MANDATORY - READ ENTIRE FILE' boilerplate — state each once.

Fix reference paths to match the actual bundle: docx-js.md, ooxml.md, and ooxml/scripts/{unpack,pack}.py do not exist; point to the real scripts/ layout (document.py, utilities.py, templates/) or add the referenced files.

Add an explicit XML validation checkpoint after each batch (e.g., a validate step on the unpacked directory) with a fix-and-retry loop before running pack.py, instead of relying solely on post-pack markdown verification.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean (commands and examples over concept explanations), but carries real duplication: the batch-grouping guidance appears nearly verbatim twice ("Batch organization (group 3-10 related changes per batch)" in step 2 and "Suggested batch groupings:" in step 4), and the "MANDATORY - READ ENTIRE FILE ... NEVER set any range limits" boilerplate is repeated three times. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than level 4's 'minor instances'.	3 / 5
Actionability	Mostly executable: concrete pandoc/soffice/pdftoppm commands with flags, unpack/pack invocations, a grep-based verification snippet, and a GOOD/BAD XML example for minimal edits. It falls short of level 5 because the core editing mechanics (Document library methods, get_node usage, docx-js Document/Paragraph/TextRun syntax) have no inline example and are deferred entirely to ooxml.md / docx-js.md, and the tracked-changes snippet is a fragment rather than a runnable script.	4 / 5
Workflow Clarity	A decision tree routes tasks to clearly numbered workflows, and the redlining workflow includes per-batch testing ("Test each batch before moving to the next"), a re-grep-before-each-script note, and a final markdown verification with grep checks. It stops short of level 5 because there is no XML-level validation checkpoint before packing and no explicit fix-and-retry feedback loop — verification is post-hoc output checking only, which fits 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	Sectioning and one-level-deep references are well signaled ([docx-js.md], [ooxml.md]), but scored against the actual bundle the references are broken: docx-js.md, ooxml.md, and ooxml/scripts/unpack.py\|pack.py do not exist, while the files that do exist (scripts/document.py, scripts/utilities.py, scripts/templates/) are never referenced or made discoverable from the body. This is more than the level-4 'minor organization gaps' — navigation from SKILL.md to the real bundle fails, matching level 3's 'references present but' mis-organized structure.	3 / 5
	Total	14 / 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.

A strong description: concrete capability list, explicit third-person trigger guidance with enumerated use cases, and a clearly bounded .docx niche. The only gap is missing common synonyms such as 'Word' / 'Word documents' that users would naturally say.

Suggestions

Add 'Word' or 'Word documents' as a synonym alongside '.docx files' in the trigger clause, since users most often ask about 'Word docs'.

Consider tightening the catch-all 'or any other document tasks' to a more specific scope (e.g., 'or other .docx file tasks') to reduce overlap with generic document skills.

Dimension	Reasoning	Score
Specificity	Quotes multiple concrete capabilities — "document creation, editing, and analysis", "tracked changes, comments, formatting preservation, and text extraction" — giving comprehensive coverage of concrete actions. The lone softener ("Comprehensive") is backed by enumerated specifics, so it does not fall to the level-4 anchor with coverage gaps.	5 / 5
Completeness	Explicitly answers both what ("creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction") and when ("When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content..."). This mirrors the anchor-5 pattern with a concrete 'Use when'-style trigger clause and enumerated cases, so it is not the level-4 case of a weaker 'when'.	5 / 5
Trigger Term Quality	Good natural-term coverage: "tracked changes", "comments", "editing", ".docx files" are phrases users actually say, but common synonyms like "Word" or "Word documents" are absent. Not level 5 (which requires comprehensive synonym/extension coverage) yet clearly above level 3's partial keyword set.	4 / 5
Distinctiveness Conflict Risk	The ".docx files" niche plus distinctive triggers ("tracked changes", "comments") establishes a clear niche with minimal conflict risk, matching the level-5 anchor and the analogous good pptx example. The trailing "any other document tasks" catch-all is broad, but it is anchored to .docx work so it stays above the level-4 overlap-risk case.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/docx/SKILL.md
Commit: c9856ea

Reviewed: 6 days 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.