How to Install Individual Plugins from the PM Skills Marketplace: A Complete Guide

You can install individual PM Skills plugins by first adding the marketplace repository with claude plugin marketplace add phuryn/pm-skills, then installing only the specific plugins you need using the claude plugin install <plugin-name>@pm-skills command.

The PM Skills Marketplace repository (phuryn/pm-skills) distributes nine specialized product management plugins as separate packages. While you can install the entire collection, most users prefer to install individual plugins from the PM Skills Marketplace to keep their Claude or Codex environment lean and focused on specific domains like discovery, strategy, or execution.

Prerequisites for Selective Installation

Before installing individual plugins, you must register the marketplace with your CLI tool. The marketplace manifest located at .claude-plugin/marketplace.json (lines 12-65) defines the nine available plugins and their metadata. Without adding this marketplace first, the individual plugin commands will fail to resolve the @pm-skills namespace.

Supported interfaces for individual plugin installation include:

• Claude Code (Anthropic's CLI)
• Codex CLI (OpenAI's command-line interface)
• Claude Cowork (GUI interface, though it defaults to bulk installation)

Installing Individual Plugins via Claude Code

For users of the Claude Code CLI, selective installation requires two distinct phases: marketplace registration and targeted plugin installation.

First, add the marketplace once:

claude plugin marketplace add phuryn/pm-skills

Then install only the specific plugins you need. For example, to install just the discovery and strategy tools:

claude plugin install pm-product-discovery@pm-skills
claude plugin install pm-product-strategy@pm-skills

As documented in README.md (lines 61-77), the full list of available individual plugins includes: pm-toolkit, pm-product-strategy, pm-product-discovery, pm-market-research, pm-data-analytics, pm-marketing-growth, pm-go-to-market, pm-execution, and pm-ai-shipping.

Batch Installation of Selected Plugins

To install multiple specific plugins without running separate commands for each, use a bash loop:

for plugin in pm-product-discovery pm-product-strategy pm-toolkit; do
  claude plugin install "${plugin}@pm-skills"
done

Installing Individual Plugins via Codex CLI

The OpenAI Codex CLI uses nearly identical syntax for individual plugin management. After registering the marketplace, use the codex plugin add command (note the syntax difference: add instead of install).

Add the marketplace:

codex plugin marketplace add phuryn/pm-skills

Install individual plugins:

codex plugin add pm-data-analytics@pm-skills
codex plugin add pm-execution@pm-skills

According to README.md (lines 80-97), this method pulls only the specified plugin directories (such as pm-data-analytics/ or pm-execution/) and their associated skill files from the repository.

Claude Cowork GUI Limitations

The Claude Cowork graphical interface automatically installs all nine plugins when you add the marketplace via Customize → Browse plugins → Personal → Add marketplace from GitHub (see README.md lines 50-58). As implemented in phuryn/pm-skills, the GUI workflow does not provide a native interface for selecting individual plugins during installation.

To use individual plugins in Claude Cowork, install via CLI first, then use the GUI to disable specific plugins, or accept the full installation and ignore unused plugin commands.

Available Individual Plugins

The marketplace exposes nine distinct packages covering specific product management domains. Each plugin maintains its own plugin.json manifest (e.g., pm-toolkit/.claude-plugin/plugin.json) and skills/ directory:

• pm-toolkit: Core utilities and frameworks
• pm-product-discovery: User research and brainstorming tools
• pm-product-strategy: Strategic planning and roadmap frameworks
• pm-market-research: Competitive analysis and market sizing
• pm-data-analytics: Metrics definition and analytical frameworks
• pm-marketing-growth: Growth hacking and marketing strategies
• pm-go-to-market: Launch planning and execution workflows
• pm-execution: Delivery management and agile frameworks
• pm-ai-shipping: AI-assisted development and shipping tools

Summary

• You must add the marketplace first: Run claude plugin marketplace add phuryn/pm-skills before installing individual plugins, as the CLI reads .claude-plugin/marketplace.json to resolve plugin locations.
• Use the @pm-skills suffix: All individual plugin commands require the namespace suffix (e.g., pm-toolkit@pm-skills).
• Claude Code uses install, Codex uses add: The syntax differs slightly between Anthropic's and OpenAI's CLI tools.
• Nine plugins available: The marketplace defined in lines 12-65 of marketplace.json exposes distinct packages covering discovery, strategy, execution, market research, analytics, marketing, go-to-market, toolkit, and AI shipping.
• GUI installs all: Claude Cowork lacks granular selection; use CLI workflows for individual plugin control.

Frequently Asked Questions

Can I install PM Skills plugins without adding the marketplace first?

No. The marketplace manifest at .claude-plugin/marketplace.json acts as the registry source. The CLI tools parse this file (specifically the "plugins" array at lines 12-65) to resolve plugin names and source locations. Without claude plugin marketplace add phuryn/pm-skills, the system cannot locate the @pm-skills namespace or download the individual plugin directories like pm-product-discovery/ or pm-execution/.

What is the difference between claude plugin install and codex plugin add?

claude plugin install is the Anthropic CLI command for adding plugins to Claude Code, while codex plugin add is the OpenAI CLI equivalent for Codex. Both perform the same function—downloading the specified plugin directory and registering its plugin.json manifest—but the command verbs differ between the two platforms. Both require the marketplace to be added first using the respective marketplace add command.

How do I know which individual plugin contains the skills I need?

Each plugin directory contains a skills/ subdirectory with markdown files defining specific capabilities. For example, pm-product-discovery/skills/ contains brainstorming and user research tools defined in files like brainstorm-ideas-new/SKILL.md, while pm-go-to-market/commands/ holds launch planning workflows. Consult the marketplace.json file at the repository root, which lists each plugin's description and source directory, or examine the individual plugin.json files within each plugin folder (e.g., pm-toolkit/.claude-plugin/plugin.json) for detailed capability listings.

Can I mix individual plugins from PM Skills with other marketplaces?

Yes. Once you add the phuryn/pm-skills marketplace, you can install individual plugins from it alongside plugins from other marketplaces. The @pm-skills namespace isolates these plugins from others. For example, you can run claude plugin install pm-ai-shipping@pm-skills alongside claude plugin install some-other-plugin@different-marketplace without conflict, as each plugin maintains its own isolated skill directory and command namespace.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}