CtrlK
BlogDocsLog inGet started
Tessl Logo

greeter

A friendly greeter skill

70

2.17x
Quality

53%

Does it follow best practices?

Impact

100%

2.17x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./packages/cli/src/commands/extensions/examples/skills/skills/greeter/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, fully actionable instruction with a concrete trigger and exact response string, appropriate for a simple single-purpose skill. It respects the token budget and needs no external references.

DimensionReasoningScore

Conciseness

Two short lines with no padding or explanation of concepts Claude already knows; every token earns its place. It is not a 2 because there is no unnecessary explanation to trim.

3 / 3

Actionability

It gives an explicit trigger ("says 'hello' or asks for a greeting") and the exact verbatim reply string, making it copy-paste ready. It is not a 2 because no key details are missing.

3 / 3

Workflow Clarity

This is a simple single-action skill with an unambiguous trigger and response, which the rubric allows to score 3. It is not a 2 because the single action is fully clear with nothing implicit.

3 / 3

Progressive Disclosure

A sub-50-line single-task skill with no need for external references qualifies for 3 under the rubric's simple-skills note; content is self-contained. It is not a 2 because nothing is mis-split or poorly signaled.

3 / 3

Total

12

/

12

Passed

Description

7%

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 a minimal label that conveys a domain but omits concrete actions, natural trigger terms, and any "when to use" guidance. It is too vague to clearly route Claude to this skill.

Suggestions

Add concrete actions, e.g. "Replies with a friendly greeting when greeted."

Add an explicit "Use when..." trigger clause naming natural phrases like "hello", "hi", or "greet me".

Include natural trigger terms users would actually say rather than the abstract label "greeter skill".

DimensionReasoningScore

Specificity

"A friendly greeter skill" names only a domain and no concrete actions, matching the vague/abstract anchor ("Helps with documents"). It is not a 2 because it lists no specific actions at all.

1 / 3

Completeness

It gives a weak "what" (greeter) and entirely lacks a "when"/"Use when..." trigger clause, so both halves are missing or very weak. It is not a 2 because the "what" itself is too vague to count as adequate.

1 / 3

Trigger Term Quality

"greeter" is a label, not a natural phrase a user would say; no keywords like "hello", "greet me", or "greeting" appear. It is not a 2 because there are no common variations present.

1 / 3

Distinctiveness Conflict Risk

Greeting is a recognizable niche, but with no explicit triggers it could still overlap with general conversation. It is not a 3 because there are no distinct triggers; not a 1 because the niche is fairly specific.

2 / 3

Total

5

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
google-gemini/gemini-cli
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.