CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

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

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

A tight, high-signal skill body: correct routing across create/edit/read, precise gotchas, executable pipelines with built-in validation and repair loops, and a well-structured script bundle. The two minor gaps are the absence of any assembled creation example and small redundancies in the redlining/tracked-changes discussion.

Suggestions

Add a minimal complete docx-js 'hello world' script (page size, one heading, one styled paragraph) under the gotchas so the Create path is executable end-to-end like the edit path.

Dedupe the redlining --author guidance: keep it either in the pipeline code comment or the Tracked changes prose, not both, and tighten the accept_changes/pandoc empty-bullet discussion to one statement plus the two tool-specific bullets.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence ('The model knows the API; these are the footguns') with exact, non-obvious values (DXA 1440 = 1″, ShadingType.CLEAR vs SOLID, w:delText vs w:t), but has minor trimmable redundancy — e.g. the --author redlining validation is stated in the pipeline comment and restated in prose in the same section.

4 / 5

Actionability

The edit, verify, and comment workflows give copy-paste-ready bash with real script paths and flags, but the Create path — one of the three task types in the routing table — provides precise API gotchas without even a minimal assembled example script.

4 / 5

Workflow Clarity

Sequences are explicit with validation checkpoints and feedback loops: the edit pipeline embeds validate.py --original with --auto-repair for error recovery and an --author check that every edit is tracked, and created files get a render-to-PDF → rasterize → visually inspect verification loop.

5 / 5

Progressive Disclosure

A task→approach routing table up front, all referenced bundle files (scripts/office/soffice.py, scripts/office/validate.py, scripts/merge_runs.py, scripts/accept_changes.py, scripts/comment.py, scripts/templates/) exist one level deep, and implementation detail appropriately lives in the scripts rather than being inlined.

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete capabilities, natural trigger terms including extensions and synonyms, explicit when-guidance, and explicit exclusions. The only weakness is that one trigger clause about 'professional documents with formatting' is not tied to the Word format, creating slight overlap potential with non-Word document skills.

DimensionReasoningScore

Specificity

The description lists many concrete actions — 'create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files)', 'extracting or reorganizing content', 'inserting or replacing images', 'performing find-and-replace', 'working with tracked changes or comments', 'converting content into a polished Word document' — with comprehensive coverage of the domain.

5 / 5

Completeness

Both 'what' (the enumerated create/read/edit/manipulate/extract/convert actions) and 'when' ('Use this skill whenever…', 'Triggers include:…', 'Also use when…', 'If the user asks for a report…') are explicitly and concretely answered.

5 / 5

Trigger Term Quality

It covers natural user phrasing ('Word doc', 'word document', 'report', 'memo', 'letter', 'template'), file extensions ('.docx', '.dotx'), and task phrasings ('find-and-replace in Word files', 'tracked changes or comments'), plus explicit negative triggers ('Do NOT use for PDFs, spreadsheets, Google Docs').

5 / 5

Distinctiveness Conflict Risk

The .docx/.dotx niche is clear and the explicit 'Do NOT use for PDFs, spreadsheets, Google Docs' exclusion wards off the nearest neighbors, but the trigger 'requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads' is not Word-scoped, leaving minor overlap risk with e.g. PDF/typesetting deliverables.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

K-Dense-AI/claude-scientific-writer

Path

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.