create-cowork-plugin

Creating a Claude Cowork plugin involves scaffolding the directory structure, defining the plugin manifest, designing required skills, and packaging everything into an installable .plugin artifact. A guided workflow interactively walks you through discovery, design, and implementation phases to produce the final file.

A Cowork plugin requires a specific directory structure with a required manifest file at a defined location. You must use kebab-case naming conventions and define skills with optional references so the Cowork UI can automatically discover and load them.

Packaging a Cowork plugin into an installable artifact requires a Cowork environment with access to the outputs directory. The guided workflow completes a review phase to validate your component choices before delivering the final .plugin file to that directory.

You can design custom skills and include optional references within your new Cowork plugin. The creation workflow guides you through component planning interactively, ensuring your architecture and skill definitions align with Cowork UI discovery conventions.

You need a Cowork environment with access to the outputs directory to scaffold and package a plugin. This environment access is required so the creation workflow can validate your manifest conventions and deliver the final installable .plugin file.

Scaffolding a Cowork plugin requires strict kebab-case naming for the plugin and components. The workflow enforces required manifest conventions and a structured interactive process across discovery, design, implementation, and review phases, limiting freeform architectural deviations.