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

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

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

Quality

Content

82%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 dense, highly actionable skill body with strong code examples and a well-sequenced redlining workflow that includes verification. The main weaknesses are minor redundancy in the batch-grouping guidance, an undefined "Basic OOXML editing" workflow referenced by the decision tree, and a mismatch between some referenced script paths and the actual bundle layout.

Suggestions

Deduplicate the batch-organization advice: keep one canonical list (By section / By type / By proximity) in step 4 and remove the overlapping list in step 2, or vice versa.

Add a short "Basic OOXML editing" section (or rename the existing editing section to match) so the decision-tree branch resolves to actual content, and add an explicit validation step to the plain editing workflow.

Reconcile referenced script paths with the bundle: either point the unpack/pack commands at the actual `scripts/` contents or document where `ooxml/scripts/unpack.py` and `pack.py` live so navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and action-oriented with executable code blocks throughout, but batch-grouping advice is listed twice (step 2 "Batch organization" and step 4 "Suggested batch groupings" give near-identical By-section/By-type lists) and the "MANDATORY - READ ENTIRE FILE" directive is repeated. Matches the score-4 anchor (efficient, minor instances that could be trimmed); not a 5 due to that redundancy, not a 3 because no concepts Claude already knows are over-explained.	4 / 5
Actionability	Provides copy-paste-ready commands throughout — pandoc with --track-changes flags, `python ooxml/scripts/unpack.py`/`pack.py`, soffice and pdftoppm with each flag explained, and a concrete BAD-vs-GOOD OOXML example showing exact `<w:del>`/`<w:ins>` markup. Fully executable guidance covering common cases per the score-5 anchor.	5 / 5
Workflow Clarity	The redlining workflow has a clear 6-step sequence with an explicit final-verification checkpoint (pandoc + grep "should NOT find" / "should find"), satisfying the batch-operation validation requirement. However the decision tree references a "Basic OOXML editing workflow" that is never defined as a section, and the plain editing workflow (unpack → script → pack) lacks an explicit validation step. Clear sequence with most checkpoints but minor gaps, matching score 4 rather than 5.	4 / 5
Progressive Disclosure	SKILL.md acts as an overview with a decision tree and clearly signals one-level-deep references via MANDATORY-READ links to `docx-js.md` (~500 lines) and `ooxml.md` (~600 lines). Good structure per the score-4 anchor; not a 5 because referenced helper paths (`ooxml/scripts/unpack.py`, `pack.py`) do not match the visible bundle (scripts/ contains document.py, utilities.py, templates/*.xml) and the "Basic OOXML editing" workflow referenced in the decision tree has no corresponding section.	4 / 5
	Total	17 / 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, well-structured description that clearly states capabilities and enumerates explicit use-when triggers with the .docx extension. The only gap is missing natural synonyms (e.g., "Word documents") that would round out trigger-term coverage.

Suggestions

Add the synonym "Word documents" or "Word files" alongside ".docx files" so users who say "Word" trigger the skill naturally.

Consider leading with the trigger clause ("Use when Claude needs to work with .docx/Word files for...") so the 'when' appears before the capability list, improving scanability.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "document creation, editing, and analysis" plus "tracked changes, comments, formatting preservation, and text extraction" — giving comprehensive coverage rather than a single generic verb. This matches the score-5 anchor listing multiple specific concrete actions; it is not a 4 because coverage spans seven distinct capabilities with no real gaps.	5 / 5
Completeness	Explicitly answers both what ("Comprehensive document 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)... (2)... (3)... (4)...") with concrete trigger phrases. This fits the score-5 anchor cleanly; it is not a 4 because the 'when' clause is explicit and enumerated.	5 / 5
Trigger Term Quality	Includes natural terms and the file extension — "professional documents (.docx files)", "Creating new documents", "Modifying or editing content", "Adding comments" — but omits common synonyms like "Word files" or "Word documents". Good keyword coverage with a few natural terms missing, matching the score-4 anchor rather than 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Scoped to ".docx files" with distinctive features (tracked changes, comments, formatting preservation) that carve a clear niche apart from PDF or generic document skills. Minimal conflict risk per the score-5 anchor; not a 4 because the .docx + tracked-changes combination is highly specific.	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: netease-youdao/LobsterAI
Path: SKILLs/docx/SKILL.md
Commit: 100d3f7

Reviewed: 2 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.