docx

Create, edit, and analyze Word documents with tracked changes, comments, and formatting. Useful for design briefs, copy docs, and review-ready deliverables.

Quality

70%

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%

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 clean, concise catalogue stub that defers all real capability to the upstream repo, so it is well-organized and token-efficient but offers no executable or actionable guidance for the skill's stated task.

Suggestions

Add at least one concrete, copy-paste-ready example or command that performs an actual docx task (e.g., a snippet for applying tracked changes or unpacking/editing word/document.xml) instead of only linking out.

Replace the generic "install the upstream bundle" direction with explicit, sequenced install steps and a verification checkpoint confirming the skill is available.

Provide a short in-SKILL quick-start so the skill is usable without first fetching the upstream README.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence; it does not explain what Word documents or tracked changes are, and every section is short and purposeful.	3 / 3
Actionability	The only concrete command is `open <github-url>`, which sends the reader elsewhere; the body describes how to install the upstream bundle rather than providing executable guidance for creating, editing, or analyzing Word documents.	1 / 3
Workflow Clarity	A loose install sequence is present (inspect README, install bundle, invoke by name/trigger), but it is a meta-install workflow for the skill itself with no validation checkpoints and no workflow for the actual docx task.	2 / 3
Progressive Disclosure	For an under-50-line pointer skill, the body is well-organized into clear sections (What it does, Source, How to use) with a single, clearly signaled one-level reference to the upstream bundle.	3 / 3
	Total	9 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, specific description with strong action verbs and good natural trigger terms, but it lacks an explicit "Use when..." trigger clause, leaving the activation conditions implied rather than stated.

Suggestions

Add an explicit "Use when..." clause naming triggering situations (e.g., "Use when the user asks to create or edit Word documents, track changes, or prepare review-ready copy docs").

Include the file extension term ".docx" in the description to strengthen trigger-term coverage.

Reframe the trailing "Useful for..." list as triggering contexts rather than only output deliverable types.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Create, edit, and analyze Word documents") plus concrete feature areas ("tracked changes, comments, and formatting"), matching the score-3 anchor that lists several specific actions.	3 / 3
Completeness	"What" is explicit, but the "when" is only a soft "Useful for design briefs, copy docs, and review-ready deliverables" listing deliverable types rather than an explicit "Use when..." trigger clause, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	The description surfaces natural terms a user would say ("Word documents", "tracked changes", "design briefs", "copy docs", "review-ready deliverables"), giving good coverage rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to Word/.docx with tracked changes, comments, and formatting, giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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: nexu-io/open-design
Path: skills/docx/SKILL.md
Commit: f2760fd

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