CtrlK
BlogDocsLog inGet started
Tessl Logo

minimax-docx

Professional DOCX document creation and editing using OpenXML SDK. Useful for branded reports, polished proposals, and template-based authoring.

42

Quality

42%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/minimax-docx/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body acts as a thin catalogue stub that defers all real guidance to an external upstream repo, offering little actionable or verifiable instruction. It is concise but lacks executable steps, a real workflow, and any local progressive-disclosure structure.

Suggestions

Replace the external-repo pointer with at least one concrete, copy-paste-ready command or code snippet for the core task (e.g., creating a DOCX via OpenXML SDK).

Define a real multi-step workflow with explicit validation (e.g., create -> validate -> pack) instead of 'inspect the upstream README'.

Either ship local references/scripts and link to them with well-signaled one-level-deep paths, or clearly state that this entry is a discovery stub so reviewers don't expect in-skill instructions.

DimensionReasoningScore

Conciseness

The body is short and avoids re-explaining concepts Claude knows, but spends tokens on meta framing ('This catalogue entry advertises the skill in Open Design so the agent discovers it during planning') that does not advance the skill's purpose; matches the 'mostly efficient but includes some unnecessary explanation' anchor.

2 / 3

Actionability

The only executable snippet is `open https://github.com/...`; the rest defers to 'install the upstream bundle' and 'ask the agent to invoke' with no concrete commands, paths, or steps, so it describes rather than instructs; matches the 'vague or abstract; no concrete code/commands' anchor.

1 / 3

Workflow Clarity

There is a minimal ordering (inspect the upstream README, then invoke the skill) but no real sequence with validation checkpoints, and the actual workflow is offloaded to an external README; matches the 'steps listed but validation gaps / checkpoints missing' anchor.

2 / 3

Progressive Disclosure

No local bundle files exist and the only reference points to an external GitHub repo rather than well-signaled one-level-deep local files; there is some section structure but no appropriately split local references, matching the 'some structure but could be better organized; references not clearly signaled' anchor.

2 / 3

Total

7

/

12

Passed

Description

50%

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 competent and on-topic but generic: it states the domain and a few use cases without concrete actions or an explicit 'Use when' trigger clause. It would benefit from listing specific verbs and adding explicit trigger guidance.

Suggestions

Add concrete actions (e.g., 'generate branded reports from templates, insert tables and charts, apply styles') instead of the generic 'creation and editing'.

Add an explicit 'Use when the user needs to produce Word/.docx files, branded reports, proposals, or template-driven documents' trigger clause.

Include natural phrasings a user would say ('Word document', '.docx', 'make a report') alongside the technical 'OpenXML SDK' term.

DimensionReasoningScore

Specificity

It names the domain ('DOCX document creation and editing using OpenXML SDK') and a few use cases, but stops at create/edit rather than listing multiple concrete actions; matches the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

It answers 'what' (DOCX creation/editing) but offers only an implied 'when' via 'Useful for...', with no explicit 'Use when...' trigger clause; per the guidelines a missing explicit trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

It includes some natural terms ('branded reports', 'proposals', 'template-based authoring') alongside jargon ('OpenXML SDK'), but misses common variations a user would actually say such as 'Word document' or 'make a .docx'; matches the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

DOCX/OpenXML SDK is a reasonably clear niche, yet it could still overlap with a general document-authoring skill; matches the 'somewhat specific but could still overlap' anchor rather than a fully distinct niche.

2 / 3

Total

8

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.