How to Install PM Skills Marketplace Plugins for Claude Cowork: A Complete Guide

Add the repository phuryn/pm-skills to Claude Cowork via the Customize menu or CLI to instantly access 9 product management plugins bundled with domain-specific skills and slash commands.

The PM Skills Marketplace is a curated collection of Claude Cowork plugins designed specifically for product management workflows. By installing this marketplace from the phuryn/pm-skills repository, you gain immediate access to nine distinct plugins—including pm-toolkit, pm-execution, and pm-product-discovery—without needing to install each component individually. This guide covers both the UI-based installation for Claude Cowork and the CLI method for Claude Code, referencing the actual source structure and configuration files that power the integration.

Installation via Claude Cowork UI

The fastest way to install PM Skills Marketplace plugins is through the Claude Cowork graphical interface. This method automatically resolves all nine plugins defined in .claude-plugin/marketplace.json and registers their commands in your workspace.

Step-by-Step Installation

Follow these steps to add the marketplace to your Claude Cowork environment:

  1. Open Claude Cowork and locate the Customize button in the bottom-left corner of the interface.

  2. Select Browse plugins, then navigate to the Personal tab.

  3. Click the + (Add plugin) button.

  4. Choose Add marketplace from GitHub.

  5. Enter the repository identifier:

    phuryn/pm-skills
  6. Confirm the addition and wait for the installation to complete.

Once the spinner finishes, Claude Cowork downloads the marketplace definition from .claude-plugin/marketplace.json (lines 11-66) and automatically registers all nine plugins. You can verify the installation by typing any slash command, such as /discover, into the chat interface.

Installation via Command Line Interface

For users running Claude Code or preferring terminal-based workflows, you can install the marketplace using the CLI. This approach provides granular control over plugin installation.

Add the Full Marketplace

To register the entire marketplace and make all nine plugins available:

claude plugin marketplace add phuryn/pm-skills

Install Individual Plugins

After adding the marketplace, you can install specific plugins rather than the entire bundle. For example, to install only the toolkit plugin:

claude plugin install pm-toolkit@pm-skills

This method references the plugin definitions stored in subdirectories like pm-toolkit/ and pm-execution/, as documented in the repository's README.md (lines 64-80).

What Gets Installed: The Nine Plugins

When you install the PM Skills Marketplace, Claude Cowork pulls nine distinct plugin packages, each containing specialized skills and commands:

  • pm-toolkit: Core product management utilities and resume review tools
  • pm-execution: Sprint planning and delivery management workflows
  • pm-product-discovery: User research and discovery lifecycle management
  • pm-strategy: Product strategy canvas and roadmap generation
  • pm-prd: Feature specification and requirements documentation
  • pm-launch: Go-to-market planning and launch coordination
  • pm-metrics: Analytics and success metric definition
  • pm-stakeholder: Communication and alignment frameworks
  • pm-career: Career development and interview preparation

Each plugin follows a standardized structure with skills/ directories containing markdown knowledge modules and commands/ directories defining slash-command workflows.

Using Installed Plugins: Available Commands

After installation, the marketplace registers numerous slash commands in Claude Cowork's command registry. These commands chain multiple skills together to execute complex workflows.

Key commands available immediately:

  • /discover — Run a full product-discovery workflow
  • /strategy — Create a product-strategy canvas
  • /write-prd — Generate a PRD from a feature idea
  • /plan-launch — Build a GTM launch plan
  • /review-resume — Analyze and optimize product management resumes

When you invoke /discover AI-powered meeting summarizer for remote teams, Claude Cowork automatically loads the underlying skills from pm-product-discovery/skills/ and guides you through the discovery lifecycle without requiring manual skill selection.

Architecture and File Structure

Understanding how the PM Skills Marketplace integrates with Claude Cowork helps troubleshoot issues and customize workflows.

Marketplace Definition

The marketplace manifest at .claude-plugin/marketplace.json serves as the entry point. This JSON file lists all nine plugins, their source directories, and categorical metadata. Claude Cowork reads this file during installation to determine which plugin folders to pull from the repository.

Plugin Package Structure

Each plugin resides in its own subdirectory (e.g., pm-toolkit/, pm-execution/) and contains:

Skills vs. Commands

Skills are atomic knowledge units that can be invoked directly using the syntax /plugin-name:skill-name or automatically by commands. Commands are user-facing workflows that chain multiple skills together. For example, the /write-prd command might sequentially invoke skills for user-story generation, acceptance criteria definition, and technical requirement gathering.

Summary

  • Install via UI: Use Customize → Browse plugins → Personal → + → Add marketplace from GitHub → enter phuryn/pm-skills
  • Install via CLI: Run claude plugin marketplace add phuryn/pm-skills for the full bundle or claude plugin install pm-toolkit@pm-skills for specific tools
  • Automatic Registration: The marketplace JSON at .claude-plugin/marketplace.json (lines 11-66) defines all nine plugins, which are fetched and registered automatically
  • Immediate Usage: Access 9 plugins with commands like /discover, /strategy, and /write-prd immediately after installation completes
  • No Configuration Required: Claude Cowork handles skill loading and command registration automatically based on the repository structure

Frequently Asked Questions

Do I need to install each plugin individually after adding the marketplace?

No. When you add the phuryn/pm-skills repository as a marketplace, Claude Cowork reads the .claude-plugin/marketplace.json file and automatically installs all nine plugins listed in the manifest. You only need to install individual plugins if you initially added the repository via CLI and want to select specific tools rather than the full bundle.

Can I use these plugins in standard Claude Code without Cowork?

Yes. The plugins work in standard Claude Code environments through the CLI installation method. Use claude plugin marketplace add phuryn/pm-skills to register the marketplace, then invoke commands using the slash-command syntax. The underlying skills and commands function identically regardless of whether you use the Cowork UI or the command-line interface.

Where are the skill definitions stored in the repository?

Each plugin stores its skills in dedicated skills/ subdirectories. For example, the resume review skill resides at pm-toolkit/skills/review-resume/SKILL.md. These markdown files contain the domain-specific knowledge that Claude uses when executing commands. You can reference these files directly to understand the exact prompting logic and knowledge boundaries for each capability.

How do I update the plugins when the repository changes?

Claude Cowork periodically checks for updates to registered marketplaces. When the phuryn/pm-skills repository updates its marketplace.json or plugin definitions, your installation will sync automatically. For CLI users, run claude plugin marketplace update phuryn/pm-skills to pull the latest versions of the skills and commands defined in the repository.

Have a question about this repo?

These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:

Share the following with your agent to get started:
curl -s "https://instagit.com/install.md"

Works with
Claude Codex Cursor VS Code OpenClaw Any MCP Client

Maintain an open-source project? Get it listed too →