Cowork Plugin Customization

Customize a plugin for a specific organization, either by setting up a generic plugin template for the first time, or by tweaking and refining an already-configured plugin.

Target format: this skill customizes Claude Code / Cowork plugin packages (.claude-plugin/plugin.json + skills/ ...). That is the deliverable format, distinct from the Octop expert-library format (manifest.json); do not conflate the two.

Finding the plugin: The plugin's source files live inside this workspace. Ask the user which directory holds the plugin, or search the workspace for .claude-plugin/plugin.json to locate it, then read its files to understand its structure before making changes. If the plugin is not in the workspace yet, ask the user to upload or provide its files first, do not abort.

Determining the Customization Mode

After locating the plugin, check for ~~-prefixed placeholders: grep -rn '~~\w' /path/to/plugin --include='*.md' --include='*.json'

Default rule: If ~~ placeholders exist, default to Generic plugin setup unless the user explicitly asks to customize a specific part of the plugin.

1. Generic plugin setup, The plugin contains ~~-prefixed placeholders. These are customization points in a template that need to be replaced with real values (e.g., ~~Jira → Asana, ~~your-team-channel → #engineering).

2. Scoped customization, No ~~ placeholders exist, and the user asked to customize a specific part of the plugin (e.g., "customize the connectors", "update the standup skill", "change the ticket tool"). Read the plugin files to find the relevant section(s) and focus only on those. Do not scan the entire plugin or present unrelated customization items.