CtrlK
BlogDocsLog inGet started
Tessl Logo

glossary

Look up, add, or audit Chatto terms in docs/GLOSSARY.md.

60

Quality

71%

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 ./.agents/skills/glossary/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a tightly written, well-structured instruction skill with concrete guidance, clear task sequencing, and appropriate validation/approval gates. The only mild gap is a few implicit checkpoints and entry-format details that could be made fully explicit.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or over-explanation of concepts Claude already knows; every line carries instruction, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete, specific guidance throughout ('Check for duplicates', 'Expand abbreviations on first use', 'Limit missing-term proposals to about ten'); as an instruction-only skill the absence of code is not penalized, but a few details (exact entry format) remain implicit, sitting between the mostly-executable and fully-executable anchors.

4 / 5

Workflow Clarity

Each task (Lookup/Add/Audit) has a clear sequence with validation checkpoints such as duplicate/source checks and 'propose ... for approval before writing'; the destructive/batch cap does not apply because explicit validation gates are present, but a couple of checkpoints are implicit rather than stated as feedback loops.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (Tasks/Entries) and a single clearly-signaled one-level reference to the project glossary, qualifying for the simple-skill exception that allows a 5 without external bundle references.

5 / 5

Total

18

/

20

Passed

Description

57%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, third-person, and well-scoped to a distinct niche, but it lacks an explicit 'Use when...' trigger clause and offers only terse action verbs without comprehensive coverage. Adding trigger phrases and slightly richer action detail would lift specificity and completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to look up, define, or audit Chatto glossary terms.'

Expand the action list with a couple more concrete capabilities (e.g. 'check for duplicates', 'verify definitions against code, FDRs, and ADRs') to improve specificity.

Include a natural synonym or file reference (e.g. 'docs/GLOSSARY.md') as a trigger term to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (Chatto glossary terms) and three concrete actions ('Look up, add, or audit'), but the actions are terse verb phrases without elaboration, matching the '1-2 concrete actions, not comprehensive' anchor rather than the comprehensive level 4.

3 / 5

Completeness

The 'what' is clear (look up/add/audit terms) but there is no explicit 'Use when...' trigger clause, so per the rubric's capping guideline completeness cannot exceed 3.

3 / 5

Trigger Term Quality

Relevant keywords like 'Look up', 'audit', 'glossary', and 'terms' are present, but natural synonyms and file extensions are missing, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Scoped to 'Chatto terms in docs/GLOSSARY.md' — a clearly defined niche tied to a specific project file with minimal overlap risk, matching the 'clear niche with distinct triggers' anchor.

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
chattocorp/chatto
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.