CtrlK
BlogDocsLog inGet started
Tessl Logo

docx-skill

All-in-one Word document (.docx) read / write / convert / review. Trigger scenarios: summarize a docx, read paragraphs / outline / tables / images / comments / tracked changes, replace body text, insert images, change page settings, rebuild table of contents, add comments or replies, add tracked changes (insert/delete/replace), accept/reject revisions, convert docx ↔ pdf/html/md/txt. Typical phrasings: "summarize this Word doc", "change the second paragraph to XXX", "replace all 'Company A' with 'Company B'", "add a tracked change comment", "accept all revisions", "convert docx to pdf", "generate a sales report from these bullet points". Load this skill whenever the user mentions a .docx / .doc file or targets a Word document as the deliverable.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

83%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 lean, executable, and well-structured with strong code demos and a useful pitfalls table. Its main gap is the absence of explicit validation/feedback loops for the destructive XML-editing paths, which caps workflow clarity.

Suggestions

Add an explicit validation step after §2.2 and §2.4 XML edits (e.g. 'Verify the output opens cleanly / run WordInspect(render) before finalizing') to establish a validate→fix→retry loop and lift workflow clarity.

Reconcile §2.4 (hand-editing document.xml via adm-zip) with the §4 pitfall that hand-edited OOXML triggers Word's 'document repaired' warning — either wrap it with a validation check or route tracked-change acceptance through the docx package where possible.

Consider extracting the four code demos or the pitfalls table into a references/ file so the SKILL.md overview stays lighter, enabling a cleaner one-level-deep reference structure.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding: assumes Claude knows what docx/libraries are and lets executable code blocks, a tool table, and a pitfalls table earn their tokens.

5 / 5

Actionability

Four complete copy-paste-ready code demos (meeting-notes generation, find-replace, image+header, accept-tracked-changes) plus concrete WordInspect/DocConvert invocations covering the common cases.

5 / 5

Workflow Clarity

The read branch table sequences next steps by signal, but destructive XML-editing operations (§2.2, §2.4) and output writing lack an explicit validate→fix→retry feedback loop; the feedback-loops note caps workflow_clarity at 3 for XML/document manipulation.

3 / 5

Progressive Disclosure

Well-organized single-file skill with clear Read/Write/Convert/Pitfalls sections and a tool table; no bundle files exist to split content into, so it is appropriately self-contained, with only minor room for a separate API-reference file.

4 / 5

Total

17

/

20

Passed

Description

100%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 exemplary: third-person voice, concrete capabilities, natural trigger phrasings, and an explicit load-this-skill clause covering both what and when. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (read paragraphs/outline/tables/images/comments/tracked changes, replace body text, insert images, rebuild TOC, accept/reject revisions, convert docx↔pdf/html/md/txt) for comprehensive coverage, matching the score-5 anchor.

5 / 5

Completeness

Explicitly states both the 'what' (read/write/convert/review with enumerated capabilities) and the 'when' ('Load this skill whenever the user mentions a .docx / .doc file or targets a Word document as the deliverable').

5 / 5

Trigger Term Quality

Provides natural phrasings users would say ('summarize this Word doc', 'convert docx to pdf'), file extensions (.docx/.doc), and synonyms (Word/docx), matching the comprehensive coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Word/.docx) with explicit file-extension triggers, minimal overlap risk with PDF/Excel/presentation skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
itsablabla/openloaf-web
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.