CtrlK
BlogDocsLog inGet started
Tessl Logo

greeter

A friendly greeter skill

68

2.17x
Quality

50%

Does it follow best practices?

Impact

100%

2.17x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./packages/cli/src/commands/extensions/examples/skills/skills/greeter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 exactly what it needs to do with no wasted tokens. The trigger condition and expected output are both explicit and unambiguous. There is nothing to improve given the simplicity of the task.

DimensionReasoningScore

Conciseness

The skill is extremely brief and every token serves a purpose. It doesn't explain what greetings are or pad with unnecessary context. For such a simple skill, this is appropriately lean.

3 / 3

Actionability

The instruction is completely concrete and unambiguous: when the user says 'hello' or asks for a greeting, reply with a specific exact string. There's no vagueness—the trigger and response are both explicit.

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 per the scoring notes for simple skills, this merits a 3.

3 / 3

Progressive Disclosure

For a skill under 50 lines with no need for external references, the content is well-organized in a single concise block. No additional files or structure are needed.

3 / 3

Total

12

/

12

Passed

Description

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 extremely weak across all dimensions. It provides no concrete actions, no trigger terms, no 'when to use' guidance, and no distinguishing characteristics. It reads more like a label than a functional description for skill selection.

Suggestions

Specify concrete actions the skill performs, e.g., 'Generates personalized greeting messages based on time of day, user name, and context.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for a greeting, welcome message, or says hello.'

Differentiate from general conversational skills by clarifying the specific greeting scenarios or formats this skill handles.

DimensionReasoningScore

Specificity

The description is entirely vague — 'friendly greeter skill' names no concrete actions, no domain details, and no specific capabilities. It is comparable to 'Helps with documents' in its lack of substance.

1 / 3

Completeness

Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause or any explicit trigger guidance.

1 / 3

Trigger Term Quality

There are no natural keywords a user would say. 'Greeter' is not a term users typically use in requests, and no variations or synonyms are provided.

1 / 3

Distinctiveness Conflict Risk

The description is so generic that it could overlap with any conversational or introductory skill. There is nothing to distinguish it from other skills.

1 / 3

Total

4

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
google-gemini/gemini-cli
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.