docx

Inspect, edit, validate, and preview existing Word documents while preserving structure and unrelated content.

Quality

72%

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 ./resources/bundled-skills/docx/SKILL.md

Quality

Content

86%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 a tight, well-organized, instruction-only skill: exact tool routing, a hash-protected edit workflow, explicit completion gates, and clear boundaries. The only meaningful gaps are the missing error-recovery feedback loop and the undefined structured-operation format.

Dimension	Reasoning	Score
Conciseness	The ~30-line body has zero padding or explanation of concepts Claude already knows — every section (tool routing, workflow, gates, boundaries, delivery) is directly actionable, matching the "lean and efficient; every token earns its place" anchor.	5 / 5
Actionability	Concrete guidance names the exact tools (office_inspect, office_edit, office_preview) and the critical parameter (expectedSha256) in a clear sequence; gaps remain in that no invocation syntax is shown and "smallest structured operation batch" is left undefined, so it is mostly executable rather than fully so.	4 / 5
Workflow Clarity	The 5-step workflow is clearly sequenced with hash capture and a Completion gates section covering validation (valid DOCX package, confirm text/layout in preview), but there is no explicit validate-fix-retry feedback loop, which the scoring notes require for document manipulation to reach 5.	4 / 5
Progressive Disclosure	The skill has no bundle files and none are needed; under the guideline that skills under 50 lines with no external references can score 5 with well-organized sections, the clean section structure (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery) fully qualifies, and no referenced file paths are broken.	5 / 5
	Total	18 / 20 Passed

Description

58%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 states a clear, third-person "what" with four concrete actions and a differentiator (preserving structure and unrelated content), but it has no "when to use" guidance and lacks the most natural trigger terms (.docx, DOCX, Microsoft Word). Adding a Use-when clause with file-extension triggers would move it into the top tier.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. "Use when working with existing Word (.docx) files or when the user mentions Word documents, DOCX, or .docx files."

Include the natural trigger synonyms and file extensions — .docx, DOCX, Microsoft Word — since users most often refer to files by extension.

Optionally surface the hash-protected atomic editing as a capability differentiator to further distinguish this skill from generic document skills.

Dimension	Reasoning	Score
Specificity	"Inspect, edit, validate, and preview existing Word documents" lists four concrete actions in the Word domain, but coverage has minor gaps (no detail on text/table operations), matching the anchor for several specific actions rather than comprehensive coverage.	4 / 5
Completeness	The "what" is clear (inspect, edit, validate, preview with structure preservation), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; the "when" is at best weakly implied by "existing Word documents".	3 / 5
Trigger Term Quality	"Word documents" is a relevant keyword, but the description omits the most natural triggers users would say — ".docx", "DOCX", "doc file", "Microsoft Word" — matching the anchor for some relevant keywords with missing variations/synonyms rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	"existing Word documents" carves a niche distinct from PDF/spreadsheet skills, but the generic "documents" phrasing without .docx/DOCX triggers leaves minor overlap risk with other document-handling skills, matching the "mostly distinct; minor overlap risk" anchor rather than the minimal-conflict anchor.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: KunAgent/Kun
Path: resources/bundled-skills/docx/SKILL.md
Commit: ebce7f6

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.