# Can You Use phuryn/pm-skills as a Library? A Complete Integration Guide > Discover if phuryn/pm-skills can be used as a library. This guide shows you how to integrate it into your projects using various installation methods for seamless AI assistant development. - Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills) - Tags: how-to-guide - Published: 2026-06-28 --- **Yes, you can use phuryn/pm-skills as a reusable library by installing it via Claude Code, Claude Cowork, or Codex, or by copying the markdown skill files into any AI assistant that supports the SKILL.md format.** The phuryn/pm-skills repository functions as a modular library of product management frameworks, distributing reusable knowledge blocks through a plugin-based architecture. Unlike traditional compiled libraries, it delivers **skills** (markdown-driven prompt templates) and **commands** (CLI-style workflows) that integrate directly into AI-assisted development environments. This guide explains how to consume phuryn/pm-skills as a library across Claude, OpenCode, Gemini, and other compatible platforms. ## Understanding the Library Architecture ### Skills, Commands, and Plugins The repository organizes content into three distinct layers that function as a modular library: - **Skills** are self-contained markdown files (conventionally named [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md)) that contain complete prompt templates. Each skill file in paths like [`pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.md) defines a specific product management capability that models can load on demand. - **Commands** are thin wrappers that chain multiple skills together into CLI-style workflows. Files like [`pm-execution/commands/write-prd.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/write-prd.md) orchestrate several execution-related skills to create comprehensive workflows. - **Plugins** group related skills and commands into domain-specific packages (e.g., `pm-product-discovery`, `pm-go-to-market`). The [`pm-go-to-market/.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/.claude-plugin/plugin.json) file serves as the plugin manifest that tells Claude which assets belong together, functioning similarly to a package manifest in traditional package managers. ## Installing phuryn/pm-skills as a Library ### Claude Code CLI Integration To use phuryn/pm-skills as a library in Claude Code, first add the marketplace to your environment, then install specific plugins: ```bash # Add the marketplace (one-time setup) claude plugin marketplace add phuryn/pm-skills # Install only the product-discovery plugin claude plugin install pm-product-discovery@pm-skills ``` After installation, invoke skills using slash commands: ``` /discover AI-powered meeting summarizer for remote teams ``` ### Claude Cowork GUI Setup For Claude Cowork users, install the entire library through the graphical interface: 1. Open **Customize → Browse plugins → Personal → +** 2. Select *Add marketplace from GitHub* 3. Enter `phuryn/pm-skills` This automatically installs all 9 plugins, making the same slash commands available through the UI. ### OpenCode, Cursor, and Gemini Integration Because the underlying assets are plain Markdown files, you can treat phuryn/pm-skills as a generic skill library in other AI assistants. Copy the skill folders into the appropriate directory for your tool: ```bash # Copy 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/`: ```bash for plugin in pm-*/; do cp -r "$plugin/skills/"* ~/.gemini/skills/ 2>/dev/null done ``` These skills work as pure markdown knowledge blocks; however, note that commands are Claude-specific and will not run in other assistants, while the skills themselves can be called by name from any compatible model. ### Codex (OpenAI) Integration Codex can consume the same marketplace definition used by Claude Code. The [`.claude-plugin/marketplace.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/marketplace.json) file at the repository root describes the available plugins: ```bash codex plugin marketplace add phuryn/pm-skills codex plugin add pm-go-to-market@pm-skills ``` Then invoke from your code: ```python response = codex.run("/plan-launch AI-code-review tool targeting mid-size engineering teams") print(response) ``` ## Practical Usage Examples ### Running a Complete Discovery Flow Once installed via Claude Code, you can trigger complex product management workflows: ``` /discover AI-powered meeting summarizer for remote teams ``` This command leverages the `pm-product-discovery` plugin to execute a full discovery flow. ### Copying Skills for Non-Claude Models To use specific skills in OpenCode without installing the full plugin system: ```bash # Copy specific skill folders cp -r pm-product-discovery/skills/brainstorm-ideas-existing .opencode/skills/ ``` Then invoke directly: ``` product-vision: Craft an inspiring vision for a new AI writing assistant. ``` ### Querying Risk Assumptions After copying skills to a Gemini-compatible directory: ``` What are the riskiest assumptions for our AI-code-review tool? ``` The model references the copied [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files to provide structured analysis. ## Repository Structure and Key Files Understanding the file structure helps when using phuryn/pm-skills as a library: - **[`.claude-plugin/marketplace.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/marketplace.json)** – The marketplace definition used by Claude Code and Codex to discover available plugins. - **[`pm-go-to-market/.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/.claude-plugin/plugin.json)** – Plugin manifest that defines the skills and commands included in the go-to-market package. - **[`pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.md)** – Representative skill file showing the markdown format used across the repository. - **[`pm-execution/commands/write-prd.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/commands/write-prd.md)** – Example command file that chains several execution-related skills into a single workflow. - **[`README.md`](https://github.com/phuryn/pm-skills/blob/main/README.md)** – Contains the installation instructions for various platforms (lines 50-78). - **[`pm-toolkit/README.md`](https://github.com/phuryn/pm-skills/blob/main/pm-toolkit/README.md)** – Documentation for a minimal plugin containing utilities like resume review and NDA drafting. ## Summary - **phuryn/pm-skills is not a compiled library** but a catalog of markdown-based skills and commands that function as reusable modules. - **Install via Claude Code** using `claude plugin marketplace add phuryn/pm-skills` followed by specific plugin installation commands. - **Cross-platform compatibility** allows you to copy [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files into OpenCode, Gemini, Cursor, or Kiro directories for use with any model supporting the format. - **Plain-text architecture** enables version control, forking, and vending without binary dependencies. - **Plugin manifests** in [`.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/plugin.json) files define modular groupings, allowing you to import only the domains you need. ## Frequently Asked Questions ### Is phuryn/pm-skills a traditional Python or npm library? No, phuryn/pm-skills is not a compiled library distributed via PyPI or npm. It is a collection of Claude plugins containing markdown-based skills and commands. You consume it through AI assistant marketplaces or by copying the plain-text skill files into your project's skill directories. ### Can I use these skills without Claude? Yes, but with limitations. The **skills** (markdown files) are portable and work with any AI assistant that reads the [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) format, including OpenCode, Gemini, Cursor, and Kiro. However, the **commands** (CLI-style workflows) are Claude-specific and will not execute in other environments. ### How do I install only specific domains from the library? Use the plugin-based installation to import only the modules you need. For example, in Claude Code run `claude plugin install pm-toolkit@pm-skills` to get only the toolkit utilities, or `claude plugin install pm-execution@pm-skills` for execution-related skills. This modular approach keeps your environment lightweight. ### Where does the marketplace configuration reside? The marketplace definition is stored in the root-level [`.claude-plugin/marketplace.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/marketplace.json) file, which Claude Code and Codex read to discover available plugins. Individual plugin configurations reside in their respective directories (e.g., [`pm-go-to-market/.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/.claude-plugin/plugin.json)), defining which skills and commands each package exports.