docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

1.52x

Quality

94%

Does it follow best practices?

Impact

93%

1.52x

Average score across 8 eval scenarios

Securityby

Passed

No findings from the security scan

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

Quality

Content

88%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 high-quality, actionable skill body with strong workflows and validation feedback loops. Main improvement opportunity is splitting the large inline reference material into referenced sub-files to reduce the top-level token load.

Suggestions

Move the detailed 'XML Reference' patterns and the per-feature docx-js snippets (Tables, Hyperlinks, Footnotes, Tab Stops, Multi-Column) into referenced sub-files (e.g., references/xml-reference.md, references/docx-js-patterns.md), keeping SKILL.md as an overview with one-level-deep links.

Consolidate the 'Critical Rules for docx-js' summary list with the inline CRITICAL comments to avoid stating each rule twice; reference a single checklist instead.

Trim the page-size DXA derivation commentary where it restates unit conversions already shown in the table.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence, but the 'Critical Rules for docx-js' section repeats inline CRITICAL warnings already stated in each subsection, adding some redundancy.	4 / 5
Actionability	Fully executable, copy-paste-ready code and commands throughout — concrete docx-js snippets, exact DXA values, and real script invocations cover the common cases.	5 / 5
Workflow Clarity	Editing workflow is explicitly sequenced (Unpack → Edit XML → Pack) with a validation checkpoint, auto-repair feedback, and a create-then-validate loop for new documents, satisfying the destructive-operation requirement.	5 / 5
Progressive Disclosure	Well-organized with clear section headers and bundled executable scripts, but the XML Reference and docx-js API details are largely inlined in one ~590-line file rather than split into one-level-deep referenced sub-files.	4 / 5
	Total	18 / 20 Passed

Description

100%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.

An exemplary description: specific, comprehensive, with explicit trigger guidance and clear boundary exclusions. Third-person voice is maintained throughout with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'create, read, edit, or manipulate Word documents', 'inserting or replacing images', 'performing find-and-replace', 'working with tracked changes or comments', 'converting content into a polished Word document' — with comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('create, read, edit, or manipulate Word documents') and when ('Use this skill whenever the user wants... Triggers include:...') with concrete trigger phrases and a clear negative-boundary clause.	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms and extensions: 'Word doc', 'word document', '.docx', plus deliverable nouns 'report', 'memo', 'letter', 'template'.	5 / 5
Distinctiveness Conflict Risk	Clear .docx niche with explicit exclusions ('Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks'), minimizing overlap with adjacent skills.	5 / 5
	Total	20 / 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
skill_md_line_count	SKILL.md is long (591 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 7 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: tsinghua-fib-lab/AgentSociety
Path: extension/skills/docx/SKILL.md
Commit: 13e28b5

Reviewed: 1 day 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.