docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", 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 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

90%

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

Quality

Content

81%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 highly actionable, well-sequenced skill body with executable code, validation checkpoints, and real one-level-deep script references. The main weakness is conciseness — significant restatement across sections and inlined API/XML reference material that could be split out.

Suggestions

Deduplicate the width/page-size guidance: the DXA rules appear in Page Size, Tables, Width rules, and Critical Rules — consolidate into one section and reference it.

Consider moving the full XML Reference (tracked changes, comments, images) and the docx-js API examples into separate reference files, keeping SKILL.md as a tighter overview with one-level-deep links.

Trim repeated CRITICAL callouts where the adjacent code example already demonstrates the rule, to reduce token cost without losing the warning.

Dimension	Reasoning	Score
Conciseness	Largely efficient code-heavy reference, but the body is long (~480 lines) with some redundancy — page-size/width rules are restated in multiple sections (Page Size, Tables, Critical Rules) and several CRITICAL callouts repeat inline guidance, so it could be tightened.	3 / 5
Actionability	Fully executable, copy-paste-ready code and commands throughout — concrete docx-js snippets, exact bash invocations, and complete XML patterns with specific values (DXA widths, entities, w:id usage), covering common cases comprehensively.	5 / 5
Workflow Clarity	Multi-step edit workflow is explicitly sequenced (Unpack → Edit XML → Pack) with a validation checkpoint, auto-repair details, and a feedback loop ('If validation fails, unpack, fix the XML, and repack'), plus a Critical Rules checklist for the creation path.	5 / 5
Progressive Disclosure	Good structure with section headers and real referenced bundle files (scripts/office/unpack.py, pack.py, validate.py, comment.py, templates/), all one level deep; however the XML reference and docx-js API details are largely inlined in SKILL.md rather than split out, leaving minor organization gaps.	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.

A strong, specific description with concrete actions, natural trigger synonyms, explicit when-guidance, and clear boundary exclusions. It comprehensively answers both what and when with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'create, read, edit, or manipulate', 'inserting or replacing images', 'find-and-replace', 'tracked changes or comments', 'converting content into a polished Word document' — with comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both what (create/read/edit/manipulate Word documents) and when (detailed 'Triggers include' clause plus 'Use when' and 'Do NOT use for' boundary), exceeding the concrete-trigger-phrases bar for a 5.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms and extensions: 'Word doc', 'word document', '.docx', plus deliverable nouns ('report', 'memo', 'letter', 'template'), matching the top anchor.	5 / 5
Distinctiveness Conflict Risk	Clear Word/.docx niche with distinct triggers and an explicit exclusion list ('Do NOT use for PDFs, spreadsheets, Google Docs, or general coding'), giving minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 6 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: agentscope-ai/QwenPaw
Path: src/qwenpaw/agents/skills/docx-en/SKILL.md
Commit: 2094e07

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