greeter
A friendly greeter skill
63
42%
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
Specify concrete actions the skill performs, e.g., 'Generates personalized greeting messages, welcome responses, and introductions for users.'
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 general 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 | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no meaningful explanation of functionality. | 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 extremely generic. 'Friendly greeter' could overlap with any conversational or introductory skill, and provides no distinct triggers or niche to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
85%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 greeting skill that is clear and unambiguous in its instruction. Its main weakness is minor verbosity in framing ('You are a friendly greeter') which doesn't add value. Overall it accomplishes its narrow goal effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is short but includes some unnecessary framing ('You are a friendly greeter') that Claude doesn't need explained. The phrase 'When the user says "hello" or asks for a greeting' is slightly verbose but not egregiously so. | 2 / 3 |
Actionability | For this simple skill, the instruction is fully concrete and unambiguous: it specifies the exact trigger conditions and the exact output string to produce. No code is needed for an instruction-only greeting skill. | 3 / 3 |
Workflow Clarity | This is a single-action skill with no multi-step process. The single action (respond with a specific greeting) is completely unambiguous, so workflow clarity is satisfied per the simple-skills scoring note. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is appropriately self-contained. No additional files or references are needed for this trivial skill. | 3 / 3 |
Total | 11 / 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
77e65c0
- 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.