docx

Document toolkit (.docx). Create/edit documents, tracked changes, comments, formatting preservation, text extraction, for professional document processing.

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/document-skills/docx/SKILL.md

Quality

Content

63%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 actionable commands and a sequenced redlining workflow including verification, but it carries a tangential schematics section and its progressive-disclosure references point to files that are absent from the provided bundle. Aligning references to the real bundle and trimming cross-promotion would materially improve it.

Suggestions

Resolve the reference mismatch: either add the referenced docx-js.md / ooxml.md / ooxml/scripts/* files to the bundle or re-point the workflows at the existing scripts/document.py and scripts/templates/*.xml.

Remove or drastically shorten the 'Visual Enhancement with Scientific Schematics' section and the broken scripts/generate_schematic.py reference, which pad the skill with another skill's concerns.

De-duplicate the redlining batch-organization lists (the grouping suggestions appear twice) and add an explicit XML validation checkpoint before the pack step.

Dimension	Reasoning	Score
Conciseness	Core workflows are efficiently written with concrete commands, but the ~30-line 'Visual Enhancement with Scientific Schematics' section cross-promotes another skill and the redlining section duplicates its batch-grouping suggestions twice, adding padding.	3 / 5
Actionability	Provides copy-paste-ready pandoc, unpack/pack, soffice, and pdftoppm commands plus a concrete GOOD/BAD tracked-changes XML example, but several referenced scripts (generate_schematic.py) and files do not exist in the bundle.	4 / 5
Workflow Clarity	The redlining workflow is a clear 6-step sequence with a final verification step (pandoc re-conversion + grep checks) and a 'grep before scripting' checkpoint, though it lacks an explicit XML validation gate before packing.	4 / 5
Progressive Disclosure	Section headers are clear and references to docx-js.md/ooxml.md are one level deep, but those referenced files and the ooxml/scripts/* paths do not exist in the actual bundle, while the real bundle files (scripts/document.py, scripts/templates/*.xml) are not referenced from the body.	3 / 5
	Total	14 / 20 Passed

Description

71%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 distinguishes the skill well via the .docx niche, but it lacks an explicit 'Use when...' trigger clause, leaving the activation guidance only weakly implied. Adding concrete trigger phrases would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when working with .docx files, Word documents, tracked changes, comments, or document redlining.'

Include the natural synonym 'Word' / 'Word documents' alongside '.docx' to improve trigger-term coverage.

Lead with the action verbs in third person and keep the trailing 'for professional document processing' only if it adds a real trigger; otherwise replace it with concrete use-cases.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create/edit documents, tracked changes, comments, formatting preservation, text extraction' — giving comprehensive coverage of the toolkit's capabilities.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no explicit 'Use when...' trigger clause — 'for professional document processing' only weakly implies when, capping completeness per the missing-trigger guidance.	3 / 5
Trigger Term Quality	Includes natural terms like '.docx', 'documents', 'tracked changes', 'comments', and 'text extraction', but omits the common synonym 'Word' that users would naturally say.	4 / 5
Distinctiveness Conflict Risk	The '.docx' niche and tracked-changes/comments focus make it mostly distinct from PDF or generic document skills, with only minor overlap risk against a generic document skill.	4 / 5
	Total	16 / 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
relative_links	Relative link issues: 3 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/document-skills/docx/SKILL.md
Commit: d5ae560

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.