manage-skills

To manage agent skills across a repository, you can discover, add, update, and synchronize them using a lifecycle model that ensures consistency and safe synchronization between local overlays and upstream cores.

The best way to avoid duplicating skill work is to perform tiered searches across local repositories, shared commons, and public catalogs to locate existing skills before building new ones.

You track provenance for repository skills by applying frontmatter tracking, category alignment, and catalog integration rules to validate changes and ensure consistency within the governance surfaces.

You decide whether to vendor a skill or publish it to the commons by running a workflow that evaluates existing local and upstream skills, applying governance rules to determine the correct synchronization path.

Handling local overlays for upstream skill cores requires applying a synchronization lifecycle model that safely coordinates updates and maintains consistency between your local repository and shared catalogs.

Yes, you can validate skill frontmatter against a repository catalog inventory using validation tooling that ensures category alignment and enforces catalog integration rules for safe governance.