CtrlK
BlogDocsLog inGet started
Tessl Logo

documents

Compatibility alias for the docx skill. Prefer loading docx.

60

Quality

70%

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/documents/SKILL.md
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.

The body is an exemplary lean alias: minimal, unambiguous, and correctly delegating all real work to the docx skill with a single clearly signaled one-level reference, with no wasted tokens.

DimensionReasoningScore

Conciseness

The body is two tight sentences with zero padding ('This skill is a compatibility alias for docx. Load and follow the docx skill body for the actual workflow.'), assuming Claude's competence and earning every token, matching the 'lean and efficient' anchor exactly.

5 / 5

Actionability

'Load and follow the docx skill body' is a concrete, executable directive naming the exact target skill, meeting 'mostly executable guidance'; it stops short of score 5 only because no examples are given, though for an alias a single redirect is the whole task.

4 / 5

Workflow Clarity

Per the simple-skill exception, a single unambiguous action (load and follow the docx skill) can score 5; there is no destructive or batch operation, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no bundle files, and cleanly delegates one level deep to the docx skill with a clearly signaled pointer, satisfying the simple-skill exception for well-organized content.

5 / 5

Total

19

/

20

Passed

Description

48%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 correctly and concisely identifies the skill as a docx compatibility alias, but it functions as a redirect rather than a capability statement: it names no concrete actions, includes only the single keyword 'docx', and lacks any 'when to use' trigger guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about .docx files or document editing and the docx skill is available.'

Name one or two concrete capabilities inherited from docx (e.g. 'reads, edits, and creates .docx files') to lift specificity above a pure redirect.

Broaden trigger terms beyond 'docx' to include 'Word documents', '.docx', and 'document editing' to improve natural keyword coverage.

DimensionReasoningScore

Specificity

The description ('Compatibility alias for the docx skill. Prefer loading docx.') names the domain (docx) but states no concrete actions of its own — it only redirects to another skill, matching the 'names domain but actions minimal/generic' anchor rather than score 1 which requires total vagueness or score 3 which requires 1-2 concrete actions.

2 / 5

Completeness

It gives a clear 'what' (this is a compatibility alias for docx) but provides no 'Use when...' trigger clause, so per the judging guidelines a missing explicit trigger caps completeness at 3; it is not score 2 because the 'what' is clear rather than vague.

3 / 5

Trigger Term Quality

It contains the natural keyword 'docx' (a file extension users say), but offers no synonyms or variations and no trigger phrasing, fitting 'some relevant keywords but missing common variations'; it is above score 2 because 'docx' is specific rather than generic, but below score 4 which expects broader keyword coverage.

3 / 5

Distinctiveness Conflict Risk

By explicitly declaring itself a docx alias and instructing 'Prefer loading docx', it occupies a clear niche with only minor overlap risk against the real docx skill (intentional); it falls short of score 5 because the alias name 'documents' is broad and could surface for unrelated document tasks.

4 / 5

Total

12

/

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.

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
Hmbown/CodeWhale
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.