CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docx

Create/edit/inspect Word documents using available managed or host capabilities.

Quality

68%

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 ./crates/tui/assets/skills/docx/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 exceptionally lean and well-organized with sensible policy guidance (preserve originals, verify by reopening), but it provides almost no executable detail — no commands, code, or concrete procedures for using python-docx/pandoc. Actionability and the concreteness of the verification step are the main weaknesses.

Suggestions

Add a minimal executable example, e.g. a short python-docx snippet for opening, editing, and saving a document, or a pandoc conversion command.

Make the verification step concrete (e.g. 'python -c "from docx import Document; print(Document(path).paragraphs[0].text)"') and describe what to do when verification fails.

Clarify step 1 ('Prefer .docx in the workspace') — state what to do when the document is in another format or not in the workspace.

DimensionReasoningScore

Conciseness

The 12-line body has zero padding and no explanation of concepts Claude already knows — sections are 'When to use', 'Compatibility', 'Workflow', each earning its tokens. Every line adds skill-specific information (aliasing behavior, originals preservation policy), matching 'lean and efficient; every token earns its place'.

5 / 5

Actionability

"Use python-docx/pandoc when available" names tools but provides no commands, code, or function-level guidance, and "Prefer .docx in the workspace" is a high-level hint. This matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute'; it is not a 3 because there is no even pseudocode-level concrete procedure.

2 / 5

Workflow Clarity

Four steps are clearly sequenced and step 4 is an explicit verification step ('Verify by reopening and extracting representative text'), placing it above the validation-absent anchors. It stays at 3 rather than 4 because the verification checkpoint is not concretely executable and there is no fix-and-retry feedback loop, which the rubric flags as important for document manipulation.

3 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and its three sections are clearly labeled and well-organized. Per the judging guideline for simple skills, well-organized sections alone earn 5 here.

5 / 5

Total

15

/

20

Passed

Description

58%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 concise and third-person with a clear capability statement, but it lacks any 'when to use' trigger guidance and misses the .docx extension and common synonyms that would make it surface reliably. Trigger term coverage and completeness are the main weaknesses.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with .docx or Word files, or when the user mentions memos, reports, or letters.'

Include the '.docx' extension and natural synonyms ('Word files', 'docx') in the description so it matches how users actually phrase requests.

Replace the vague 'using available managed or host capabilities' with one or two more concrete capability details (e.g. 'extract text and tables, fill templates, convert formats') to raise specificity.

DimensionReasoningScore

Specificity

"Create/edit/inspect Word documents" lists three specific concrete actions in a named domain, matching 'lists several specific actions; minor gaps in coverage'. It is not a 5 because coverage is terse (no extraction, conversion, or formatting detail) and "using available managed or host capabilities" is vague filler; not a 3 because three distinct actions exceed the '1-2 concrete actions' anchor.

4 / 5

Completeness

The description has a clear 'what' (create/edit/inspect Word documents) but contains no 'Use when...' clause or equivalent trigger guidance, which the judging guidelines explicitly cap at 3. It is not a 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

The only natural keyword cluster is "Word documents"; the description omits ".docx", "docx", "Word files", and "memos/reports/letters" which users would naturally say. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage (4) anchor whose example includes multiple trigger terms.

3 / 5

Distinctiveness Conflict Risk

"Word documents" carves a mostly distinct niche with minor overlap risk against generic document or PDF skills, matching 'mostly distinct; minor overlap risk'. It is not a 5 because without the .docx extension or narrower trigger phrases, generic document requests could still route here over other document skills.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

Hmbown/Codewhale

Path

crates/tui/assets/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.