skill-catalog-builder

Build a bounded Agent Skill catalog across explicit discovery scopes and report collisions before loading instruction bodies.

Quality

75%

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 ./phases/13-tools-and-protocols/24-skill-discovery-and-progressive-disclosure/outputs/skill-catalog-builder/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 concise, well-structured, and points cleanly to real one-level-deep bundle files with a clear sequenced workflow and an activation checkpoint. Its only gap is placeholder command arguments and the absence of an explicit error-recovery loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no padding or explanation of concepts Claude already knows; every line (numbered steps, two guard rules, a return statement) earns its place.	5 / 5
Actionability	Provides a concrete executable command ('python3 scripts/build_catalog.py project=PATH user=PATH') and names specific files/arrays, but uses PATH placeholders and delegates detail to references, leaving minor gaps.	4 / 5
Workflow Clarity	A clear five-step sequence with an explicit checkpoint (step 4: 'Inspect the JSON collisions and omitted arrays before activating a skill'); no full validate-fix-retry loop, so it stops just short of 5.	4 / 5
Progressive Disclosure	A short overview body with three clearly signaled, one-level-deep references (references/discovery-contract.md, assets/scope-policy.json, scripts/build_catalog.py), all verified to exist as real files.	5 / 5
	Total	18 / 20 Passed

Description

53%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 specific and occupies a clear niche, but lacks an explicit 'when to use' trigger clause and relies on somewhat technical jargon over natural user phrases. It sits at a solid mid-range quality.

Suggestions

Append an explicit 'Use when…' clause naming natural trigger phrases (e.g., 'Use when an agent host must discover skills across multiple directories or resolve duplicate/conflicting skills').

Swap jargon like 'discovery scopes' and 'instruction bodies' for user-natural synonyms ('skill directories', 'duplicate skills') to improve trigger-term quality.

Add a concrete trigger mentioning file extensions or common phrasings users actually say when they need this skill.

Dimension	Reasoning	Score
Specificity	Names the domain (Agent Skill catalog) and two concrete actions — 'Build a bounded Agent Skill catalog' and 'report collisions' — but coverage is not comprehensive, matching the '1-2 concrete actions' anchor.	3 / 5
Completeness	The 'what' is clear (build catalog, report collisions before loading bodies) but there is no 'Use when…' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords like 'catalog', 'collisions', and 'discovery scopes' appear but lean technical; common natural synonyms a user would say ('find skills', 'duplicate skills', 'conflicting skills') are missing.	3 / 5
Distinctiveness Conflict Risk	The skill occupies a clear niche (deterministic multi-scope skill discovery with collision reporting) with distinct triggers and only minor overlap risk with closely related skills.	4 / 5
	Total	13 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rohitg00/ai-engineering-from-scratch
Path: phases/13-tools-and-protocols/24-skill-discovery-and-progressive-disclosure/outputs/skill-catalog-builder/SKILL.md
Commit: c02ca08

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.