greeter
tessl i github:google-gemini/gemini-cli --skill greeterA friendly greeter skill
Review Score
65%
Validation Score
11/16
Implementation Score
100%
Activation Score
0%
Generated
Validation
Total
11/16Score
Passed| Criteria | Score |
|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') |
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow |
Implementation
Score
100%Overall Assessment
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 scope.
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 3/3 | The skill is extremely brief (2 lines) and contains only the essential instruction. No unnecessary explanation of what greetings are or how to respond. |
Actionability | 3/3 | 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. |
Workflow Clarity | 3/3 | This is a simple single-action skill with no multi-step process. The single action (respond with specific text) is completely unambiguous. |
Progressive Disclosure | 3/3 | For a skill under 50 lines with no need for external references, the content is appropriately self-contained and well-organized. |
Activation
Suggestions 3
Score
0%Overall Assessment
This description is critically underdeveloped, scoring at the lowest level across all dimensions. It provides no concrete actions, no trigger terms, no usage guidance, and would be indistinguishable from other skills. Claude would have no reliable basis for selecting this skill from a collection.
Suggestions
- Add specific concrete actions the skill performs (e.g., 'Generates personalized welcome messages, introduces users to available features, provides onboarding guidance')
- Include a 'Use when...' clause with natural trigger terms (e.g., 'Use when users say hello, ask for introductions, request help getting started, or need onboarding assistance')
- Define the specific context or domain where this skill applies to distinguish it from general conversation (e.g., 'for new users joining a workspace' or 'for application onboarding flows')
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 1/3 | The description 'A friendly greeter skill' uses vague, abstract language with no concrete actions specified. It doesn't describe what the skill actually does. |
Completeness | 1/3 | Missing both 'what does this do' (no specific actions) and 'when should Claude use it' (no 'Use when...' clause or equivalent guidance). |
Trigger Term Quality | 1/3 | Contains no natural keywords users would say. 'Greeter' is not a term users would naturally use when requesting help, and there are no trigger terms like 'hello', 'welcome', or 'introduction'. |
Distinctiveness Conflict Risk | 1/3 | Extremely generic description that provides no clear niche. 'Friendly greeter' could overlap with any conversational or introductory skill and lacks distinct triggers. |