docx

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

Quality

56%

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

47%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.

This is a clean, well-structured catalogue entry that advertises an upstream skill and points to its source. However, as standalone skill content it offers little executable guidance — the install step is unspecified and the only command opens a URL — so actionability and workflow clarity are weak.

Suggestions

Replace the vague 'install the upstream bundle into your active agent's skills directory' with concrete copy-paste commands (e.g., git clone path and the target skills directory).

Add a brief verification step confirming the skill is installed and invokable (e.g., 'Then ask the agent to invoke `docx` and confirm it loads').

Drop the verbatim repeat of the description in 'What it does' or replace it with a value-adding summary to tighten token use.

Dimension	Reasoning	Score
Conciseness	The body is lean and well under the token budget, though the 'What it does' section repeats the frontmatter description verbatim and the inline comment '# Inspect the upstream README for exact paths' is mild padding.	4 / 5
Actionability	Guidance is high-level: it tells the reader to 'install the upstream bundle into your active agent's skills directory' without steps, and the only concrete command is `open <url>`, which merely opens a browser rather than executing the skill.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream README -> install bundle -> invoke by name/trigger), but the steps are poorly defined with no detail on how to install or verify, and validation is absent.	2 / 5
Progressive Disclosure	The body is short, well-organized into clearly labeled sections (What it does, Source, How to use), and points to a single one-level-deep upstream reference with no nested bundling; minor gap is that the reference is an external repo URL rather than local bundle files.	4 / 5
	Total	12 / 20 Passed

Description

66%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 distinct, clearly naming the Word-document domain and several concrete capabilities alongside reasonable use-case triggers. Its main weakness is the 'when' guidance, which is framed as deliverable types rather than an explicit 'Use when...' trigger clause, capping completeness.

Suggestions

Add an explicit 'Use when...' clause naming trigger conditions (e.g., 'Use when working with .docx files, tracked changes, or review-ready Word deliverables') to lift completeness.

Include the '.docx' file extension and the term 'docx' in the description to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Word documents') and several concrete actions/elements ('create, edit, and analyze', 'tracked changes, comments, and formatting'), but the verbs remain somewhat generic for document work, leaving minor coverage gaps.	4 / 5
Completeness	Provides a clear 'what' (create/edit/analyze Word docs) and a 'when' framed as 'Useful for design briefs, copy docs, and review-ready deliverables', but the 'when' is deliverable-oriented rather than an explicit 'Use when...' trigger clause, so per the cap guidance it stays at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Word documents', 'tracked changes', 'design briefs', 'copy docs'), but omits the file extension '.docx' and the term 'docx' itself, so a few natural variations are missing.	4 / 5
Distinctiveness Conflict Risk	'Word documents' is a clear, narrow niche with low conflict risk against other skills, though terms like 'design briefs' could lightly overlap with general document or design skills.	4 / 5
	Total	15 / 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: nexu-io/open-design
Path: skills/docx/SKILL.md
Commit: 1a7a23d

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