greeter
A friendly greeter skill
68
50%
Does it follow best practices?
Impact
100%
2.17xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/cli/src/commands/extensions/examples/skills/skills/greeter/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an extremely weak description that fails on all dimensions. It reads more like a label than a functional description, providing no concrete actions, no trigger terms, and no guidance on when Claude should select this skill. It is essentially unusable for skill selection among multiple options.
Suggestions
Describe specific concrete actions the skill performs, e.g., 'Generates personalized greeting messages, welcome responses, and introductions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user says hello, hi, greetings, or asks to be welcomed.'
Differentiate from other conversational skills by specifying the exact context or format of greetings this skill handles.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'A friendly greeter skill' is entirely abstract and vague, comparable to 'Helps with documents'. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause and no description of actual capabilities. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is 'greeter' which is not a natural keyword users would say. Users might say 'hello', 'hi', 'greeting', or 'introduce yourself' but none of these are present. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's unclear what domain it belongs to. 'Friendly greeter' could overlap with any conversational or introductory skill and provides no distinct triggers. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a minimal, single-purpose skill that does its job well. It is concise, unambiguous, and appropriately scoped for its simple task. No improvements are needed given the trivial nature of the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely brief and every token serves a purpose. No unnecessary explanation of concepts Claude already knows. | 3 / 3 |
Actionability | The instruction is fully concrete and unambiguous: a specific trigger ('hello' or greeting request) maps to a specific, copy-paste-ready output string. No vagueness. | 3 / 3 |
Workflow Clarity | This is a simple single-action skill with no multi-step process. The single action (respond with a specific greeting) is completely unambiguous, so per the scoring notes for simple skills, this qualifies for a 3. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized and appropriately scoped. No additional structure or references are needed. | 3 / 3 |
Total | 12 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- google-gemini/gemini-cli
- Commit
9f76f34
- 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.