cowork-plugin-customizer_skill

Overview

This skill personalizes a Claude Cowork plugin to match an organization's tools, workflows, and configuration values. It updates plugin files with real tool names, workspace IDs, and team conventions, then packages the customized plugin for installation. The skill requires Cowork mode with mounted plugin directories and will not run in remote or standard CLI sessions.

How this skill works

The skill scans the plugin source files to locate lines and values marked for customization, then gathers organization context from connected knowledge sources. It builds a clear todo list of replacements, applies changes when answers are available, and prompts for any missing information. Finally, it updates plugin MCP configuration for identified tools and packages the plugin as a .plugin file in the outputs folder.

When to use it

• You want a generic plugin adapted to your company’s tools and naming conventions.
• You need workspace IDs, project names, or team identifiers filled into a plugin.
• You want the plugin to reference your organization’s chat channels or ticketing tools.
• You plan to connect MCPs for company tools and persist those connections in the plugin.

Best practices

• Run this only in the desktop Cowork mode with plugin directories mounted; abort if running remotely.
• Gather internal documentation, chat histories, and onboarding guides before changing files.
• Do not rename the plugin, its directory, or the skill name — only replace configurable values.
• Record all findings and show them to stakeholders before applying irreversible edits.
• Zip the final plugin in /tmp/ then copy the .plugin file to the outputs folder to avoid permission issues.

Example use cases

• Replace generic task-tracker references with Asana workspace and project IDs and update example URLs.
• Turn a standup helper template into a team-specific workflow that posts to the engineering Slack channel.
• Configure MCP entries for CI, issue tracking, and documentation services so the plugin can access them.
• Prepare a packaged plugin for distribution to a department with company-specific naming and statuses.