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.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

90%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 strong, highly actionable skill body with executable examples and an exemplary validate-fix-repack workflow for fragile XML editing. Slight redundancy in the table-width guidance and some inlined reference material keep it just short of perfect conciseness and progressive disclosure.

Suggestions

Consolidate the table-width rules (Tables block, width-calculation block, 'Width rules' list, and 'Critical Rules for docx-js') into one authoritative location to reduce repetition.

Move the detailed XML Reference (tracked changes, comments, images XML) into a separate references file and link to it from SKILL.md to improve progressive disclosure.

Add explicit links to the scripts/templates/ files (e.g. comments.xml, people.xml) from the relevant body sections so their role is discoverable.

Dimension	Reasoning	Score
Conciseness	Largely lean and dense with code-first sections and minimal conceptual padding; a few sections repeat guidance (e.g. the dual-width table rule appears in the Tables block, the width-calculation block, the 'Width rules' list, and again in 'Critical Rules') which is slightly more than needed.	4 / 5
Actionability	Every section provides copy-paste-ready, executable JavaScript/bash/XML with concrete values (DXA numbers, entity tables, exact script invocations) and explicit call-outs of required parameters, covering the common creation and editing cases.	5 / 5
Workflow Clarity	The editing flow is explicitly sequenced as Step 1/2/3, creation has a Validation step with an unpack-fix-repack feedback loop, and pack.py documents auto-repair behavior plus what it will and won't fix — a textbook validate→fix→retry loop for fragile XML operations.	5 / 5
Progressive Disclosure	Well-organized with clear sections and real bundle scripts (office/unpack.py, pack.py, validate.py, comment.py, accept_changes.py, templates/) referenced at one level deep; however detailed XML reference and docx-js patterns are inlined in SKILL.md rather than split into reference files, and template files (e.g. comments*.xml) are not explicitly linked from the body.	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 excellent description: specific, comprehensive in trigger terms, explicit about both what and when, and clearly distinguished from neighboring skills with explicit negative-scope guidance. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'create, read, edit, or manipulate', 'inserting or replacing images', 'performing find-and-replace', 'working with tracked changes or comments', 'converting content into a polished Word document' — covering the domain comprehensively.	5 / 5
Completeness	Explicitly answers both what (create/read/edit/manipulate .docx) and when (explicit 'Use this skill whenever...' and 'Also use when...' trigger clauses with concrete trigger phrases), plus a negative-scope 'Do NOT use for...' clause.	5 / 5
Trigger Term Quality	Comprehensive natural keyword coverage including 'Word doc', 'word document', '.docx', 'report', 'memo', 'letter', 'template', plus synonyms and the file extension, all phrased as things users would actually say.	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to Word/.docx with explicit exclusion of PDFs, spreadsheets, Google Docs, and general coding, giving it a clear niche with minimal conflict risk against adjacent document skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 7 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: eigent-ai/eigent
Path: resources/example-skills/docx/SKILL.md
Commit: d308955

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.