create-cowork-plugin

Name: create-cowork-plugin
Availability: InStock
Author: sun2443

Guide creation of Claude Cowork plugins packaged as installable .plugin artifacts.

Updated Apr 8, 2026

Search Tags:#automation #packaging #skill design #cowork #plugin scaffolding #guided workflow #plugin manifest

Ready to run

npx skills add https://github.com/sun2443/designer-skills --skill create-cowork-plugin-sun2443

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-cowork-plugin
Source: https://github.com/sun2443/designer-skills/tree/main/cowork-plugin-management/skills/create-cowork-plugin
Command: npx skills add https://github.com/sun2443/designer-skills --skill create-cowork-plugin-sun2443

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Users often need a reliable way to turn an idea for a Claude Cowork plugin into a working, installable plugin without guessing the architecture, file layout, or workflow steps.

Core Features & Use Cases

End-to-end guided plugin creation: Walks through discovery, component planning, design questions, implementation, and review/packaging to produce a ready-to-install .plugin file.
Correct plugin architecture by default: Instructs on the expected directory structure, required manifest location, and how to define skills (with optional references) so the Cowork UI can discover them.
Safe, user-aligned interaction style: Keeps conversation in plain language while guiding the user toward concrete plugin decisions and validations.

Quick Start

Use create-cowork-plugin to guide the creation of a new plugin from your requirements, ending with an installable .plugin file.

Frequently Asked Questions about create-cowork-plugin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a Claude Cowork plugin from scratch?▼

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.

What is the required directory structure and manifest format for a Cowork plugin?▼

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.

How do I package a Cowork plugin into an installable artifact?▼

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.

Can I design custom skills and references within a new Cowork plugin?▼

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.

Do I need a specific environment to scaffold and package a Cowork plugin?▼

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.

What are the limitations when scaffolding a Cowork plugin?▼

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.