docx

Create/edit/inspect Word documents using available managed or host capabilities.

Quality

61%

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 ./crates/tui/assets/skills/docx/SKILL.md

Quality

Content

65%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 exceptionally lean and well-structured for a simple skill, but its workflow gives only high-level hints with no executable code and lacks a feedback loop for the document-editing operations it describes.

Suggestions

Add a concrete code or command example for the core create/edit/inspect operation using python-docx or pandoc so the guidance is executable.

Turn step 4 into an explicit validation feedback loop (verify → if text is wrong, fix and re-verify) to satisfy the document-manipulation feedback-loop requirement.

Specify how to "preserve originals" (e.g. copy to a backup path) so that policy step is actionable rather than aspirational.

Dimension	Reasoning	Score
Conciseness	The body is roughly ten lean lines with no over-explanation of what a docx is or how libraries work; every section (When to use, Compatibility, Workflow) earns its place, matching the anchor-5 example of lean, competence-assuming content.	5 / 5
Actionability	The workflow names tools ("Use python-docx/pandoc when available") but provides no executable code or commands, and steps like "Verify by reopening and extracting representative text" are high-level hints missing the specific steps to execute; matches anchor 2 rather than 3, which requires at least pseudocode or partial executable guidance.	2 / 5
Workflow Clarity	Four steps are clearly sequenced and step 4 is a verify checkpoint, but for document manipulation the rubric requires a validate→fix→retry feedback loop, whose absence caps workflow_clarity at 3; not 2 because the sequence and a checkpoint are present.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files and no need for external references, and its sections are well-organized, so the simple-skill exception lets progressive disclosure score 5 on well-organized sections alone.	5 / 5
	Total	15 / 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 cleanly states what the skill does with three concrete actions and a distinct Word niche, but it lacks any "when to use" trigger guidance and misses the .docx extension as a natural keyword.

Suggestions

Add a "Use when…" clause naming natural triggers, e.g. "Use when working with .docx or Word-style documents (memos, reports, letters, templates)."

Include the ".docx" file extension and "Word files" synonym to improve trigger-term coverage.

Drop or sharpen "using available managed or host capabilities," which reads as vague jargon rather than a concrete capability.

Dimension	Reasoning	Score
Specificity	"Create/edit/inspect Word documents" names the domain plus three concrete actions; falls at anchor 4 (several specific actions, minor gaps) rather than 5 because "using available managed or host capabilities" is vague and coverage is not comprehensive, and above 3 because more than 1-2 actions are listed.	4 / 5
Completeness	The "what" is clear (create/edit/inspect Word documents) but there is no "Use when…" clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3; not 2 because the "what" is concrete rather than vague.	3 / 5
Trigger Term Quality	"Word documents" is one relevant natural keyword, but the description omits common variations/synonyms such as ".docx", "Word files", or the file extension; matches anchor 3 (some relevant keywords but missing common variations) rather than 4 which expects broader coverage.	3 / 5
Distinctiveness Conflict Risk	"Word documents" carves a mostly distinct niche with only minor overlap risk against general document or PDF skills, matching anchor 4; not 5 because no explicit trigger phrase is given, and not 3 because the Word-specific scope is clearer than merely "works with document files".	4 / 5
	Total	14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Hmbown/CodeWhale
Path: crates/tui/assets/skills/docx/SKILL.md
Commit: cd986b3

Reviewed: ~16 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.