CtrlK
BlogDocsLog inGet started
Tessl Logo

aif-hello-world

A hello world skill provided by the aif-ext-hello extension. Demonstrates extension-provided skills.

54

Quality

60%

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 ./examples/extensions/aif-ext-hello/skills/aif-hello-world/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 appropriately concise and clearly structured for a trivial single-purpose skill; it would benefit only from a concrete example greeting to make the action fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean (under 15 lines) with no padding or explanations of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

It gives a concrete instruction ("respond with a friendly greeting and confirm that the extension system is working") and an invocation path, but lacks a copy-paste-ready example greeting, leaving a minor gap.

4 / 5

Workflow Clarity

This is a simple single-action skill with an unambiguous instruction; per the simple-skill exception the single action is fully clear with no validation needed.

5 / 5

Progressive Disclosure

The content is well-organized with a clear overview and a Usage section, and being under 50 lines with no need for external references it satisfies the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

28%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 concise and accurate but functions as an internal demo label rather than a user-facing trigger; it lacks concrete actions and any explicit "when to use" guidance.

Suggestions

Add a concrete "Use when..." clause describing when this skill should be invoked (e.g., testing that the extension system is working).

Replace the internal phrase "extension-provided skills" with natural user-facing trigger terms.

State the concrete action the skill performs ("Responds with a friendly greeting") instead of the abstract "Demonstrates".

DimensionReasoningScore

Specificity

The description names the domain ("hello world skill", "extension-provided skills") but the only action stated is "Demonstrates", which is minimal and generic rather than a concrete capability.

2 / 5

Completeness

It states a vague "what" (demonstrates extension-provided skills) but provides no "Use when..." clause or any trigger guidance, and the what is itself weak, so it falls at the low end between anchors 1 and 3.

2 / 5

Trigger Term Quality

Phrases like "aif-ext-hello extension" and "extension-provided skills" are technical/internal labels; a user would not naturally say these when needing this skill, and natural trigger phrases are absent.

2 / 5

Distinctiveness Conflict Risk

The hello-world/demo niche is somewhat specific, but the generic phrasing ("Demonstrates extension-provided skills") could overlap with other extension test skills, so it sits at the midpoint anchor.

3 / 5

Total

9

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
lee-to/ai-factory
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.