CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

documents

Compatibility alias for the docx skill. Prefer loading docx.

Quality

77%

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%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 a maximally efficient delegation stub: it states the alias relationship and gives one complete, executable instruction. For its purpose there is nothing to add and nothing to trim.

DimensionReasoningScore

Conciseness

The body is three lean lines — 'This skill is a compatibility alias for **docx**.' and 'Load and follow the `docx` skill body for the actual workflow.' — with zero padding and no explanation of concepts Claude already knows. It matches anchor 5 ('Lean and efficient; assumes Claude's competence; every token earns its place').

5 / 5

Actionability

The single directive — 'Load and follow the `docx` skill body for the actual workflow.' — names the exact skill to load and what to do with it, which is fully executable guidance. Per the code_vs_instruction scoring note, absence of code in an instruction-only skill is not penalized when the guidance is actionable, and here it is unambiguous for the skill's single purpose.

5 / 5

Workflow Clarity

This is a single-task skill (delegation) with one unambiguous action and no destructive or batch operations, so the simple-skill exception applies and workflow clarity can score 5. There are no gaps: nothing is left implicit about what to do next.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files present (no references/, scripts/, or assets/ directories), and its single external pointer — the `docx` skill — is one level deep and clearly signaled. Under the simple-skill guideline this matches anchor 5; there is no inlined content that belongs in separate files.

5 / 5

Total

20

/

20

Passed

Description

45%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 honest and concise about being an alias, but as a standalone trigger it is weak: it declares no capabilities, no use-when guidance, and no disambiguating keywords beyond 'docx'. An alias description still needs to carry enough of the target skill's semantics to route correctly.

Suggestions

Add a 'Use when...' clause stating when this alias applies (e.g., 'Use when the user asks for the documents skill or mentions docx/Word file tasks').

Summarize the target skill's core capabilities so the alias can route on its own (e.g., 'Delegates to docx: creating, editing, and analyzing .docx files').

Include natural trigger synonyms such as 'Word documents', '.docx', and 'Office files' to reduce overlap with pdf and other document skills.

DimensionReasoningScore

Specificity

The description names the target domain ('the docx skill') but describes no capability actions of its own — 'Compatibility alias for the docx skill. Prefer loading docx.' states only what the skill is, never what it does (create, edit, or read Word documents). This matches the anchor 'Names the domain but actions are minimal or generic'; it is above level 1 because the domain and delegation target are explicitly named, but below level 3 because no concrete action verb beyond 'loading' appears.

2 / 5

Completeness

The 'what' is explicit ('Compatibility alias for the docx skill. Prefer loading docx.') but the 'when' is entirely absent, matching anchor 3 ('Has a clear what but when is missing'), and the judging guidelines independently cap completeness at 3 for a missing 'Use when...' clause. It is above anchor 2 because the what is clear, not vague.

3 / 5

Trigger Term Quality

'docx' is a natural keyword users would say, so it rises above anchor 2's 'only generic keywords', but coverage stops there — missing 'Word', '.docx', 'Word documents', and any 'Use when...' phrasing, matching anchor 3 ('Some relevant keywords but missing common variations or synonyms').

3 / 5

Distinctiveness Conflict Risk

The explicit delegation to docx reduces confusion about intent, but the alias name 'documents' and the bare description give it broad overlap with pdf, xlsx, and other document-adjacent skills — fitting anchor 3 ('Somewhat specific but could still overlap with similar skills'). It is below anchor 4 because the description offers no distinct trigger to disambiguate when this alias versus the real docx skill should fire.

3 / 5

Total

11

/

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