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

The canonical home for this skill is docx in anthropics/skills

Quality

Content

68%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 highly actionable with executable commands and clear decision-tree routing, but redundant batch guidance and missing mid-process validation feedback loops limit conciseness and workflow clarity. Referenced detail files are signaled but not actually present in the bundle.

Suggestions

Add an explicit validate->fix->retry loop during batch tracked-change implementation (e.g., a pre-pack validation step), not just end-of-process grep verification, to lift workflow clarity above the cap.

De-duplicate the batch-organization guidance (steps 2 and 4 repeat the same by-section/by-type/by-proximity groupings) into a single concise section.

Reconcile referenced paths with the actual bundle: either include docx-js.md and ooxml.md, or correct the ooxml/scripts/unpack.py and pack.py paths to the real scripts/ layout.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and a decision tree, but batch-organization guidance is restated twice (steps 2 and 4) with overlapping examples and some padded explanation around batching strategy.	3 / 5
Actionability	Provides copy-paste-ready commands throughout (pandoc, unpack/pack, soffice, pdftoppm with flags) plus good/bad OOXML examples covering the common cases.	5 / 5
Workflow Clarity	Workflows are well sequenced with a final verification step, but batch/XML-document manipulation lacks an explicit validate->fix->retry feedback loop mid-process, which the rubric caps at 3.	3 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level references to docx-js.md and ooxml.md, but those referenced files are absent from the bundle and script paths mismatch (ooxml/scripts/unpack.py vs scripts/document.py), leaving minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

87%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 clearly communicates capabilities and explicit trigger conditions scoped to .docx work, with concrete enumerated use cases. It is slightly held back by mild fluff ('comprehensive') and missing 'Word' synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('creation, editing, and analysis', 'tracked changes, comments, formatting preservation, and text extraction') with only minor coverage gaps; 'comprehensive' and 'analysis' are mildly generic, keeping it below a 5.	4 / 5
Completeness	Explicitly states both what the skill does and when to use it, with concrete enumerated triggers ('When Claude needs to work with professional documents (.docx files) for: (1)... (2)...').	5 / 5
Trigger Term Quality	Includes natural terms and the file extension ('documents', '.docx files', 'tracked changes', 'comments') but misses common synonyms like 'Word' or 'Word documents'.	4 / 5
Distinctiveness Conflict Risk	Scoped narrowly to '.docx files' and 'professional documents' with distinct triggers, giving it a clear niche with minimal overlap risk.	5 / 5
	Total	18 / 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: a9fa86d

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