# How to Integrate PM Skills Marketplace with Codex, Gemini CLI, and Other AI Assistants

> Integrate PM Skills Marketplace with Codex, Gemini CLI, and more. Copy skills directories to enable universal markdown-based skill definitions across AI assistants.

- Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills)
- Tags: how-to-guide
- Published: 2026-06-21

---

**Copy the `skills/` directories from the PM Skills Marketplace repository into your assistant's skill folder to enable universal markdown-based skill definitions across Codex, Gemini CLI, Cursor, and other tools.**

The **PM Skills Marketplace** (`phuryn/pm-skills`) is a collection of product-management knowledge shipped as plain markdown files. While originally designed for Claude, the repository's architecture uses a universal skill format that any AI assistant can parse, making it possible to integrate these capabilities into Codex, Gemini CLI, OpenCode, Cursor, and Kiro without code modification.

## Understanding the PM Skills Marketplace Architecture

The repository organizes knowledge into two distinct layers: **skills** and **commands**. Understanding this separation is critical for successful integration with non-Claude assistants.

### Skill Files vs. Claude Commands

**Skills** are pure markdown documents stored in `*/skills/*` directories throughout the repository. Each skill lives in its own folder containing a [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) file that describes a PM framework, usage notes, and example prompts. For example, the resume review skill resides at [`pm-toolkit/skills/review-resume/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-toolkit/skills/review-resume/SKILL.md), while the product discovery brainstorming skill is located at [`pm-product-discovery/skills/brainstorm-ideas-new/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-product-discovery/skills/brainstorm-ideas-new/SKILL.md).

**Commands** (such as `/discover`, `/plan-launch`, and `/gtm`) are Claude-specific orchestrations that chain multiple skills together. These slash commands are not automatically usable in other assistants, but the underlying skills they orchestrate remain fully accessible.

## Step-by-Step Integration Guide

To integrate PM Skills Marketplace with your preferred AI assistant, you only need to copy the relevant skill directories into the assistant's designated skill folder.

### Gemini CLI (Global Installation)

For Gemini CLI, skills are stored globally in `~/.gemini/skills/`. Run the following script from the repository root to copy all nine plugin skill directories:

```bash

# Copy all skills for Gemini CLI (global installation)

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

```

This copies every [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) from plugins like `pm-toolkit`, `pm-product-discovery`, and `pm-go-to-market` into the global Gemini skills directory.

### OpenCode (Project-Level Setup)

OpenCode expects skills at the project level within `.opencode/skills/`:

```bash

# 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

```

### Cursor and Kiro

Both Cursor and Kiro follow similar project-level patterns:

- **Cursor**: Copy skills to `.cursor/skills/`
- **Kiro**: Copy skills to `.kiro/skills/`

Use the same bash loop pattern shown above, adjusting the target directory accordingly.

### Codex (Manual Workflow)

Codex does not currently support native slash commands, so you must manually drive workflows by prompting the assistant with individual skills in sequence. For example, to run a product discovery workflow:

```text
User: "I need to run a product discovery for a new AI-assistant idea."
Assistant:
1️⃣ Run the "brainstorm-ideas-new" skill → generate a list of ideas.
2️⃣ Run the "identify-assumptions-new" skill → list risky assumptions.
3️⃣ Run the "prioritize-assumptions" skill → rank assumptions by impact × risk.
4️⃣ Run the "brainstorm-experiments-new" skill → suggest experiments.

```

## Working with Universal Markdown Skills

Each skill file follows a consistent structure that any LLM can parse. The [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files contain a short description, usage notes, and sample prompts. For instance, [`pm-go-to-market/skills/gtm-strategy/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/gtm-strategy/SKILL.md) defines go-to-market strategies, while [`pm-execution/skills/create-prd/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/create-prd/SKILL.md) handles PRD creation.

Because these are plain markdown files, you can invoke them naturally:

```text
"Help me draft a privacy policy using the pm-toolkit privacy-policy skill"

```

Codex or Gemini CLI will locate the relevant [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) and generate the appropriate response based on the examples and structure provided in the file.

## Replicating Claude Slash Commands in Other Assistants

Since commands like `/discover` are Claude-specific, you must re-implement the orchestration logic in your target assistant. Here is pseudocode showing how to replicate the discovery workflow:

```python

# Pseudocode for a "discover" workflow in a generic assistant

def discover(topic):
    ideas = run_skill('brainstorm-ideas-new', topic)
    assumptions = run_skill('identify-assumptions-new', ideas)
    prioritized = run_skill('prioritize-assumptions', assumptions)
    experiments = run_skill('brainstorm-experiments-new', prioritized)
    return {
        "ideas": ideas,
        "assumptions": assumptions,
        "prioritized": prioritized,
        "experiments": experiments,
    }

```

Alternatively, drive the workflow manually by prompting your assistant to execute each skill in sequence as outlined in the previous section.

## Summary

- **PM Skills Marketplace** (`phuryn/pm-skills`) contains nine plugins with markdown-based skill definitions located in `*/skills/*` directories.
- **Skills** (universal): Plain markdown files like [`pm-toolkit/skills/review-resume/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-toolkit/skills/review-resume/SKILL.md) that work with any assistant.
- **Commands** (Claude-only): Slash commands like `/discover` that require manual re-implementation in other tools.
- **Integration method**: Copy skill directories to assistant-specific folders (`~/.gemini/skills/`, `.opencode/skills/`, `.cursor/skills/`, `.kiro/skills/`).
- **Usage**: Reference skills by name in natural language prompts, or chain them programmatically to replace Claude-specific orchestrations.

## Frequently Asked Questions

### Can I use PM Skills Marketplace commands like /discover in Codex?

No, slash commands like `/discover` are Claude-specific orchestrations that are not supported in Codex, Gemini CLI, or other assistants. However, you can access the same functionality by manually running the underlying skills in sequence—`brainstorm-ideas-new`, `identify-assumptions-new`, `prioritize-assumptions`, and `brainstorm-experiments-new`—or by writing a wrapper script that chains these calls programmatically.

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

**Skills** are standalone markdown files ([`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md)) containing product management frameworks and prompts that any AI assistant can parse. **Commands** are Claude-only wrapper scripts that chain multiple skills together into a single interaction (e.g., `/discover` runs four skills in sequence). Skills are universal; commands are platform-specific.

### Where are the skill files located in the repository?

Skill files are distributed across nine plugin directories (such as `pm-toolkit`, `pm-product-discovery`, and `pm-go-to-market`). Each plugin contains a `skills/` subdirectory with individual skill folders. For example, the resume review skill is at [`pm-toolkit/skills/review-resume/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-toolkit/skills/review-resume/SKILL.md), and the GTM strategy skill is at [`pm-go-to-market/skills/gtm-strategy/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/gtm-strategy/SKILL.md).

### Do I need to convert the markdown files to use them with Gemini CLI?

No conversion is necessary. The PM Skills Marketplace uses a universal markdown format that Gemini CLI, Codex, OpenCode, Cursor, and Kiro can read natively. Simply copy the `skills/` directories into your assistant's designated skill folder (`~/.gemini/skills/` for Gemini CLI, `.opencode/skills/` for OpenCode, etc.) and restart the assistant to discover the new capabilities.