hello-commit

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

Quality

65%

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

86%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 a lean, well-structured workflow with exact git commands and a confirmation checkpoint before the destructive step — an exemplary token-efficient skill body for a simple task. Its only real gap is the absence of a concrete commit-message example and any failure-handling guidance.

Dimension	Reasoning	Score
Conciseness	The body is ~18 lines with zero padding: one orienting sentence ("This skill replaces the built-in `aif-commit` to demonstrate the `replaces` feature.") and a five-step workflow with exact commands. Every token earns its place and nothing explains concepts Claude already knows, matching anchor 5.	5 / 5
Actionability	Three exact commands are given ("git status", "git diff --cached", "git commit") plus a concrete message prefix rule ("[hello] prefix"), but there is no example of the commit message format and "suggest staging" is high-level direction. This is mostly executable guidance with minor gaps — anchor 4, not 5, because a copy-paste-ready message template/example is missing.	4 / 5
Workflow Clarity	The five steps are clearly sequenced and include a human checkpoint ("Ask for confirmation") before the commit, matching anchor 4. It falls short of anchor 5 because there is no error-recovery guidance (e.g. what to do if the commit fails or the message is rejected), though the confirmation step keeps it above anchor 3's 'checkpoints missing or implicit'.	4 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, references no external files (and no references/scripts/assets bundle exists), and is organized into a clean intro plus a Workflow section. Per the rubric's simple-skill guideline, this earns a 5 with just well-organized sections.	5 / 5
	Total	18 / 20 Passed

Description

45%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 communicates the skill's purpose (a custom commit workflow replacing aif-commit) concisely, but it omits any trigger guidance and lists no concrete capabilities beyond the replacement relationship. It reads as a demo note rather than a discovery-oriented description.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to commit staged changes or write a commit message', to satisfy the completeness and trigger-term dimensions.

State the concrete capabilities, e.g. 'Reviews staged changes with git status/git diff --cached, generates a [hello]-prefixed commit message, and commits after user confirmation'.

Include natural trigger phrases users would actually say ("commit", "commit message", "write a commit") and drop the meta commentary about demonstrating the extension system, which adds no triggering value.

Dimension	Reasoning	Score
Specificity	"Custom commit workflow" names the domain, but the only stated action is "replaces the built-in aif-commit", which describes a relationship rather than a user-facing capability; no concrete actions like generating commit messages are listed. This matches anchor 2 (domain named, actions minimal or generic) better than anchor 3, which expects 1-2 concrete capability actions.	2 / 5
Completeness	There is a reasonably clear "what" ("Custom commit workflow that replaces the built-in aif-commit"), but the "when" is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Anchor 3 (clear what, when missing) is the exact match; not 4 because no when-clause exists at all.	3 / 5
Trigger Term Quality	Relevant keywords like "commit workflow" and "aif-commit" are present, but common natural variations users would say ("commit message", "write a commit", "git commit") are missing, and "skill replacement feature of the extension system" is technical jargon. This sits between anchor 2 (one or two generic keywords) and anchor 4 (good coverage), landing on 3.	3 / 5
Distinctiveness Conflict Risk	The niche (replacing a specific built-in, aif-commit) is somewhat distinct, but without any when-to-use guidance it could overlap with other commit-related skills. This matches anchor 3 (somewhat specific but could still overlap) rather than 4, which requires minor overlap risk with closely related skills.	3 / 5
	Total	11 / 20 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: 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.