# Which AI Assistants Are Supported by pm-skills? Full Compatibility Guide > Discover which AI assistants pm-skills supports. Learn about full compatibility with Claude Code and Claude Cowork, plus limited support for Gemini CLI, Cursor, and more. - Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills) - Tags: compatibility-guide - Published: 2026-06-29 --- **pm-skills supports Claude Code and Claude Cowork with full features (skills + commands), while Gemini CLI, OpenCode, Cursor, Kiro, and Codex CLI support only the skill files through the universal markdown format.** The phuryn/pm-skills repository functions as a Claude Marketplace containing product management frameworks, but its architecture intentionally separates skills from commands to enable cross-platform compatibility. While the full plugin ecosystem is designed for Anthropic's Claude, the skill files use a universal markdown format that any AI assistant capable of reading [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files can import. ## Understanding the pm-skills Architecture The repository organizes capabilities into two distinct layers that determine AI assistant compatibility. **Skills** are framework-level knowledge encoded in pure markdown files ([`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md)). These contain structured PM methodologies like "product-vision" or "pricing-strategy" and reside in paths like `pm-*/skills/*/SKILL.md`. **Commands** are Claude-specific slash-command workflows (e.g., `/discover`, `/strategy`) that orchestrate multiple skills into end-to-end processes. These commands only function within Claude Code or Claude Cowork environments. This separation allows the repository to serve dual purposes: a complete marketplace for Claude users and a portable knowledge base for other assistants. ## Fully Supported: Claude Code and Claude Cowork Claude Code (CLI) and Claude Cowork receive the complete feature set, including all **9 plugins** with both skills and commands. According to the repository's README, the installation process uses the marketplace format defined in [`.claude-plugin/marketplace.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/marketplace.json)【/cache/repos/github.com/phuryn/pm-skills/main/README.md#L14-L22】: ```bash # Add the marketplace to Claude Code claude plugin marketplace add phuryn/pm-skills # Install individual plugins claude plugin install pm-toolkit@pm-skills claude plugin install pm-product-strategy@pm-skills claude plugin install pm-product-discovery@pm-skills ``` Once installed, Claude automatically loads relevant skills based on conversation context while commands like `/write-prd` or `/discover` must be invoked explicitly【/cache/repos/github.com/phuryn/pm-skills/main/README.md#L63-L79】. ## Skills-Only Support for Other AI Assistants Non-Claude assistants can utilize the **skill files only**, as they cannot execute the Claude-specific slash commands. The repository explicitly lists these compatible assistants in the README【/cache/repos/github.com/phuryn/pm-skills/main/README.md#L117-L124】: - **Gemini CLI** - **OpenCode** - **Cursor** - **Kiro** To use pm-skills with these assistants, you manually copy the skill directories into the assistant's specific skill path: ```bash # Example: Copying skills to Gemini CLI for plugin in pm-*/; do cp -r "$plugin/skills/"* ~/.gemini/skills/ 2>/dev/null done ``` Similar patterns work for other assistants: - OpenCode: Copy to `.opencode/skills/` - Cursor: Copy to `.cursor/skills/` - Kiro: Copy to `.kiro/skills/` The assistant then treats each [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) as a reusable knowledge chunk, reading the markdown content verbatim when relevant prompts are detected【/cache/repos/github.com/phuryn/pm-skills/main/README.md#L124-L135】. ## Codex CLI Compatibility **Codex CLI** (OpenAI) represents a special case. Because it reads the same plugin definition file as Claude Code—[`.claude-plugin/marketplace.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/marketplace.json)—Codex CLI supports the full marketplace installation method: ```bash codex plugin marketplace add phuryn/pm-skills codex plugin add @pm-skills ``` While Codex can install plugins through the marketplace system, note that the slash-commands are not exposed as native Codex commands. Codex CLI utilizes the skills portion through the marketplace format, similar to the manual copy method but with automated installation. ## How Skills Work Across Different Assistants When you interact with a pm-skill in a non-Claude assistant, the runtime reads the markdown file directly. For example, if you copy the `pricing-strategy` skill into your assistant's skill folder and ask about SaaS pricing, the assistant references the structured framework in [`pm-product-strategy/skills/pricing-strategy/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-strategy/skills/pricing-strategy/SKILL.md) rather than executing a predefined workflow. The [`CLAUDE.md`](https://github.com/phuryn/pm-skills/blob/main/CLAUDE.md) file serves as the source-of-truth for agent guidance, while individual [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files contain the actual framework definitions that any assistant can parse. This architecture ensures that core product management methodologies remain portable even as command orchestration remains Claude-specific. ## Summary - **Claude Code and Claude Cowork** receive full support including 9 plugins, 23+ skills, and slash commands via `claude plugin marketplace add`. - **Gemini CLI, OpenCode, Cursor, and Kiro** support skills only through manual copying of [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files to assistant-specific directories. - **Codex CLI** supports the marketplace format for installation but uses skills only (no slash commands). - **Skills** are universal markdown files ([`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md)) located in `pm-*/skills/` directories. - **Commands** are Claude-specific workflows defined in the marketplace manifest that cannot transfer to other assistants. ## Frequently Asked Questions ### Can I use pm-skills commands in Cursor or VS Code? No. Commands like `/discover` or `/strategy` are Claude-specific slash commands that require the Claude Code runtime. When using pm-skills with Cursor, you only have access to the static knowledge contained in the [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files, which Cursor can reference as context but cannot execute as interactive workflows. ### Does pm-skills work with ChatGPT or the ChatGPT desktop app? No. ChatGPT does not currently support local skill directories or markdown-based skill injection in the same way that Gemini CLI, OpenCode, or Cursor do. The skills are designed for assistants that can load local [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files from a filesystem directory, which ChatGPT does not support. ### How do I install pm-skills skills in Gemini CLI? First, clone the repository, then copy the skill directories from each plugin into Gemini's global skill directory at `~/.gemini/skills/`. You can use a shell loop to copy all skills at once: `for plugin in pm-*/; do cp -r "$plugin/skills/"* ~/.gemini/skills/; done`. Gemini will then automatically reference these markdown files when you ask relevant product management questions. ### What is the difference between skills and commands in pm-skills? **Skills** are static markdown documentation containing frameworks and methodologies (like "how to write a PRD" or "pricing strategy frameworks"). **Commands** are interactive Claude-specific workflows that orchestrate multiple skills into step-by-step processes (like `/write-prd` which guides you through the entire PRD creation process). Only Claude Code and Claude Cowork can execute commands; other assistants can only read the static skill files.