docx

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When GLM 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

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/docx/SKILL.md

Quality

Content

57%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 well-structured with clear decision-tree routing and mostly executable guidance, but it is held back by repeated python-docx examples and some over-explanation, plus missing validation checkpoints in the creating/editing workflows and referenced .md files not present in the bundle.

Suggestions

Collapse the three python-docx add_comment code blocks into one example plus a compact 'common patterns' list to cut repeated padding.

Add an explicit validation/verify step (e.g., pandoc re-conversion or a quick open check) to the 'Creating a new Word document' and 'Editing an existing Word document' workflows, mirroring the redlining workflow's final verification.

Either include docx-js.md and ooxml.md in the references/ bundle or note where they live, and consider moving the color-palette/design-requirements block into a separate styling reference file.

Dimension	Reasoning	Score
Conciseness	Mostly actionable, but padded in places — the python-docx comments section repeats the same add_comment example three times with full code, and 'A .docx file is essentially a ZIP archive...' explains a concept Claude already knows. Could be tightened significantly.	3 / 5
Actionability	Provides executable commands (pandoc, unpack/pack, add_toc_placeholders.py CLI) and complete python-docx snippets, but the core 'creating' workflow defers the actual docx-js code to an external docx-js.md file rather than showing it inline — a minor gap.	4 / 5
Workflow Clarity	Numbered workflows with unpack/pack steps are clearly sequenced and the redlining workflow has a final verification step, but the creating and basic-editing workflows lack validation checkpoints for destructive document operations, which caps clarity per the feedback-loop rule.	3 / 5
Progressive Disclosure	Structure uses one-level-deep references (docx-js.md, ooxml.md) and correctly points to real scripts, but the referenced .md files are absent from the provided bundle and the large inline color-palette/design section is content that could live in a separate styling reference.	3 / 5
	Total	13 / 20 Passed

Description

88%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 strong: it concisely states concrete capabilities and provides an explicit, numbered 'when to use' trigger list anchored on the .docx extension. It loses a point on trigger coverage (missing 'Word files/documents' synonyms) and a point on distinctiveness due to the somewhat broad 'professional documents' phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creation, editing, and analysis', 'tracked changes, comments, formatting preservation, and text extraction' — giving comprehensive coverage of docx capabilities rather than just naming the domain.	5 / 5
Completeness	Explicitly answers both 'what' (creation/editing/analysis with tracked changes, comments, formatting, text extraction) and 'when' via a numbered 'When GLM needs to work with professional documents (.docx files) for: (1)... (2)... (3)...' trigger list.	5 / 5
Trigger Term Quality	Includes the '.docx' extension and natural task phrases ('Creating new documents', 'Modifying or editing content', 'tracked changes', 'Adding comments'), but misses common synonyms like 'Word files' or 'Word documents' that users would also say.	4 / 5
Distinctiveness Conflict Risk	The '.docx' niche with specific triggers (tracked changes, comments) is mostly distinct from PDF/pptx skills, but the broad phrase 'professional documents' leaves minor overlap risk with general document skills.	4 / 5
	Total	18 / 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
relative_links	Relative link issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: jjyaoao/HelloAgents
Path: skills/docx/SKILL.md
Commit: 93e77ea

Reviewed: 5 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.