How to Install and Configure PM Skills for Claude Code: Complete Setup Guide

You can install PM Skills by adding the phuryn/pm-skills marketplace via the Claude Code CLI (claude plugin marketplace add phuryn/pm-skills) or through the Claude Cowork UI, then installing individual plugins to access slash commands like /discover and /write-prd.

PM Skills is a comprehensive Claude Marketplace that bundles nine specialized plugins for product management workflows. According to the phuryn/pm-skills repository source code, this marketplace delivers frameworks, templates, and guided workflows as reusable skills and executable commands. Whether you prefer the graphical interface of Claude Cowork or the terminal-based Claude Code CLI, installing and configuring PM Skills requires just a few steps to unlock the full suite of product management capabilities.

What Is PM Skills?

PM Skills is organized as a marketplace—a collection of related plugins, each containing discrete skills (Markdown-based frameworks) and optional commands (slash-commands that chain skills together). When you add the marketplace at phuryn/pm-skills, Claude automatically ingests the metadata from .claude-plugin/marketplace.json to recognize all nine available plugin packages.

The nine plugins included are:

• pm-toolkit – Core utilities and templates
• pm-product-strategy – Strategic planning frameworks
• pm-product-discovery – User research and validation workflows
• pm-market-research – Competitive analysis tools
• pm-data-analytics – Metrics and measurement guides
• pm-marketing-growth – Growth and acquisition frameworks
• pm-go-to-market – Launch planning and execution
• pm-execution – Sprint and delivery management
• pm-ai-shipping – AI-specific shipping workflows

Each plugin folder (e.g., pm-toolkit/) contains a /.claude-plugin/plugin.json manifest that registers its specific skills and commands with Claude.

Installation Methods

You can install PM Skills through two interfaces: the Claude Cowork UI for non-developers or the Claude Code CLI for terminal-centric workflows.

Claude Cowork (UI Installation)

This method is recommended if you prefer graphical interfaces and want to install all nine plugins simultaneously.

1. Open the Customize pane (bottom-left corner of Claude Cowork).
2. Choose Browse plugins → Personal → +.
3. Click Add marketplace from GitHub and enter phuryn/pm-skills.

All nine plugins install automatically, immediately exposing commands such as /discover, /strategy, and /write-prd in your conversation context. The repository's README.md (lines 48-60) contains visual screenshots of this flow, and .docs/images/pm-skills-install.gif provides an animated guide.

Claude Code (CLI Installation)

For developers who prefer terminal control, use the Claude Code CLI to add the marketplace and selectively install plugins.

First, register the marketplace:

claude plugin marketplace add phuryn/pm-skills

Then install the specific plugins you need. To install all nine, run:

claude plugin install pm-toolkit@pm-skills
claude plugin install pm-product-strategy@pm-skills
claude plugin install pm-product-discovery@pm-skills
claude plugin install pm-market-research@pm-skills
claude plugin install pm-data-analytics@pm-skills
claude plugin install pm-marketing-growth@pm-skills
claude plugin install pm-go-to-market@pm-skills
claude plugin install pm-execution@pm-skills
claude plugin install pm-ai-shipping@pm-skills

These commands reference the exact syntax found in the repository's README.md (lines 61-77). After installation, the slash commands become available in any Claude Code session.

Configuration and File Structure

Understanding the underlying file structure helps you configure and customize PM Skills after installation.

Marketplace Configuration

The file .claude-plugin/marketplace.json in the repository root defines the marketplace metadata and lists all nine plugin packages. When you run claude plugin marketplace add, Claude parses this JSON to understand what plugins are available under the pm-skills namespace.

Plugin Manifests

Each plugin contains a /.claude-plugin/plugin.json file that specifies:

• Skills: Reusable frameworks stored as Markdown files under */skills/*/SKILL.md
• Commands: Claude-specific slash-commands defined in */commands/*.md

For example, pm-product-discovery/.claude-plugin/plugin.json registers the discovery workflow skills, while pm-product-discovery/commands/discover.md defines the /discover slash command implementation.

Cross-Platform Skill Reusability

The skills follow a universal Markdown format, making them portable to other AI assistants. Each SKILL.md file contains structured prompting frameworks that work with Gemini, OpenCode, and other compatible assistants. To extract skills for use outside Claude, copy the Markdown files from any pm-*/skills/ directory:

for plugin in pm-*/; do
  mkdir -p .opencode/skills/
  cp -r "$plugin/skills/"* .opencode/skills/ 2>/dev/null
done

This loop, documented in the repository's "Other AI assistants" section (README.md lines 122-133), ports the skills while ignoring command-specific metadata.

Using PM Skills After Installation

Once configured, interact with PM Skills through two mechanisms:

Slash Commands: Type / followed by the command name to execute chained workflows. Examples include:

• /discover [product idea] – Runs the product discovery framework
• /strategy – Generates strategic positioning documents
• /write-prd – Creates product requirement documents using built-in templates

Direct Skill Invocation: Reference specific skills by name in natural language, such as "What are the riskiest assumptions for our AI writing assistant idea?" This triggers the risk assessment framework from pm-product-discovery/skills/ without requiring the slash-command syntax.

Summary

• PM Skills is a Claude Marketplace containing nine product management plugins available at phuryn/pm-skills.
• Installation requires either adding the marketplace in Claude Cowork (UI) or running claude plugin marketplace add phuryn/pm-skills followed by claude plugin install commands in Claude Code.
• Configuration relies on .claude-plugin/marketplace.json for the marketplace definition and individual plugin.json files for skill registration.
• Skills are framework-agnostic Markdown files under */skills/*/SKILL.md, while commands are Claude-specific implementations in */commands/*.md.
• Portability: Skills can be extracted for use with other AI assistants by copying the Markdown files from plugin directories.

Frequently Asked Questions

Do I need to install all nine PM Skills plugins?

No. While the Claude Cowork UI installs all nine plugins automatically, the Claude Code CLI allows selective installation. You can install only pm-toolkit@pm-skills and pm-product-discovery@pm-skills if you only need core utilities and discovery workflows, then add others later using claude plugin install.

Can I use PM Skills with other AI assistants besides Claude?

Yes. The skills are stored as standard Markdown files in */skills/*/SKILL.md following a universal format. You can copy these files to other AI assistant directories (such as .opencode/skills/ for OpenCode) and use them without the slash-command infrastructure. However, the command chaining features are Claude-specific.

Where are the skill files stored locally after installation?

After running claude plugin install, Claude downloads the skill Markdown files and plugin manifests into its local plugin directory. The exact path depends on your Claude Code installation, but the content mirrors the repository structure: each plugin folder contains .claude-plugin/plugin.json and skill definitions that Claude references when executing commands.

How do I update PM Skills to the latest version?

Run claude plugin marketplace update phuryn/pm-skills to refresh the marketplace metadata, then claude plugin update with the specific plugin name (e.g., claude plugin update pm-toolkit@pm-skills) to pull the latest skill definitions. Since the marketplace uses a static JSON descriptor at .claude-plugin/marketplace.json, updating ensures you receive the latest skill templates and command workflows from the repository.

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