create-cowork-plugin

Guide the creation of a Claude Cowork plugin from discovery to packaged .plugin file.

2|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/rakibulism/agent-skills-os --skill create-cowork-plugin-rakibulism
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-cowork-plugin
Source: https://github.com/rakibulism/agent-skills-os/tree/main/skills/cowork-plugin-management-create-cowork-plugin
Command: npx skills add https://github.com/rakibulism/agent-skills-os --skill create-cowork-plugin-rakibulism

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users create a new Claude Cowork plugin from scratch without needing to know the plugin format up front. It turns an open-ended idea into a structured plugin plan, implementation, validation, and packaged deliverable.

Core Features & Use Cases

  • Discovery and Scope Definition: Clarifies what the plugin should do, who will use it, and what external tools it needs.
  • Component Planning and Design: Determines whether the plugin needs skills, agents, hooks, MCP servers, or connector placeholders.
  • Implementation Guidance: Directs the creation of the plugin manifest, component files, and README using the required schema.
  • Packaging and Validation: Ensures the plugin structure is checked and packaged as a ready-to-install .plugin file.
  • Use Case: A user says they want a plugin for managing cowork tasks, and this Skill walks them from the first idea to a finished plugin archive.

Quick Start

Ask the create-cowork-plugin skill to help design and build a new plugin from your idea.

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 Claude Cowork plugin from scratch?

Building a Claude Cowork plugin involves a guided scaffolding process that takes your idea from initial discovery through component planning, implementation, validation, and packaging into a ready-to-install .plugin file.

What components can I include when scaffolding a cowork plugin?

Scaffolding a cowork plugin allows you to include components such as skills, agents, hooks, MCP servers, or tool-agnostic connector placeholders based on your specific plugin requirements and scope.

Do I need Cowork desktop access to create and package a plugin?

You need Cowork desktop access to the outputs directory to validate the plugin structure and access the packaged .plugin file generated during the creation process.

How does the plugin creation process handle the manifest and README?

The plugin creation process directs the implementation of the plugin manifest (plugin.json), component files like SKILL.md, and the README using the required schema to ensure proper validation and packaging.

What is the best way to structure an idea into a packaged cowork plugin?

Structuring an idea into a packaged cowork plugin is best achieved through guided collaboration that clarifies scope, designs components, implements the schema, and packages the validated structure into a ready-to-install archive.