How to Install Individual Plugins vs the Entire Marketplace in PM Skills

You can either deploy all nine product management plugins by installing the entire PM Skills marketplace, or selectively install individual plugins after registering the marketplace root to minimize your installation footprint.

The PM Skills repository (phuryn/pm-skills) is structured as a plugin marketplace containing nine independent domain-specific tools. Understanding how to install individual plugins vs the entire marketplace gives you flexibility to either access the complete skill set or restrict your environment to only the capabilities you actively use.

Understanding the PM Skills Architecture

The repository uses a two-level manifest system that distinguishes between the marketplace registry and individual plugin definitions.

At the root level, .claude-plugin/marketplace.json serves as the master manifest listing all nine available plugins. When you install the entire marketplace, the assistant reads this file and automatically resolves every plugin subdirectory.

Each plugin maintains its own manifest at pm-<plugin-name>/.claude-plugin/plugin.json. For example, pm-toolkit/.claude-plugin/plugin.json contains the specific configuration for the toolkit utilities, while pm-product-strategy/.claude-plugin/plugin.json defines the strategy and visioning capabilities. Installing individual plugins targets these specific files rather than the root marketplace manifest.

Installing the Entire Marketplace

Installing the complete marketplace registers the root manifest and automatically pulls all nine plugins in a single operation.

Claude Cowork UI Method

1. Open Customize → Browse plugins → Personal → +.
2. Select Add marketplace from GitHub and enter phuryn/pm-skills.

All nine plugins (including pm-toolkit, pm-product-strategy, pm-market-research, and others) become immediately available.

Claude Code CLI Method

claude plugin marketplace add phuryn/pm-skills

This command registers the marketplace and processes .claude-plugin/marketplace.json, resolving every plugin listed in the manifest.

Codex CLI Method

codex plugin marketplace add phuryn/pm-skills

Installing Individual Plugins

To install individual plugins vs the entire marketplace, you must first register the marketplace root (required one time), then invoke separate install commands for each specific plugin you need.

Claude Code Workflow

First, register the marketplace to make the plugin manifests available:

claude plugin marketplace add phuryn/pm-skills

Then install only the specific plugins you require:

claude plugin install pm-toolkit@pm-skills
claude plugin install pm-product-strategy@pm-skills
claude plugin install pm-ai-shipping@pm-skills

Codex Workflow

Register the marketplace once:

codex plugin marketplace add phuryn/pm-skills

Then add individual plugins selectively:

codex plugin add pm-toolkit@pm-skills
codex plugin add pm-market-research@pm-skills

This approach keeps your installation footprint minimal, loading only the domains (such as utilities, vision/roadmapping, or research) that you actively use.

Verifying Your Installation

Confirm which plugins are currently active in your environment:

claude plugin list

This displays all installed plugins, whether installed via the full marketplace or individually.

Summary

• Full marketplace install processes .claude-plugin/marketplace.json and automatically resolves all nine plugins in one operation.
• Individual plugin install requires first registering the marketplace root, then targeting specific plugins via their pm-<name>/.claude-plugin/plugin.json manifests.
• Claude Code uses claude plugin install <plugin-name>@pm-skills for individual selections.
• Codex CLI uses codex plugin add <plugin-name>@pm-skills for individual selections.
• Both workflows require the initial marketplace add command to register the phuryn/pm-skills source.

Frequently Asked Questions

Do I need to register the marketplace before installing individual plugins?

Yes. You must run claude plugin marketplace add phuryn/pm-skills (or codex plugin marketplace add phuryn/pm-skills) before installing individual plugins. This one-time registration makes the plugin manifests available to the assistant, even if you do not install the full marketplace.

Can I mix marketplace-wide and individual plugin installations?

Yes. You can start with individual plugins and later install the entire marketplace, or vice versa. The marketplace manifest simply ensures all nine plugins are available; individual install commands target specific plugin.json files regardless of prior installations.

What determines which plugins are available in the marketplace?

The root .claude-plugin/marketplace.json file defines the available plugin list. According to the source code, this manifest references nine independent plugins including pm-toolkit, pm-product-strategy, pm-market-research, pm-ai-shipping, and others. The CLAUDE.md specification details how these manifests must sync versions and dependencies.

How do I know which installation method is right for my workflow?

Install the entire marketplace if you need comprehensive product management capabilities across strategy, research, execution, and AI-assisted workflows. Install individual plugins if you work in constrained environments, need to minimize context window usage, or only require specific domains like the pm-toolkit for resume reviews and interview preparation.

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