CtrlK
BlogDocsLog inGet started
Tessl Logo

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

84

1.62x
Quality

81%

Does it follow best practices?

Impact

91%

1.62x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A well-organized, highly actionable skill body with clear sequenced workflows and concrete verification steps. Its weaknesses are minor redundancy in the batching guidance and two mandatory-read reference files (docx-js.md, ooxml.md) that are referenced but absent from the bundle.

Suggestions

Ensure docx-js.md and ooxml.md are present in the bundle, or inline the essential API patterns so the MANDATORY read instructions resolve to real files.

Deduplicate the batch-organization guidance — keep the by section/type/proximity grouping in one place rather than repeating it across steps 2 and 4.

Drop or sharpen the generic "Code Style Guidelines" section, which restates defaults Claude already applies.

DimensionReasoningScore

Conciseness

Mostly lean with executable commands and a tight decision tree, but the batching guidance is restated (step 2 "Batch organization" vs step 4 "Suggested batch groupings" both list by section/type/proximity) and the generic "Code Style Guidelines" ("Write concise code", "Avoid verbose variable names") tells Claude what it already knows.

2 / 3

Actionability

Provides copy-paste-ready shell commands (pandoc, unpack/pack, soffice, pdftoppm with flags), a concrete GOOD/BAD OOXML redline example, and exact install commands, fully meeting the executable-guidance anchor.

3 / 3

Workflow Clarity

The redlining workflow is a clearly numbered 6-step sequence with per-batch testing ("Test each batch before moving to the next"), a re-grep checkpoint (line numbers change after each run), and a final verification step with concrete grep checks, satisfying explicit validation and feedback loops for a batch operation.

3 / 3

Progressive Disclosure

The body is structured as an overview that defers detail to one-level-deep, clearly signaled references ([docx-js.md], [ooxml.md] with MANDATORY read calls), but neither referenced markdown file exists in the bundle, so the navigation does not actually resolve and content is not split into present files.

2 / 3

Total

10

/

12

Passed

Description

85%

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, specific description that clearly states capabilities and explicit use-when triggers with a distinct .docx niche. Its main gap is trigger-term coverage: it never mentions "Word", the most common way users refer to these files.

Suggestions

Add "Word documents" / "Word files" / ".doc" as trigger terms alongside ".docx files" so the description matches how users most commonly phrase the request.

Consider trimming "Comprehensive" and "professional" which add little specificity relative to concrete action verbs.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "document creation, editing, and analysis" plus "tracked changes, comments, formatting preservation, and text extraction" and enumerated tasks (1)-(4) — matching the anchor for several specific concrete actions.

3 / 3

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)...(4)...").

3 / 3

Trigger Term Quality

Includes natural terms like ".docx files", "documents", "tracked changes", and "comments", but omits the most common user phrasing ("Word document"/"Word file"/.doc), so it has relevant keywords missing common variations.

2 / 3

Distinctiveness Conflict Risk

The ".docx files" / "professional documents" niche with task-specific triggers is clearly distinct from PDF, spreadsheet, or presentation skills and unlikely to trigger the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.