create-cowork-plugin

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

Guide creation of Cowork desktop plugins with manifest files and MCP configurations.

1|Updated Jan 17, 2026

Search Tags:#developer tools #code generation #scaffolding #plugin development #extension development #cowork

Ready to run

npx skills add https://github.com/juandaniel190/personal-projects --skill create-cowork-plugin-juandaniel190

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-cowork-plugin
Source: https://github.com/juandaniel190/personal-projects/tree/main/.claude/.claude_backup/skills/tools/create-cowork-plugin
Command: npx skills add https://github.com/juandaniel190/personal-projects --skill create-cowork-plugin-juandaniel190

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of new plugins for the Cowork desktop application, guiding users through the entire development process from concept to a packaged .plugin file.

Core Features & Use Cases

Guided Development: Walks users through discovery, planning, design, implementation, and packaging.
Plugin Architecture: Encodes best practices for directory structure, manifest files, and component schemas.
Use Case: A user wants to create a plugin that integrates with their company's internal ticketing system. This Skill will help them define commands, skills, and potentially MCP servers needed for the integration, ultimately producing a functional .plugin file.

Quick Start

Use the create-cowork-plugin skill to start building a new plugin for Cowork.

Frequently Asked Questions about create-cowork-plugin

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

FAQPage Schema

How do I build a custom plugin for the Cowork desktop application?▼

To build a Cowork plugin, you need a guided development process covering discovery, component planning, design, implementation, and packaging to generate the final .plugin file. The workflow ensures correct manifest files and component schemas are created.

What components can I include when developing a Cowork extension?▼

When developing a Cowork extension, you can configure commands, skills, agents, hooks, and MCP server configurations. The plugin architecture supports these components alongside the required manifest files and directory structure.

Do I need a specific directory setup to generate a packaged .plugin file?▼

Generating a packaged .plugin file requires access to an outputs directory for delivering the final build. This directory is where the packaged plugin is placed after the implementation and packaging stages are complete.

What is the best way to structure a plugin manifest for Cowork?▼

The best way to structure a plugin manifest for Cowork is to follow encoded best practices for directory structure and component schemas. The guided process helps you define the manifest files alongside commands, skills, and MCP servers.

Can I integrate an internal ticketing system into a Cowork plugin?▼

You can integrate an internal ticketing system by using this plugin development process to define the necessary commands, skills, and MCP servers. It guides you from concept through packaging to produce a functional .plugin file for the integration.