docx

Create, read, edit, template, and review Word .docx files.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%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 an exemplar of a bundled-tool skill: dense, executable, with a sequenced procedure and explicit verification checkpoints, and it appropriately offloads implementation detail to the scripts and one reference file. No substantive weaknesses found.

Dimension	Reasoning	Score
Conciseness	The body is lean reference-style prose with no padding about what a .docx is or how python-docx works; every section (Quick Reference, Procedure, Pitfalls, Verification) earns its tokens by covering non-obvious edge cases.	5 / 5
Actionability	Copy-paste-ready bash invocations and a full Quick Reference table give executable commands for every common case, matching the fully-executable anchor.	5 / 5
Workflow Clarity	A numbered 7-step Procedure ends with an explicit "Verify (always)" checkpoint, backed by a dedicated Verification section with per-operation checklists, satisfying the destructive/batch validation requirement rather than being capped at 3.	5 / 5
Progressive Disclosure	SKILL.md is a clear overview; deep spec format is deferred to scripts/docx_create.py and revision edge cases to references/revisions-and-comments.md (both verified to exist), giving well-signaled one-level-deep navigation.	5 / 5
	Total	20 / 20 Passed

Description

75%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 and clearly niched, but lacks an explicit trigger/"Use when" clause, which limits its completeness and leaves some natural user phrasings uncovered. Adding when-to-use guidance and a synonym like "Word documents" would raise it.

Suggestions

Append a "Use when..." clause naming concrete triggers (e.g., "Use when the user asks to generate, fill, or review a Word document or .docx file").

Add the synonym "Word document(s)" so the description matches how users naturally phrase requests.

Clarify the generic verb "review" (e.g., "review tracked changes and comments") to make every listed action concrete.

Dimension	Reasoning	Score
Specificity	"Create, read, edit, template, and review Word .docx files" lists five distinct concrete actions covering the full document lifecycle on a named domain, matching the comprehensive-coverage anchor.	5 / 5
Completeness	The "what" is clear (create/read/edit/template/review), but there is no explicit "Use when..." trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms "Word", ".docx", and "files" are present, but common synonyms like "Word document(s)" are missing, so it sits just below the comprehensive-synonym anchor at 5.	4 / 5
Distinctiveness Conflict Risk	"Word .docx files" carves a clear niche distinct from the related pdf/xlsx/powerpoint skills, with minimal conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/productivity/docx/SKILL.md
Commit: 6680afb

Reviewed: about 3 hours 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.