How PM Skills Marketplace Integrates with Claude Code and Cowork: A Complete Guide

PM Skills Marketplace integrates with Claude Code and Cowork through a shared marketplace JSON that serves as a plugin registry, enabling both assistants to auto-load markdown-based skills and execute chained workflow commands. The phuryn/pm-skills repository functions as an AI operating system that delivers domain-specific product management capabilities through nine modular plugins.

Understanding the PM Skills Marketplace Architecture

The integration relies on a plugin-based architecture where skills and commands are stored as plain markdown files. This design ensures compatibility across Claude-based environments without requiring proprietary APIs or complex configuration files.

The Marketplace JSON Configuration

At the root of the repository, a marketplace file lists all nine available plugins—including pm-toolkit, pm-product-strategy, and pm-product-discovery. Both Claude Code and Claude Cowork read this JSON definition to discover available capabilities. According to the source code in README.md lines 48-58, Claude Cowork loads this data through its personal plugin browser, while Claude Code parses the same file via CLI commands.

Plugin Structure and Skill Loading

Each plugin contains two core components:

• Skills – Stored as */skills/*/SKILL.md files that Claude automatically loads when user prompts match trigger phrases. As documented in README.md lines 36-40, this auto-loading mechanism works across any Claude-based environment because the artifacts are pure markdown.

• Commands – Defined in commands/*.md files as chained workflows. In CLAUDE.md lines 7-20 and 48-66, the architecture specifies that commands group related skills into executable workflows, appearing as slash-commands in Cowork and natural-language invocations in Code.

Integration with Claude Cowork (GUI-Based)

Claude Cowork provides a graphical interface for installing and managing the PM Skills Marketplace plugins.

Installation via the Plugin Browser

Users install the entire marketplace through the Customize → Browse plugins → Personal UI. By selecting Add marketplace from GitHub and entering the identifier phuryn/pm-skills, all nine plugins install simultaneously. This workflow is detailed in README.md lines 48-57.

Using Slash Commands

Once installed, commands appear as slash-commands in the Cowork interface:

• /discover – Initiates product discovery workflows
• /write-prd – Generates product requirement documents
• /analyze-data – Executes data analytics pipelines

These commands trigger the markdown-defined workflows stored in each plugin's commands/ directory.

Integration with Claude Code (CLI-Based)

Claude Code requires explicit CLI commands to register and install the marketplace components.

Registering the Marketplace

First, add the marketplace registry to your local Claude Code installation:

claude plugin marketplace add phuryn/pm-skills

This command registers the marketplace JSON so Claude Code can resolve plugin dependencies.

Installing Individual Plugins

Unlike Cowork's bulk installation, Code requires installing each plugin individually. According to README.md lines 61-77, install the specific capabilities you need:

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

Natural Language Invocation

In Claude Code, commands are not exposed as slash-syntax. Instead, invoke workflows by describing the intent in natural language. For example, to run a product discovery session:

> Run product discovery on "AI-powered meeting summarizer": brainstorm ideas, map assumptions, prioritize risks, design experiments.

This approach leverages the same underlying command definitions while adapting to Code's conversational interface.

Cross-Assistant Compatibility

Because PM Skills Marketplace uses markdown-based skill definitions rather than proprietary formats, the same skill set can be ported to other AI assistants. As noted in README.md lines 15-21, copying the skills/ directories to Gemini, OpenCode, or Cursor requires only simple file system commands. This portability ensures that product management knowledge captured in the phuryn/pm-skills repository remains accessible regardless of which Claude-based assistant you deploy.

Summary

• Shared marketplace JSON – Both Claude Code and Cowork consume the same registry file to discover the nine available plugins.
• Auto-loading skills – Markdown files in */skills/*/SKILL.md paths automatically activate when prompts match trigger phrases.
• Dual command interfaces – Cowork exposes commands as /slash syntax, while Code accepts natural language descriptions of the same workflows.
• Installation methods – Cowork uses GUI-based bulk installation via phuryn/pm-skills, while Code requires explicit claude plugin marketplace add followed by individual plugin installation.
• File-based architecture – Pure markdown storage ensures skills work across Claude variants and other AI assistants without modification.

Frequently Asked Questions

How do I update PM Skills Marketplace plugins in Claude Code?

Run claude plugin update <plugin>@pm-skills for each installed plugin, or reinstall using claude plugin install with the latest version tag. The marketplace JSON at phuryn/pm-skills tracks version compatibility, ensuring CLI users receive the same updates as Cowork GUI users.

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

Yes. Because skills are stored as plain markdown files (SKILL.md), you can copy the skills/ directories from any plugin folder into other assistants like Gemini, OpenCode, or Cursor. The trigger phrases and knowledge content remain functional since they rely on standard markdown parsing rather than Claude-specific APIs.

What is the difference between skills and commands in the PM Skills Marketplace?

Skills are atomic knowledge modules stored in skills/*/SKILL.md that auto-load when mentioned. Commands are chained workflows defined in commands/*.md that orchestrate multiple skills into complete processes. In Claude Cowork, commands appear as /write-prd or /discover, while in Claude Code you invoke them by describing the workflow goal in natural language.

Which file should I read to understand the integration architecture?

Review CLAUDE.md in the repository root. Lines 7-20 describe the plugin structure and marketplace relationship, while lines 48-66 explain how skills auto-load and how commands differ between Code and Cowork environments. For installation specifics, refer to README.md lines 48-77.

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