CtrlK
BlogDocsLog inGet started
Tessl Logo

minimax-docx

Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three pipelines: (A) create new documents from scratch, (B) fill/edit content in existing documents, (C) apply template formatting with XSD validation gate-check. MUST use this skill whenever the user wants to produce, modify, or format a Word document — including when they say "write a report", "draft a proposal", "make a contract", "fill in this form", "reformat to match this template", or any task whose final output is a .docx file. Even if the user doesn't mention "docx" explicitly, if the task implies a printable/formal document, use this skill.

72

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

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

An exemplary content body: executable code and commands, a routed multi-pipeline workflow with mandatory validation and feedback loops, and clean one-level progressive disclosure into a verified reference bundle. Only minor conciseness gains remain in the inline Critical Rules prose.

DimensionReasoningScore

Conciseness

Largely lean and directive with tight tables and CLI shorthand, but the Critical Rules section inlines several lengthy prose rules (multi-template merge, multi-section headers) that could partly live in the scenario reference; minor trimming possible.

4 / 5

Actionability

Fully executable guidance throughout: copy-paste C# scaffold, concrete `$CLI` commands with full flags, and exact OpenXML values (sz='24' for 12pt, 1440 DXA/inch).

5 / 5

Workflow Clarity

Clear pipeline routing tree, a numbered validation pipeline run after every write, explicit auto-repair feedback loop (fix-order -> re-validate -> fallback), and a hard gate-check enforced before delivery for Scenario C.

5 / 5

Progressive Disclosure

Well-signaled one-level-deep references verified to exist (scenario guides, encyclopedia parts, sample .cs files, XSD assets) with two clear tables mapping topic-to-file; body stays an overview pointing into the bundle.

5 / 5

Total

19

/

20

Passed

Description

91%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, third-person description that explicitly covers both capability and trigger conditions with extensive natural phrasing including CJK synonyms. Specificity is slightly limited by summarizing pipelines rather than enumerating concrete document operations.

Suggestions

Consider listing 2-3 concrete document operations (e.g. tables, TOC, headers/footers, images) in the description to push specificity from pipeline-level to action-level.

Tighten the broad 'any task whose final output is a printable/formal document' clause to reduce overlap risk with PDF/presentation skills.

DimensionReasoningScore

Specificity

Names the domain (DOCX creation/editing/formatting) and three concrete pipelines (create, fill/edit, apply-template with XSD gate-check), but stops short of listing the many specific sub-actions (tables, TOC, headers, images) found in the body.

4 / 5

Completeness

Explicitly answers both 'what' (three named pipelines) and 'when' with a dedicated 'MUST use this skill whenever...' clause plus concrete trigger phrases and the implicit-document case.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including English phrases ('write a report', 'draft a proposal', 'make a contract', 'fill in this form'), the .docx extension, and CJK synonyms (报告, 合同, 公文, 排版).

5 / 5

Distinctiveness Conflict Risk

Clearly scoped to .docx via OpenXML SDK with distinct triggers, but the broad 'printable/formal document' phrasing creates minor overlap risk with PDF or presentation skills.

4 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 7 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
UnicomAI/wanwu
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.