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

76%

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

Fix and improve this skill with Tessl

tessl review fix ./resources/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.

The body is well-organized with concrete commands, a decision tree, and a redlining workflow that includes verification. Its main weaknesses are redundant batch-grouping text and references to mandatory detail files that are not present in the bundle.

Suggestions

De-duplicate the batch-organization guidance: the 'Batch organization' list (lines 111-116) and 'Suggested batch groupings' list (lines 127-130) repeat the same by-section/by-type/by-proximity categories — keep one.

Add the missing referenced files (docx-js.md, ooxml.md) and scripts (ooxml/scripts/unpack.py, pack.py) to the bundle, or inline the essential content so the mandatory-read instructions are actionable.

Insert an explicit validation checkpoint in the basic editing workflow (e.g., validate XML or re-open the packed docx) before the pack step, mirroring the redlining workflow's verification step.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the batch-grouping guidance is duplicated (lines 111-116 and 127-130 list the same by-section/by-type/by-proximity groupings) and the emphatic 'MANDATORY - READ ENTIRE FILE' block repeats three times, so it could be tightened.	3 / 5
Actionability	Provides executable commands (pandoc, soffice, pdftoppm, unpack/pack scripts) and a copy-pasteable BAD/GOOD XML redlining example, with only minor gaps where the referenced library docs are unavailable.	4 / 5
Workflow Clarity	A decision tree plus numbered workflows give a clear sequence, and the redlining workflow has an explicit final-verification feedback loop (step 6, grep checks); the basic editing workflow lacks a validate-before-pack checkpoint, a minor validation gap.	4 / 5
Progressive Disclosure	The body is structured as an overview with clearly signaled one-level references to docx-js.md and ooxml.md, but those files (and ooxml/scripts/unpack.py, pack.py) are absent from the actual bundle, so the navigation chain is broken rather than merely imperfect.	3 / 5
	Total	14 / 20 Passed

Description

88%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 provides an explicit 'When Claude needs to...' trigger clause enumerating use cases. It closely matches the rubric's good-overall example for presentation skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction' — giving comprehensive coverage rather than vague domain naming.	5 / 5
Completeness	Explicitly answers both what (creation, editing, analysis, tracked changes, etc.) and when via 'When Claude needs to work with professional documents (.docx files) for: (1)...(4) any other document tasks'.	5 / 5
Trigger Term Quality	Includes natural terms 'documents', '.docx files', 'tracked changes', and 'comments', but omits common synonyms like 'Word documents' or 'Word files' that users would naturally say.	4 / 5
Distinctiveness Conflict Risk	Scoped to '.docx files' / 'professional documents' with distinct triggers, but the generic 'documents' framing carries minor overlap risk with related document/presentation skills.	4 / 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: ThinkInAIXYZ/deepchat
Path: resources/skills/docx/SKILL.md
Commit: fa769d4

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.