skill

To validate YAML frontmatter, run the validation command to enforce lowercase kebab-case naming and check frontmatter parity across source and plugin mirror files. This catches mismatched definitions before workflow execution.

Plugin skills drift from canonical source definitions when changes are made without syncing. Running the sync command updates the plugin mirror to match the canonical skills tree, ensuring installed availability matches source definitions.

The best way to manage kebab-case skill definitions is using structured inputs for mutations and enforcing lowercase naming. This approach maintains the skill surface by safely adding, editing, and removing skills before syncing to the plugin mirror.

Yes, you can search existing skills before adding a new workflow capability. Searching the canonical skills tree helps identify similar definitions, allowing you to validate parity and sync new skills without duplicating effort.

Yes, skill validation requires structured inputs for mutations like adding and removing files. This ensures controlled modifications to the skills tree, enforcing required YAML frontmatter and parity checks before publishing.