CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hello

Greet the user

Quality

74%

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 ./canary-plugin/skills/hello/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 a lean, unambiguous instruction that matches the skill's trivial single purpose, scoring near the top of the rubric thanks to the simple-skill exceptions. The only gap is the total absence of an example greeting, which keeps actionability at 4.

DimensionReasoningScore

Conciseness

The body is just "# Hello skill" and "Say hi to the user." — no padding, no explanation of concepts Claude already knows, and every token earns its place.

5 / 5

Actionability

"Say hi to the user." is a direct, executable instruction for this trivial task, but it offers no example greeting or variant, leaving a minor gap (anchor 4: 'mostly executable guidance with minor gaps') rather than fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines, and the single action ('Say hi to the user.') is unambiguous; per the simple-skill exception no multi-step sequence or validation is needed, and nothing destructive or batch-related applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external material; no references/scripts/assets bundle exists, and the entire content appropriately fits in SKILL.md with nothing buried or inlined that belongs elsewhere.

5 / 5

Total

19

/

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 states a clear single intent but is far below the good examples: it has only one generic action verb, no trigger clause, and none of the natural phrases users would say when they want a greeting. It sits at or slightly above the midpoint on most dimensions, with specificity the weakest.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to be greeted, says hello or hi, or wants a welcome message" — this alone lifts completeness from 3 toward 4-5.

Make the 'what' concrete instead of a single generic verb: describe what the greeting actually does (e.g., personalized or time-of-day-aware greeting) so specificity rises above 2.

Include the natural synonyms users actually say — "say hi", "hello", "welcome" — so trigger term coverage matches real user phrasing.

DimensionReasoningScore

Specificity

"Greet the user" names the domain with a single generic action, mirroring the anchor-2 example 'Processes PDF files'; there is no concrete detail about what the greeting involves. It is not 1 (it does state a concrete action, unlike 'Helps with documents') nor 3 (that requires 1-2 concrete actions with substance).

2 / 5

Completeness

The 'what' is stated clearly ('Greet the user') but a 'when' is entirely absent — no "Use when..." clause or equivalent trigger guidance, which the guidelines cap at 3. Not 4, because the 'when' is not weakly implied anywhere, let alone explicit.

3 / 5

Trigger Term Quality

"Greet" is a domain-relevant keyword (analogous to 'PDF' in the anchor-3 example 'Works with PDF files'), but every natural phrase a user would actually say — 'say hi', 'hello', 'welcome' — is missing. Not 2, because 'greet' is not generic the way 'files' is; not 4, because there are no synonyms or variations at all.

3 / 5

Distinctiveness Conflict Risk

"Greet the user" names a specific intent that would not trigger for unrelated skills, but it is generic within its own domain (like the anchor-3 example 'Works with document files') and could overlap with any greeting/welcome/social skill. Not 4, because nothing distinguishes this particular greeting skill from similar ones.

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

description_field

'description' is very short (14 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository

ruaan-tessl/int-3542-canary

Path

canary-plugin/skills/hello/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.