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.'
Rewrite in third person with actionable language instead of a noun phrase label, e.g., 'Responds to user greetings with friendly, personalized welcome messages.'
| 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, well-scoped skill that does exactly one thing clearly. It's concise, actionable, and appropriately simple for its purpose. The only minor note is that it could benefit from slightly more structured markdown formatting, but for a skill this simple, the current format is perfectly adequate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely brief and every token serves a purpose. No unnecessary explanations or padding. | 3 / 3 |
Actionability | The instruction is completely concrete and unambiguous: a specific trigger ('hello' or greeting request) maps to a specific exact output string. Copy-paste ready response. | 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, which per the scoring notes qualifies for a 3. | 3 / 3 |
Progressive Disclosure | This is a sub-50-line skill with no need for external references. The content is well-organized in a single concise block, which per the scoring notes qualifies for a 3. | 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
0758a5e
- 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.