CtrlK
BlogDocsLog inGet started
Tessl Logo

greet

A greeting skill for testing

52

Quality

56%

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 ./packages/coding-agent/test/marketplace/fixtures/valid-marketplace/plugins/hello-plugin/skills/greet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

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

The body is an admirably concise, unambiguous single-action directive that suits a trivial greeting skill; it lacks examples and section organization but needs none for this scope.

DimensionReasoningScore

Conciseness

"Say hello to the user." is a lean, single-action directive with zero padding that fully assumes Claude's competence, matching the lean-and-efficient anchor.

5 / 5

Actionability

It gives a concrete, executable directive appropriate for an instruction-only skill, but lacks any examples or specifics covering common cases, sitting just below the fully-executable-with-examples anchor at 5.

4 / 5

Workflow Clarity

This is a simple single-task skill whose single action is unambiguous and non-destructive, qualifying for the simple-skill exception that allows workflow clarity to score 5.

5 / 5

Progressive Disclosure

At under 50 lines with no need for external references the content is appropriately minimal, though the complete absence of any section structure keeps it just below the well-organized anchor at 5.

4 / 5

Total

18

/

20

Passed

Description

25%Weight 40%Scale 1-5

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

The description is minimal and names the greeting domain but provides no concrete actions, no trigger terms, and no usage guidance, making it indistinguishable from other conversational skills.

Suggestions

Add a concrete action verb, e.g. "Greets the user with a friendly hello message."

Append a "Use when..." clause naming natural trigger phrases (e.g. "Use when the user starts a session or asks to be greeted").

Include synonyms or related terms (greeting, hello, welcome) to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

The phrase "A greeting skill for testing" names the domain (greeting) but offers no concrete actions, matching the anchor "Names the domain but actions are minimal or generic" rather than the entirely-vague 1 or the action-listing 3.

2 / 5

Completeness

It gives a vague "what" ("A greeting skill") and entirely omits a "when" trigger clause, which per the guidelines caps completeness at 3 but best matches the vague-what/no-when anchor at 2.

2 / 5

Trigger Term Quality

Only one generic keyword ("greeting") is present with no natural user phrasings or synonyms, fitting the anchor for one or two generic keywords rather than the broader coverage at 3.

2 / 5

Distinctiveness Conflict Risk

"A greeting skill for testing" is very broad with high overlap risk against any conversational skill, matching the very-broad anchor rather than the somewhat-specific 3.

2 / 5

Total

8

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
can1357/oh-my-pi
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.