$ loading_
Guide users to build a plugin from scratch and deliver a .plugin file.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "create-cowork-plugin" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/cowork-plugin-management/skills/create-cowork-plugin/SKILL.md 2. Save it as ~/.claude/skills/create-cowork-plugin/SKILL.md 3. Reload skills and tell me it's ready
In cowork mode, help me create a plugin from scratch that reads CSV files and generates summaries. First define the functionality and inputs/outputs, then scaffold it step by step, and place the final deliverable .plugin file in the outputs directory.
A step-by-step collaborative build process, including plugin design, scaffolding, and a final generated .plugin file.
Help me design and develop a new plugin that lets the team input meeting notes and automatically extract action items. Complete requirement shaping, plugin scaffolding, and packaged output in a cowork session.
A plugin solution for processing meeting notes, plus a directly deliverable plugin file.
I want to quickly prototype a plugin that takes product requirement text and outputs draft test cases. Guide me from a blank start and generate the final .plugin file in the outputs directory.
A plugin creation flow from requirements to prototype implementation, with a testable .plugin output file.
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.
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:
.plugin fileNontechnical 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.
Every plugin follows this layout:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Required: plugin manifest
├── skills/ # Skills (subdirectories with SKILL.md)
│ └── skill-name/
│ ├── SKILL.md
│ └── references/
├── agents/ # Subagent definitions (.md files)
├── .mcp.json # MCP server definitions
└── README.md # Plugin documentation
Legacy
commands/format: Older plugins may include acommands/directory with single-file.mdslash commands. This format still works, but new plugins should useskills/*/SKILL.mdinstead — the Cowork UI presents both as a single "Skills" concept, and the skills format supports progressive disclosure viareferences/.
Rules:
.claude-plugin/plugin.json is always requiredskills/, agents/) go at the plugin root, not inside .claude-plugin/Located at .claude-plugin/plugin.json. Minimal required field is name.
{
"name": "plugin-name",
"version": "0.1.0",
"description": "Brief explanation of plugin purpose",
"author": {
"name": "Author 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.
Custom component paths can be specified (supplements, does not replace, auto-discovery):
{
"commands": "./custom-commands",
"agents": ["./agents", "./specialized-agents"],
"hooks": "./config/hooks.json",
"mcpServers": "./.mcp.json"
}
Detailed schemas for each component type are in references/component-schemas.md. Summary:
| Component | Location | Format |
|---|---|---|
| Skills | skills/*/SKILL.md | Markdown + YAML frontmatter |
| MCP Servers | .mcp.json | JSON |
| Agents (uncommonly used in Cowork) | agents/*.md | Markdown + YAML frontmatter |
| Hooks (rarely used in Cowork) | hooks/hooks.json | JSON |
| Commands (legacy) | commands/*.md | Markdown + YAML frontmatter |
This schema is shared with Claude Code's plugin system, but you're creating a plugin for Claude Cowork, a desktop app for doing knowledge work.
Cowork users will usually find skills the most useful. Scaffold new plugins with skills/*/SKILL.md — do not create commands/ unless the user explicitly needs the legacy single-file format.
…
Embed Zoom Virtual Agent chat on web with secure controls and context updates.
Quickly add Zoom’s prebuilt React video UI to web workflows.
Create stakeholder updates tailored to audience, cadence, and communication goals.
Review an analysis for methodology, accuracy, bias, and evidence support.
Generate people analytics reports on headcount, attrition, diversity, and org health.
Identify, categorize, and prioritize technical debt for smarter refactoring decisions.
Create and scaffold Codex plugin folders, configs, and marketplace metadata entries.
Build, update, test, and release Claude Code plugins efficiently end to end.
Customize Claude Code plugins for organization-specific tools, connectors, and workflows.
Create reusable SKILL.md skills that package repeatable workflows for future use.
Create or update skills that extend Codex with knowledge, workflows, and tools.
Guide users to co-author docs, proposals, and specs through iterative refinement.