meta-skill-catalog

To audit your AI skill inventory, invoke the catalog scanning feature to report on the status of all installed skills and identify any missing or stale entries. This process synchronizes metadata between the file system and the central registry to ensure compliance.

Skill catalog configuration drift occurs when the file system state diverges from the central registry metadata. Synchronizing the catalog.json file with the actual file system state rebuilds the inventory and resolves these metadata inconsistencies for reliable execution.

You validate AI skill naming conventions and versioning compliance by running a quality audit on the skill definitions. This auditing process checks structural standards and description clarity to ensure all registered skills adhere to the required project specifications.

The best way to synchronize skill metadata with a central registry is by rebuilding the catalog.json file. This action scans the file system and updates the central inventory, maintaining a single source of truth and preventing configuration drift across your installed skills.

Yes, catalog auditing is designed to manage a growing library of installed AI capabilities. It provides a single source of truth for all registered skills, automatically scanning and validating metadata to ensure structural standards and consistency at scale.

You should avoid an automated skill catalog rebuild when manually editing the central registry and needing to preserve unsynchronized file system changes. Running the rebuild process will overwrite manual registry entries by synchronizing metadata directly from the file system.