CtrlK
BlogDocsLog inGet started
Tessl Logo

say-hi

Respond with a friendly greeting. Use when the user says hi, hello, greets the agent, or asks to be greeted.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/say-hi/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A clean, well-organized minimal skill body that suits its simple single-task purpose, scoring top marks on workflow clarity and structure. It loses points for stylistic guidance that adds little beyond the description and for lacking a concrete example greeting.

Suggestions

Add one concrete example greeting (e.g., a sample reply) so the guidance is actionable rather than purely stylistic.

Tighten or remove the Greeting Style bullets that restate the description ("friendly greeting") and reflect behavior Claude already applies, keeping only any non-obvious preference.

If a specific tone or length target matters, state it concretely (e.g., "Reply in one short sentence") instead of abstract directives like "Match the user's energy level".

DimensionReasoningScore

Conciseness

The body is lean ("Be genuine and welcoming", "Keep it brief and natural", "Match the user's energy level"), but this soft stylistic guidance largely restates the description's "friendly greeting" and what Claude already does, so not every token earns its place; it stops short of the fully efficient 3.

2 / 3

Actionability

"respond with a warm, friendly greeting" is a clear instruction, but the body offers no concrete example greeting or specific output, leaving the guidance incomplete rather than copy-paste concrete; it instructs rather than merely describes, so above a 1.

2 / 3

Workflow Clarity

This is a simple single-purpose skill whose single action (greet the user) is unambiguous, so per the simple-skills note workflow clarity earns a 3 without needing multi-step sequencing.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ bundles exist) and uses clear organized sections ("# Say Hi", "## Greeting Style"), meeting the simple-skills bar for a 3.

3 / 3

Total

10

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-formed description that clearly pairs a single concrete action with an explicit, natural-language trigger clause. Its only limitation is naming just one action rather than multiple, which keeps specificity at 2.

DimensionReasoningScore

Specificity

The phrase "Respond with a friendly greeting" names the skill's single concrete action, but only one action is listed rather than the "multiple specific concrete actions" required for a 3; it is not vague enough for a 1.

2 / 3

Completeness

It states what ("Respond with a friendly greeting") and gives an explicit when clause ("Use when the user says hi, hello, greets the agent, or asks to be greeted"), satisfying both halves with an explicit trigger.

3 / 3

Trigger Term Quality

"hi, hello, greets the agent, or asks to be greeted" are exactly the natural terms a user would say, giving good coverage of common greeting variations.

3 / 3

Distinctiveness Conflict Risk

Greeting is a clear, narrow niche with distinct, explicit triggers ("hi, hello, greets the agent") that are unlikely to fire for task-oriented skills; it is not the generic, conflicting "Helps with code and documents" of a 1.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
amilich/isometric-city
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.