aif-hello-world

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

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

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 content is an exemplary minimal skill body: brief, unpadded, and unambiguous about what to do and how the skill is invoked. Its only minor gap is the absence of an example response, which keeps actionability at 4 rather than 5.

Dimension	Reasoning	Score
Conciseness	The 9-line body contains no padding and no explanation of concepts Claude already knows — every sentence (the greeting instruction, the confirmation instruction, the invocation trigger) earns its place. This matches anchor 5 (lean and efficient, assumes Claude's competence); it is not 4 because there is no over-explanation to trim.	5 / 5
Actionability	The guidance is concrete and executable for an instruction-only skill: "respond with a friendly greeting and confirm that the extension system is working" plus the concrete trigger "Simply say \"hello\" or invoke /aif-hello-world to test". It falls just short of anchor 5 because no example greeting or expected output is given, leaving a minor gap.	4 / 5
Workflow Clarity	This is a simple, single-purpose skill and the single action is unambiguous — per the rubric's simple-skill guideline, workflow clarity can score 5 when the one action is clear. No destructive or batch operations are involved, so the validation cap does not apply; it is not 4 because nothing is ambiguous or missing for a task of this scope.	5 / 5
Progressive Disclosure	The body is under 50 lines, needs no external reference files (and none exist in the bundle), and is organized into a clear heading plus a "## Usage" section. Per the rubric's simple-skill guideline, this matches anchor 5 — well-organized sections with no nested or buried references.	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 grammatically clean and appropriately brief, but it is essentially a placeholder: it names the skill's domain without stating what it concretely does, and it completely lacks any 'when to use this' trigger guidance. As a result it reads like metadata for a demo rather than a discoverable, actionable skill description.

Suggestions

State the concrete actions the skill performs, e.g., "Responds with a friendly greeting and confirms the extension system is working" instead of the generic "Demonstrates extension-provided skills".

Add an explicit trigger clause, e.g., "Use when the user says 'hello', asks to test the extension system, or invokes /aif-hello-world".

Include natural trigger terms users would actually say ("test extension", "greeting", "aif-ext-hello") to raise trigger-term coverage and reduce overlap with other demo skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("A hello world skill provided by the aif-ext-hello extension") but the only action stated is the generic "Demonstrates extension-provided skills"; no concrete capabilities are listed. It fits anchor 2 rather than 3 because there is no enumeration of even 1-2 specific actions, and it is not 1 since it is not pure abstract language.	2 / 5
Completeness	The "what" is vague ("hello world skill", "Demonstrates extension-provided skills") and the "when" is entirely absent. This is exactly anchor 2 (vague what, no when); it cannot be 3 because even the what is not concrete, and the missing 'Use when' clause caps completeness at 3 anyway.	2 / 5
Trigger Term Quality	The only usable keywords are "hello world" and "extension"; there are no natural trigger phrases a user would say (e.g., "test the extension", "greeting", "check the skill system") and no "Use when" phrasing. This matches anchor 2 (one or two generic keywords, missing natural phrases) rather than 3, which requires a broader set of relevant keywords.	2 / 5
Distinctiveness Conflict Risk	"hello world" and the specific extension name "aif-ext-hello" give it a somewhat distinct niche, but "Demonstrates extension-provided skills" overlaps with any test/demo skill. Anchor 3 (somewhat specific but could overlap with similar skills) is the best fit — not 4 since other demo or extension-testing skills would compete for the same triggers.	3 / 5
	Total	9 / 20 Passed

Validation

100%

Warnings & errors only

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: lee-to/ai-factory
Path: examples/extensions/aif-ext-hello/skills/aif-hello-world/SKILL.md
Commit: ac92beb

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.