plugin-packaging

To package a workspace as a distributable plugin, validate its structural integrity for skills, agents, and commands, dynamically generate a manifest with component counts, and compress the package into a tar.gz archive.

Manifest generation works by dynamically counting the validated skills, agents, and commands within your workspace, then writing those accurate component counts directly into a plugin.json file for distribution.

Plugin structure validation checks that all skills, agents, and commands adhere to defined formatting and line limits, ensuring structural integrity is enforced before the manifest is updated and the package is compressed.

Yes, you can use this packaging process to automatically check for structural errors, update the plugin manifest with the latest component counts, and create a ready-to-distribute package before releasing a new version.

The best way to export a PM-Workspace plugin is to orchestrate validation, manifest updates, and reporting together, finishing with compression into a tar.gz file for a complete plugin export.

Your plugin export fails validation during packaging when skills, agents, or commands do not adhere to defined formatting and line limits, halting the dynamic manifest generation and compression process.