CtrlK
BlogDocsLog inGet started
Tessl Logo

documents

Compatibility alias for the docx skill. Prefer loading docx.

63

Quality

75%

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

100%

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

The body is a lean, unambiguous alias redirect that does exactly what is needed and nothing more. It is appropriately concise and actionable for a compatibility shim.

DimensionReasoningScore

Conciseness

The body is two sentences that do nothing but state the alias relationship and the single instruction; every token earns its place and no known concepts are over-explained.

3 / 3

Actionability

"Load and follow the `docx` skill body for the actual workflow." is concrete, specific, and executable guidance for an instruction-only alias skill, so the absence of code is not penalized.

3 / 3

Workflow Clarity

This is a single-task skill whose one action (load and follow docx) is unambiguous, which the simple-skills note allows to score 3.

3 / 3

Progressive Disclosure

The file is well under 50 lines with no need for external references, and its heading-plus-two-lines layout is cleanly organized, satisfying the simple-skills exception.

3 / 3

Total

12

/

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 concisely identifies the skill as a docx alias but lacks explicit trigger guidance and natural keyword coverage. It is clear on 'what' yet silent on 'when.'

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user mentions Word documents, .docx files, or asks to read/edit docx content.'

Broaden trigger terms to include natural variations like 'Word,' 'Word documents,' and '.docx' alongside 'docx.'

Reinforce distinctiveness by noting it exists only for backward compatibility and should not be chosen over docx directly.

DimensionReasoningScore

Specificity

"Compatibility alias for the docx skill. Prefer loading docx." names the domain (docx) and a concrete action (load docx), but does not list multiple specific capabilities like the score-3 anchor requires.

2 / 3

Completeness

It answers the 'what' (alias for docx) clearly but provides no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

The only natural keyword is "docx"; common variations a user would say (Word, .docx, documents, Word files) are missing, matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The generic name "documents" could overlap with other document-handling skills and the description offers no distinct triggers, though the explicit 'prefer loading docx' redirect narrows its scope.

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