CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docx-official

A user may ask you to create, edit, or analyze the contents of a .docx file. A .docx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-documents-presentations/skills/docx-official/SKILL.md

The canonical home for this skill is docx-official in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

52%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 delivers a strong decision tree, concrete commands, and a well-sequenced redlining workflow with verification, but it is undermined by broken bundle navigation — every referenced file and script path (ooxml.md, docx-js.md, ooxml/scripts/unpack.py and pack.py) is absent, and the actual bundled scripts are never surfaced. Moderate redundancy (duplicated overview, repeated batching guidance, a filler 'When to Use' section) also costs tokens without adding guidance.

Suggestions

Fix progressive disclosure first: either add the missing ooxml.md, docx-js.md, and ooxml/scripts/unpack.py & pack.py files, or rewrite the references to point at the actual bundle (e.g. scripts/document.py, scripts/utilities.py) so the mandatory "READ ENTIRE FILE" steps resolve.

Trim redundancy: drop the verbatim duplicate of the description in the Overview, merge the duplicated batching guidance (steps 2 and 4), and delete the empty "When to Use" section.

Close the feedback loop in the redlining workflow's final verification: state explicitly what to do when a grep check finds the original phrase or an unintended change (e.g. re-grep the batch, fix, re-pack, and re-verify).

DimensionReasoningScore

Conciseness

The body is mostly efficient commands, but it re-explains a concept Claude already knows ("A .docx file is essentially a ZIP archive containing XML files and other resources"), duplicates the frontmatter description verbatim in the Overview, repeats batching guidance twice ("Batch organization" in step 2 and "Suggested batch groupings" in step 4), and ends with a vacuous section ("This skill is applicable to execute the workflow or actions described in the overview."). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' (3); it is above 2 because the bulk is actionable commands, not padding.

3 / 5

Actionability

There is concrete, executable guidance (pandoc flags, soffice/pdftoppm commands, a GOOD/BAD OOXML tracked-changes example, dependency installs, grep-based verification), but the core workflows hinge on files that do not exist in the bundle: "Read [`ooxml.md`](ooxml.md)", "Read [`docx-js.md`](docx-js.md)", and "python ooxml/scripts/unpack.py" / "pack.py" are all missing, and the bundled scripts/document.py and scripts/utilities.py are never referenced. This lands at 3 ('some concrete guidance but incomplete; missing key details') rather than 4 because the primary editing/creation paths cannot actually be executed as written.

3 / 5

Workflow Clarity

A decision tree routes each task type, the redlining workflow is well sequenced with batching ("Test each batch before moving to the next"), a just-in-time checkpoint ("Always grep word/document.xml immediately before writing a script"), and an explicit final verification (pandoc conversion plus grep checks for original/replacement phrases and unintended changes). It falls short of 5 because the verification step has no explicit fix-and-retry loop if a check fails, and the create/edit workflows have no verification at all — 'clear sequence with most checkpoints present; minor validation gaps' (4).

4 / 5

Progressive Disclosure

Scored against the actual bundle: the body's references — docx-js.md, ooxml.md, ooxml/scripts/unpack.py, ooxml/scripts/pack.py — point to files that do not exist anywhere in the skill, while the real bundle contents (scripts/document.py, scripts/utilities.py, scripts/templates/) are never mentioned in SKILL.md. Navigation is therefore broken in both directions, matching the anchor for 2 ('minimal structure; references are buried/lead nowhere'); it is not 1 because the body itself is well sectioned and self-contained.

2 / 5

Total

12

/

20

Passed

Description

48%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 identifies the .docx domain and its three main verbs but is padded with a vague closing sentence, written in second person, and lacks an explicit 'Use when' trigger clause plus common synonyms like 'Word document'. It reads as a domain statement rather than a trigger-ready capability summary.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Word documents, .docx files, tracked changes, or redlining a contract", so the 'when' is answered directly.

Replace the vague closing sentence with concrete capabilities (e.g., "Extract text with pandoc, unpack and edit raw OOXML, create documents with docx-js, apply tracked changes, convert pages to images") and rewrite in third person.

Include natural synonyms — "Word document", "Word file", ".doc" — alongside ".docx" to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain and generic actions ("create, edit, or analyze the contents of a .docx file") but adds vague filler ("You have different tools and workflows available for different tasks"), matching the anchor 'names the domain but actions are minimal or generic' (3). However, it uses second-person voice ("that you can read or edit", "You have different tools"), which the judging guidelines penalize by reducing the specificity score by 1, yielding 2.

2 / 5

Completeness

The 'what' is clear (create, edit, or analyze .docx contents), but there is no "Use when..." clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by "A user may ask you to create, edit, or analyze", which the guidelines cap at 3. It is not a 2 because the what-half is concrete rather than vague.

3 / 5

Trigger Term Quality

".docx file" is a relevant, natural trigger, but the description misses the most common user phrasings — "Word document", "Word file", ".doc" — so keyword coverage has relevant terms yet lacks common variations and synonyms, matching the anchor for 3. It does not reach 4 because terms like "Word documents" or "tracked changes" that users would naturally say are absent.

3 / 5

Distinctiveness Conflict Risk

The skill is anchored to a specific file format (.docx), keeping it mostly distinct from PDF/xlsx/pptx skills, but it never mentions "Word documents" — the most common synonym — so a sibling Word-processing skill could overlap, matching the anchor 'mostly distinct; minor overlap risk' (4). It falls short of 5 because the trigger vocabulary is too thin to establish a fully distinct niche.

4 / 5

Total

12

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/antigravity-bundle-documents-presentations/skills/docx-official/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.