greeter
A friendly greeter skill
60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
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 description is critically underdeveloped and fails on all dimensions. It provides no concrete actions, no trigger terms users would naturally use, no guidance on when to select this skill, and is too vague to distinguish from other skills. It reads more like a label than a functional description.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Generates personalized welcome messages, creates onboarding greetings, writes introductory text for new users').
Include a 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks for a greeting, welcome message, introduction, or says hello').
Specify the context or format of greetings to distinguish from general conversation (e.g., 'for emails, chat interfaces, or application onboarding flows').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description 'A friendly greeter skill' contains no concrete actions - it doesn't specify what the skill actually does (e.g., generate greetings, welcome users, create messages). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no specific actions) and 'when should Claude use it' (no 'Use when...' clause or trigger guidance). | 1 / 3 |
Trigger Term Quality | The only potential trigger term is 'greeter' which is not a natural word users would say. Users would more likely say 'hello', 'welcome message', 'greeting', or 'introduce'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely vague - 'friendly' and 'greeter' could overlap with any conversational, onboarding, or welcome-related skill without clear boundaries. | 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 an effective minimal skill that does exactly what it needs to do. It's concise, provides an exact response to use, and has clear trigger conditions. The simplicity is appropriate for the task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely brief (2 lines) and contains only the essential instruction. No unnecessary explanation of what greetings are or how to respond. | 3 / 3 |
Actionability | Provides a concrete, copy-paste ready response with the exact text and emoji to use. The trigger conditions ('hello' or greeting request) are clearly specified. | 3 / 3 |
Workflow Clarity | This is a simple single-action skill with no multi-step process. The single action (respond with specific text) is completely unambiguous. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is appropriately self-contained and well-organized. | 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.
- 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.