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

91

1.28x
Quality

83%

Does it follow best practices?

Impact

100%

1.28x

Average score across 5 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

71%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 content is well-structured with a routing decision tree, executable tooling commands, and validation checkpoints in the redlining workflow. Its main weaknesses are duplicated batch-grouping prose, deferred core-edit code, a validation gap in the basic editing path, and references to detailed files (docx-js.md, ooxml.md) that are absent from the bundle.

Suggestions

Add the missing referenced files (docx-js.md and ooxml.md) to the bundle, or inline their essential content so the 'MANDATORY - READ ENTIRE FILE' instructions resolve to real files.

Deduplicate the batch-organization guidance: lines 109-113 and 125-128 cover the same by-section/by-type/by-proximity groupings — keep one canonical list and reference it.

Add a validation checkpoint to the basic 'Editing existing document' workflow (e.g., run a verify/validate script or a pandoc round-trip diff before final pack) to match the redlining path's rigor.

DimensionReasoningScore

Conciseness

The body is largely lean with executable commands and no concept-explanation padding, but the batch-grouping guidance is duplicated (lines 109-113 vs 125-128) and the 'MANDATORY - READ ENTIRE FILE' directive is repeated three times, both of which could be trimmed.

4 / 5

Actionability

Tooling commands (pandoc, soffice, pdftoppm, unpack/pack scripts) and the OOXML redlining code example are concrete and executable, but the central editing operation defers its code to the external ooxml.md reference ('use get_node', 'see ooxml.md') rather than providing inline executable code.

4 / 5

Workflow Clarity

A top-level decision tree routes to clear sequenced workflows, and the redlining workflow has explicit checkpoints (per-batch testing, final grep verification); the minor gap is that the basic 'Editing existing document' path (unpack -> script -> pack) lacks any validation step.

4 / 5

Progressive Disclosure

References to detailed subfiles (docx-js.md, ooxml.md) are clearly signaled and one level deep, but neither file nor an ooxml/ directory exists in the actual bundle, so the prominently-signaled 'READ ENTIRE FILE' references point to missing files and runtime navigation fails.

3 / 5

Total

15

/

20

Passed

Description

96%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 is specific, complete, and trigger-rich with an explicit 'When Claude needs to...' clause and natural .docx trigger terms, paralleling the rubric's exemplary presentation-skill example. Its only weakness is the somewhat broad 'professional documents' lead-in, which slightly raises conflict risk versus a fully pinned niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('document creation, editing, and analysis', 'tracked changes, comments, formatting preservation, and text extraction') with comprehensive coverage, matching the anchor-5 example of multiple specific concrete actions.

5 / 5

Completeness

Explicitly answers both 'what' (creation, editing, analysis with tracked changes/comments/formatting/extraction) and 'when' ('When Claude needs to work with professional documents (.docx files) for: (1)...(4)...'), matching the anchor-5 what-and-when example.

5 / 5

Trigger Term Quality

Includes natural trigger phrases plus the file extension ('professional documents (.docx files)', 'Creating new documents', 'tracked changes', 'Adding comments'), closely paralleling the exemplary pptx good example in the rubric; only minor synonym breadth (e.g., 'Word documents') is absent.

5 / 5

Distinctiveness Conflict Risk

The '.docx files' extension pins a clear niche with distinct enumerated triggers, but the leading 'professional documents' phrasing is slightly broader than the anchor-5 PDF-pinned example, leaving minor overlap risk with generic document skills.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
einverne/dotfiles
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.