share-skill

To promote a local skill to the shared engine on Google Drive, run the share-skill command with your skill name. The workflow enforces frontmatter validation, discovers the engine path, and publishes the skill for centralized team access.

Publishing a skill requires frontmatter validation that checks for a mandatory Skill name and description. The promotion workflow applies these gate checks to ensure consistency and governance before loading the skill into the shared engine.

Yes, promoting a skill to the shared engine supports optional scripts, references, and assets directories. The promotion process transfers these components alongside the validated skill file to ensure full functionality on the target drive.

Gate-driven promotion applies standards checks and authority loading to ensure consistency across projects. This governance mechanism verifies permissions and enforces validation rules before a local skill is published to the shared engine.

Centralizing skills into a shared engine on Google Drive enables cross-project collaboration, auditing, and reuse. Using a gate-driven promotion workflow ensures that only properly validated skills are published to the shared library.

Skill promotion fails when frontmatter validation requirements are not met. A skill must have a valid name and description, and the workflow must successfully discover the Google Drive engine path before the promotion can proceed.