CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-registry

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./internal/assets/skills/skill-registry/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 instruction set with a concrete command, a decision table, and a defined output contract — a strong example of an instruction-only skill. Its main weaknesses are dangling references (both cited files are missing from the bundle) and the lack of a recovery loop after a failed refresh.

Suggestions

Ship the two referenced files in the bundle (e.g., under references/skill-style-guide.md and references/skill-resolver.md) or remove the References section entirely — both paths currently dangle, breaking navigation.

Add a recovery step after a failed or skipped refresh (e.g., fall back to the read-only hand scan for inspection, or retry with diagnostics) to close the feedback loop in Execution Steps.

Briefly gloss or localize "Pi's effective session view" and "Engram" — a one-clause note on where they come from would make the Hard Rules about them actionable for any reader.

DimensionReasoningScore

Conciseness

The body is lean and operational with no explanations of concepts Claude already knows ("The registry is an index, not a compiler or summary"). Minor duplication — the refresh command and hand-scan fallback each appear in both Hard Rules and Execution Steps — keeps it below the anchor-5 "every token earns its place" bar.

4 / 5

Actionability

Concrete executable guidance throughout: an exact command with flags ("gentle-ai skill-registry refresh --cwd <project>"), a precise output path (.atl/skill-registry.md), a decision table, and a defined output contract. Minor gaps: "Pi's effective session view" and "Engram" are used without saying where they live or how to read them.

4 / 5

Workflow Clarity

Four sequenced execution steps with a failure branch ("If skipped (not a project), unavailable, or failed, report that outcome") and decision gates covering ambiguity. Not 5: there is no recovery loop after a failed refresh — it only reports — and no verification that the produced index is usable before returning it.

4 / 5

Progressive Disclosure

Sections are well organized and the References are clearly signaled one level deep with one-line descriptions, but both referenced files (docs/skill-style-guide.md, skills/_shared/skill-resolver.md) are absent from the bundle — no references/, scripts/, or assets/ directories exist. Scored against the actual bundle structure, the navigation chain breaks at the point of use, which is more than a minor organization gap.

3 / 5

Total

15

/

20

Passed

Description

58%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 states a clear what and an explicit when, with natural trigger phrases including a Spanish synonym. Its weaknesses are single-action coverage, missing common trigger variations (add/install/remove, skill index, list skills), and a broad "update skills" trigger that risks firing for skill-editing requests rather than registry reindexing.

Suggestions

List the skill's main actions in the description — refresh the shared index, resolve duplicate skills, pass exact SKILL.md paths to delegators — instead of only "Index available skills by trigger and path".

Add natural trigger variations users would actually say: "add/install/remove skills", "skill index", "list skills", alongside the existing "update skills" and "skill registry".

Narrow the "update skills" trigger to something like "after installing, removing, moving, or renaming skills" so it does not fire when users merely want to edit a skill's content.

DimensionReasoningScore

Specificity

"Index available skills by trigger and path" names a clear domain with one concrete action, but coverage stops there — the refresh, deduplication, and delegation behaviors the body actually performs are absent. Not 2 because the action is concrete rather than generic; not 4 because only a single action is listed.

3 / 5

Completeness

Both what ("Index available skills by trigger and path") and when ("Trigger: ... after skill changes") are explicitly present, so this clears the 'Use when' cap. Not 5 because the when-clause is narrow — it doesn't mention installing, removing, creating, moving, or renaming skills, which the body's activation contract covers.

4 / 5

Trigger Term Quality

"update skills, skill registry, actualizar skills, after skill changes" are natural phrases a user would say (including a Spanish synonym), but common variations like "add/install/remove a skill", "skill index", or "list skills" are missing. Coverage of the domain's natural terms is incomplete, matching anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

"skill registry" and "index available skills" carve a distinct niche, but the "update skills" trigger would naturally fire when a user wants to edit a skill's content — a different task — creating genuine overlap with skill-authoring skills. The overlap is more than minor, so anchor 3 fits better than 4.

3 / 5

Total

13

/

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.

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

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.