hello-commit

Custom commit workflow that replaces the built-in aif-commit. Demonstrates the skill replacement feature of the extension system.

Quality

64%

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/hello-commit/SKILL.md

Quality

Content

72%

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

The skill body is appropriately lean and well-structured for a single-purpose task, but its workflow lacks executable detail on message formatting and a verification loop around the commit step. Tightening those would push it to full marks.

Suggestions

Show a concrete example of the desired commit message format (e.g., `[hello] feat: <subject>`) so step 3 is copy-paste ready.

Add a verification step before committing, such as re-checking `git diff --cached` and handling an empty staging area explicitly.

Specify what 'suggest staging' should propose (e.g., `git add <files>` or `git add -A`) so the guidance is actionable.

Dimension	Reasoning	Score
Conciseness	The body is lean — a one-line intro plus a five-step workflow — with no padding or explanation of concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	Concrete commands appear (`git status`, `git diff --cached`, `git commit`), but step 3 only says to "Generate a commit message with a [hello] prefix" without an example format, and "suggest staging" is vague, leaving guidance incomplete.	2 / 3
Workflow Clarity	Steps are sequenced and a confirmation checkpoint exists, but the workflow performs a write operation (`git commit`) with no verification/feedback loop (e.g., confirm staged content, handle a failed commit), which caps clarity at 2 per the destructive-operations guideline.	2 / 3
Progressive Disclosure	This is a simple under-50-line skill with no need for external references, and its two clearly-organized sections (intro + Workflow) satisfy the simple-skill exception for a top score.	3 / 3
	Total	10 / 12 Passed

Description

57%

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 clearly distinct, but it only implies when to use it and under-specifies the concrete commit actions it performs. Adding an explicit trigger clause and one or two specific actions would lift it.

Suggestions

Add an explicit "Use when..." clause naming the situations that should trigger this skill (e.g., committing staged changes or when the user wants a custom commit message).

List one or two concrete actions beyond 'replaces', such as 'generates commit messages with a [hello] prefix and runs git commit'.

Include common trigger variations like 'commit message' or 'git commit' so users naturally phrase requests that match.

Dimension	Reasoning	Score
Specificity	"Custom commit workflow that replaces the built-in aif-commit" names the domain (commit) and a concrete action (replaces), but does not enumerate multiple specific commit actions, so it sits at the 'names domain and some actions' anchor rather than the multi-action level.	2 / 3
Completeness	It clearly states what the skill does but lacks an explicit "Use when..." trigger clause, which per the guidelines caps completeness at 2 even though the 'what' half is answered.	2 / 3
Trigger Term Quality	It surfaces natural terms like "commit workflow" and "aif-commit" that a user might say, but misses common variations such as "commit message", "git commit", or "staged changes", so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	Tying it explicitly to replacing "the built-in aif-commit" carves out a distinct niche unlikely to be confused with generic commit helpers, matching the clear-niche anchor.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: lee-to/ai-factory
Path: examples/extensions/aif-ext-hello/skills/hello-commit/SKILL.md
Commit: 4b943ec

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.