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

88

1.28x
Quality

81%

Does it follow best practices?

Impact

100%

1.28x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

This is a well-structured, highly actionable skill that effectively serves as a routing document for complex DOCX operations. Its main strengths are the clear decision tree, detailed redlining workflow with validation steps, and good progressive disclosure to supporting files. The primary weakness is the Chinese-language agent/MCP section at the top which adds token overhead for optional tooling recommendations and the minor verbosity in explaining basic concepts.

Suggestions

Remove or significantly condense the '智能体与 MCP 增强' section — it's optional tooling context that consumes significant tokens and mixes languages, making it harder to parse. If needed, move it to a separate AGENTS.md reference.

Remove the sentence explaining what a .docx file is ('A .docx file is essentially a ZIP archive containing XML files...') — Claude already knows this.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary content. The Chinese-language agent/MCP section at the top adds significant tokens for what amounts to optional tooling recommendations rather than core skill instructions. The overview explaining what a .docx file is ('essentially a ZIP archive containing XML files') is mildly redundant for Claude. However, the core workflows are reasonably lean.

2 / 3

Actionability

The skill provides concrete, executable commands throughout: specific pandoc commands with flags, python script invocations with exact arguments, bash commands for conversion, and detailed XML examples showing good vs bad tracked change patterns. The redlining workflow includes specific grep verification commands and the code examples are copy-paste ready.

3 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with numbered steps and explicit validation checkpoints. The redlining workflow includes a final verification step with specific grep commands to confirm changes. The decision tree at the top clearly routes users to the right workflow. Batching strategy with explicit size guidance (3-10 changes) and the 'grep before writing script' checkpoint demonstrate strong feedback loops.

3 / 3

Progressive Disclosure

The skill serves as a clear overview/router that points to detailed reference files (docx-js.md, ooxml.md, AGENTS.md) with one-level-deep references. Each workflow section tells you exactly which file to read and why. Content is well-organized into distinct sections by task type, and the decision tree at the top helps navigate to the right section quickly.

3 / 3

Total

11

/

12

Passed

Description

77%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid description that clearly communicates capabilities and usage triggers with a well-structured numbered list of scenarios. Its main weaknesses are the absence of 'Word' and 'Microsoft Word' as trigger terms—the most natural way users refer to .docx files—and some risk of overlap with other document-handling skills due to generic phrasing around 'documents'.

Suggestions

Add 'Word', 'Microsoft Word', and '.doc' as trigger terms since users most naturally refer to these files by the application name rather than the extension.

Strengthen distinctiveness by explicitly contrasting with other document types, e.g., 'Use when working with Word documents (.docx), not PDFs or plain text files.'

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: document creation, editing, analysis, tracked changes, comments, formatting preservation, and text extraction. These are concrete, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (document creation, editing, analysis, tracked changes, comments, formatting preservation, text extraction) and 'when' with explicit triggers ('When Claude needs to work with professional documents (.docx files) for:' followed by numbered scenarios).

3 / 3

Trigger Term Quality

Includes '.docx files', 'documents', 'tracked changes', 'comments', but misses common user variations like 'Word', 'Microsoft Word', '.doc', 'Word document'. Users most naturally say 'Word file' or 'Word document' rather than '.docx files'.

2 / 3

Distinctiveness Conflict Risk

The term 'documents' is quite broad and could overlap with PDF skills, text file skills, or general document handling. While '.docx' narrows it, phrases like 'document creation' and 'editing content' are generic enough to potentially conflict with other document-related skills. Missing 'Word' as a distinguishing keyword weakens distinctiveness.

2 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
majiayu000/claude-skill-registry
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.