Agent skill · writing content · anthropics
create-cowork-plugin
Guide users through creating a new plugin from scratch in a cowork session. Use when users want to create a plugin, build a plugin, make a new plugin, develop a plugin, scaffold a plugin, start a plugin from scratch, or design a plugin. This skill requires Cowork mode with access to the outputs directory for delivering the final .plugin file.
Why this skill is useful
Adds a structured five-phase workflow and detailed plugin architecture that enables the AI to generate a fully functional plugin from scratch, which it cannot do on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.
What this skill does
Create Cowork Plugin Build a new plugin from scratch through guided conversation. Walk the user through discovery, planning, design, implementation, and packaging — delivering a ready-to-install .plugin file at the end. Overview A plugin is a self-contained directory that extends Claude's capabilities with skills, agents, hooks, and MCP server integrations. This skill encodes the full plugin architecture and a five-phase workflow for creating one conversationally. The process: 1. Discovery — understand what the user wants to build 2. Component Planning — determine which component types are needed 3. Design & Clarifying Questions — specify each component in detail 4. Implementation — create all plugin files 5. Review & Package — deliver the .plugin file Nontechnical output: Keep all user-facing conversation in plain language. Do not expose implementation details like file paths, directory structures, or schema fields unless the user asks. Frame everything in terms of what the plugin will do. Plugin Architecture Directory Structure Every plugin follows this layout: Legacy commands/ format: Older plugins may include a commands/ directory with single-file .md slash commands. This format still works, but new plugins should use skills//SKILL.md instead — the Cowork UI presents both as a single "Skills" concept, and the skills format supports progressive disclosure via references/. Rules: .claude-plugin/plugin.json is always required Component directories (skills/, agents/) go at the plugin root, not inside .claude-plugin/ Only create directories for components the plugin actually uses Use kebab-case for all directory and file names plugin.json Manifest Located at .claude-plugin/plugin.json. Minimal required field is name. Name rules: kebab-case, lowercase with hyphens, no spaces or special characters. Version: semver format (MAJOR.MINOR.PATCH). Start at 0.1.0. Optional fields: homepage, repository, license, keywords. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/create-cowork-plugin