CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docx

Create, inspect, edit, validate, and visually verify Microsoft Word .docx documents, including templates, comments, tracked revisions, tables, images, headers, and footers.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

Well-structured, token-efficient content with concrete commands, a sensible validated workflow, and proper use of one-level-deep bundle references. Minor improvements would be an example spec/edit JSON and an explicit validate-fix-retry loop for the document editing path.

DimensionReasoningScore

Conciseness

The ~52-line body is lean and entirely operational — install command, helper list, four invocation examples, workflow, and safety rules — with no explanations of concepts Claude already knows and nothing that could be trimmed without loss.

5 / 5

Actionability

Provides concrete copy-paste commands (e.g. 'python3 <baseDirectory>/scripts/docx_read.py input.docx --json') plus a --help fallback, but the JSON spec formats for docx_create.py and docx_edit.py are not shown, leaving the two most common authoring tasks without inline examples.

4 / 5

Workflow Clarity

A clear 6-step sequence with an explicit validation checkpoint ('Run docx_validate.py') and a fallback when LibreOffice is unavailable, but for document manipulation there is no explicit fix-and-re-validate feedback loop, which the 5 anchor requires.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview; the single reference (references/revisions-and-comments.md, verified to exist) is clearly signaled, one level deep, and loaded only when needed ('read ... before editing them'), with helper scripts organized in a Helpers section — matching the actual bundle structure.

5 / 5

Total

18

/

20

Passed

Description

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

A strong, highly specific description that names concrete actions and a well-scoped .docx niche. Its main weakness is the missing 'Use when...' trigger clause, which limits discoverability and caps completeness, and a few natural synonyms (e.g., 'Word files') are absent.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions .docx files, Word documents, tracked changes, or document templates.'

Include natural synonym phrasings users actually say, such as 'Word files' or 'Word documents', alongside '.docx'.

Optionally mention reading/writing .docx as separate trigger scenarios (creating a new report vs. editing an existing contract) to sharpen the 'when' guidance.

DimensionReasoningScore

Specificity

Lists five concrete actions ("Create, inspect, edit, validate, and visually verify") plus eight specific object types ("templates, comments, tracked revisions, tables, images, headers, and footers"), giving comprehensive capability coverage with no obvious gaps.

5 / 5

Completeness

The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage including "Microsoft Word .docx documents", "tracked revisions", "templates", and "comments", but common user phrasings like "Word files" or "Word documents" as standalone synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear single-format niche (.docx) with distinct triggers (Word, tracked revisions, comments), so conflict risk with other skills is minimal; it does not straddle multiple formats like the score-4 anchor example.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

EKKOLearnAI/hermes-studio

Path

packages/ekko-agent/skills/docx/SKILL.md

Reviewed

Table of Contents

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.