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

94%

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

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.

The body is highly actionable with executable code and a clearly sequenced, validated editing workflow, well-organized into navigable sections with real bundle references. It is slightly held back by some inline redundancy and a broken symlink in the office script bundle.

Suggestions

Consolidate the duplicated table-width guidance: state the DXA rules once in the Tables section and remove the repeated bullets from the Critical Rules list (or vice versa) to tighten conciseness.

Fix the broken 'scripts/office' symlink (target ../../_shared/office does not resolve) so referenced scripts like unpack.py, pack.py, and validate.py are actually available to the skill.

Consider moving the bulk of the XML Reference (tracked-changes/comment/image patterns) into a separate reference file with a one-line pointer, leaving SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	Mostly lean and code-forward with minimal concept explanation, but a few sections repeat guidance already stated inline (e.g., table width rules appear in both the code block and the Critical Rules list), keeping it just below the fully efficient anchor.	4 / 5
Actionability	Provides copy-paste-ready, executable code and commands for every common case (tables, images, lists, footnotes, hyperlinks, tracked-changes XML, comments) with specific flags and unit values, matching the fully executable anchor.	5 / 5
Workflow Clarity	The editing workflow is an explicit 3-step sequence (unpack → edit XML → pack) with a validation checkpoint (validate.py), documented auto-repair behavior, and error-recovery guidance, satisfying the destructive-operation feedback-loop requirement.	5 / 5
Progressive Disclosure	The body is a well-organized overview with one-level-deep references to real bundle scripts (unpack.py, pack.py, validate.py, comment.py, accept_changes.py), though a sizable XML reference is inlined and the 'office' bundle entry is a broken symlink, leaving minor organization gaps.	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.

The description is a strong, comprehensive trigger specification that clearly states capabilities, natural trigger terms, explicit when-to-use guidance, and boundary exclusions. No meaningful gaps relative to the anchors.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'create, read, edit, or manipulate Word documents', tracked changes, comments, find-and-replace, inserting images, TOC/headings/page numbers/letterheads, and conversion — covering the domain comprehensively.	5 / 5
Completeness	Explicitly answers both what (create/read/edit/manipulate .docx) and when via 'Use this skill whenever...' plus 'Triggers include:' and explicit 'Do NOT use for...' boundary guidance.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('Word doc', 'word document', '.docx', 'report', 'memo', 'letter', 'template') plus synonyms and the file extension, matching the comprehensive anchor.	5 / 5
Distinctiveness Conflict Risk	Carves a clear .docx niche and explicitly excludes PDFs, spreadsheets, Google Docs, and general coding, 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: 4 missing, 4 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: nextlevelbuilder/goclaw
Path: skills/docx/SKILL.md
Commit: 169e0ba

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.