How to Build and Install phuryn/pm-skills: Complete Setup Guide

To build phuryn/pm-skills, register the marketplace with claude plugin marketplace add phuryn/pm-skills, then install individual plugins via claude plugin install <plugin-name>@pm-skills, or manually copy skill files for non-Claude AI assistants.

The phuryn/pm-skills repository is a GitHub-hosted marketplace containing nine specialized plugins that expose product-management skills and commands for AI assistants. Building this marketplace requires registering the marketplace definition found in /.claude-plugin/marketplace.json and installing the specific plugins you need to enable slash-commands like /write-prd and /discover in Claude Code.

Prerequisites

Before building phuryn/pm-skills, ensure you have Claude Code or Claude Cowork installed, as the marketplace is designed for Anthropic's Claude ecosystem. The repository structure contains nine plugin directories, each with its own .claude-plugin/plugin.json metadata file that Claude uses for automatic discovery and installation.

Understanding the Repository Structure

The phuryn/pm-skills marketplace organizes functionality into nine distinct plugins, each targeting a specific product-management domain:

• pm-toolkit: Resume reviews, NDA drafting, and general utilities
• pm-product-strategy: Vision and strategy definition
• pm-product-discovery: User research and discovery workflows
• pm-market-research: Competitive analysis and market sizing
• pm-data-analytics: SQL queries and data interpretation
• pm-marketing-growth: Growth metrics and marketing strategies
• pm-go-to-market: Launch planning and GTM execution
• pm-execution: PRD writing and technical specifications
• pm-ai-shipping: Documentation for AI-built applications

Each plugin follows a consistent structure:

• skills/*/SKILL.md files define individual capabilities (e.g., pm-execution/skills/create-prd/SKILL.md generates Product Requirements Documents)
• commands/*.md files chain skills into workflows (e.g., pm-execution/commands/write-prd.md creates the /write-prd slash command)
• .claude-plugin/plugin.json provides metadata for automatic discovery

Step-by-Step Build Instructions

Register the Marketplace

First, add the marketplace to Claude's registry. This one-time step reads the /.claude-plugin/marketplace.json file and makes all nine plugins available for installation:

claude plugin marketplace add phuryn/pm-skills

Install Individual Plugins

After registering the marketplace, install the specific plugins you need. Install all nine for full functionality, or select only relevant domains:

# Install the complete suite

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

Each installation command references the plugin name followed by @pm-skills to specify the marketplace source.

Verify Your Installation

Confirm successful installation by testing the available slash commands. For example, the /discover command from pm-product-discovery should now be available:

/discover AI-powered meeting summarizer for remote teams

You can also invoke individual skills directly by their name, such as product-vision or referencing pm-data-analytics/skills/sql-queries/SKILL.md, without using the slash-command wrapper.

Alternative: Build for Other AI Assistants

If you use OpenCode, Gemini, Cursor, or Kiro instead of Claude, you cannot use the plugin marketplace directly. Instead, manually copy the skill files to your assistant's configuration directory:

# Copy all skills for OpenCode (project-level)

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

For Gemini, copy to ~/.gemini/skills/. For Kiro, use ~/.kiro/skills/. This method extracts the raw Markdown skill definitions from files like pm-execution/skills/create-prd/SKILL.md and pm-ai-shipping/skills/shipping-artifacts/SKILL.md, making them readable by any AI assistant that processes the universal skill format.

Key Configuration Files

Understanding these critical files helps troubleshoot build issues:

• /.claude-plugin/marketplace.json: Declares the marketplace and lists all nine available plugins. Claude reads this during the marketplace add command.
• pm-toolkit/.claude-plugin/plugin.json: Example plugin metadata that defines the toolkit's capabilities and entry points.
• pm-execution/commands/write-prd.md: Command definition that wraps the create-prd skill into a callable /write-prd workflow.
• pm-ai-shipping/commands/ship-check.md: Defines the command for running the full AI-shipping workflow.
• pm-marketing-growth/commands/north-star.md: Defines the command for North-Star metric definition sessions.

Summary

• Register once: Use claude plugin marketplace add phuryn/pm-skills to enable access to all nine plugins.
• Install selectively: Run claude plugin install <name>@pm-skills for each plugin you need, or install all nine for complete coverage.
• Verify functionality: Test with slash commands like /write-prd or /plan-launch to ensure skills are properly loaded.
• Cross-platform support: For non-Claude assistants, copy skills/* files to your assistant's skills directory (e.g., .opencode/skills/).

Frequently Asked Questions

What is phuryn/pm-skills and who should use it?

The phuryn/pm-skills repository is a marketplace of nine Claude plugins designed for product managers who want to automate discovery, strategy, execution, and go-to-market workflows using AI. It provides structured prompts and chained commands that guide AI assistants through domain-specific tasks like writing PRDs or defining North-Star metrics.

Can I install phuryn/pm-skills without Claude Code?

Yes, though you lose the plugin management features. Clone the repository and manually copy the Markdown files from skills/ directories (such as pm-data-analytics/skills/sql-queries/SKILL.md) into your AI assistant's skills folder. This works for OpenCode, Gemini, Kiro, and Cursor, which can read the universal skill format but cannot process the .claude-plugin/plugin.json metadata.

How do I update plugins after the initial build?

Run claude plugin update to check for new versions of installed plugins from the phuryn/pm-skills marketplace. Since the marketplace references the GitHub repository directly, updates to skill files in pm-execution/skills/ or command definitions in pm-ai-shipping/commands/ are automatically available when you refresh the plugin index.

What is the difference between a skill and a command in this repository?

A skill is a single capability defined in a SKILL.md file (e.g., generating SQL queries), while a command is a workflow defined in commands/*.md that chains multiple skills into an end-to-end process (e.g., /ship-check running the full AI-shipping workflow). Skills are the building blocks; commands are the user-facing interfaces.

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