skill-registry

Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

87%

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

The body is concise, well-organized, and actionable with concrete field names and a clear execution sequence. The main gap is the absence of an explicit validation checkpoint between writing the registry and reporting completion.

Suggestions

Add an explicit validation step between writing .atl/skill-registry.md and reporting results (e.g. verify the file exists and skill count matches the scan) to strengthen the workflow.

Confirm the two References paths (docs/skill-style-guide.md, skills/_shared/skill-resolver.md) exist in the bundle or mark them as external repo paths to avoid dead references.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-structured with no concept explanations or padding; every section (Hard Rules, Decision Gates, Execution Steps, Output Contract) earns its place and assumes Claude's competence.	3 / 3
Actionability	Execution Steps give concrete, specific guidance with exact keys and paths (topic_key, capture_prompt, .atl/skill-registry.md); as an instruction-only skill the absence of code is not penalized because the guidance is actionable.	3 / 3
Workflow Clarity	A clear 5-step sequence is present with a Decision Gates table for branching, but there is no explicit validation checkpoint confirming the registry was written correctly before reporting success.	2 / 3
Progressive Disclosure	Under 50 lines with clearly organized sections and two clearly signaled, one-level-deep references, satisfying the simple-skill allowance for level 3.	3 / 3
	Total	11 / 12 Passed

Description

75%

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 clearly states what the skill does and when to use it, with an explicit trigger clause and a distinct niche. It is slightly thin on concrete actions and could broaden trigger-term coverage beyond the mechanical 'Trigger:' prefix.

Suggestions

Replace the mechanical 'Trigger:' prefix with a natural 'Use when...' phrasing and add common variants like 'after installing or removing skills'.

Expand the capability statement to list a couple of concrete actions (e.g. 'scan skill directories, extract triggers, write .atl/skill-registry.md') to reach level-3 specificity.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Index available skills by trigger and path') but lists only a single indexing action rather than multiple specific concrete actions like the level-3 anchor.	2 / 3
Completeness	Explicitly answers both what ('Index available skills by trigger and path') and when ('Trigger: ... after skill changes'), matching the level-3 anchor with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes some relevant natural terms ('update skills', 'skill registry', 'after skill changes') but the mechanical 'Trigger:' prefix and the narrow Spanish variant 'actualizar skills' leave coverage of common variations incomplete.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (skill registry indexing) with distinct triggers unlikely to collide with unrelated skills.	3 / 3
	Total	10 / 12 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: Gentleman-Programming/gentle-ai
Path: internal/assets/skills/skill-registry/SKILL.md
Commit: e01b114

Reviewed: about 15 hours 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.