How to Use PM Skills with OpenCode, Gemini CLI, or Cursor: Complete Setup Guide

Copy the skill folders from any pm-* plugin into your editor-specific skills directory—.opencode/skills/ for OpenCode, ~/.gemini/skills/ for Gemini CLI, or .cursor/skills/ for Cursor—to instantly access all 68 PM Skills without installing additional runtime code.

The phuryn/pm-skills repository distributes project management expertise as editor-agnostic skill folders rather than traditional plugins. Because these skills consist entirely of markdown files located in directories like pm-toolkit/skills/, you can integrate them with OpenCode, Gemini CLI, or Cursor through simple file system operations, bypassing complex package management entirely.

How PM Skills Integration Works

Unlike conventional editor extensions, pm-skills contains no runtime code for specific editors. According to the repository's README.md (lines 119-122), the core functionality lives in skill directories within each plugin folder (e.g., pm-toolkit/skills/, pm-strategy/skills/). These directories contain markdown definitions and slash-command configurations that compatible AI assistants recognize automatically.

When you copy these folders to an editor-specific location, the AI assistant discovers the skill files and exposes them as callable commands. This architecture means you gain immediate access to 68 individual skills and 42 chained workflows without compiling code or managing dependencies.

Setting Up PM Skills for OpenCode

OpenCode uses a project-level configuration strategy. You must create a .opencode/skills/ directory at your project root and populate it with the skill files from every pm-* plugin you have installed.

Run the following commands from your project directory:

# Create the OpenCode skills directory

mkdir -p .opencode/skills/

# Copy all skills from each pm-* plugin

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

This snippet, referenced in README.md lines 124-134, iterates through all local pm-* directories and copies their skill contents into the OpenCode-specific folder. After execution, commands like /discover and /write-prd become available when you invoke OpenCode's AI assistant.

Configuring PM Skills for Gemini CLI

Gemini CLI requires a global installation approach. The tool looks for skills in ~/.gemini/skills/ rather than project-specific directories, making your PM Skills available across all workspaces.

Execute these commands from your terminal:

# Create the global Gemini skills directory

mkdir -p ~/.gemini/skills/

# Copy all skills from each pm-* plugin

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

Once copied, Gemini CLI automatically indexes these files on startup. The skills are immediately available for use in any project context, providing consistent access to project management workflows regardless of your current working directory.

Installing PM Skills in Cursor

Cursor follows a project-level pattern similar to OpenCode, using a .cursor/skills/ directory. This setup keeps your PM Skills scoped to specific repositories while maintaining version control flexibility.

From your project root, run:

# Create the Cursor skills directory

mkdir -p .cursor/skills/

# Copy all skills from each pm-* plugin

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

After running these commands, Cursor's AI assistant will recognize the skill definitions located in pm-toolkit/commands/*.md and related files, exposing them as slash commands within the editor interface.

Understanding the Skill File Structure

To troubleshoot or customize your setup, examine the source files that power the integration:

• pm-toolkit/skills/ (and analogous pm-*/skills/ folders): Contain the actual markdown skill definitions that define behavior and prompts.
• pm-toolkit/commands/*.md: Provide the slash-command definitions that map user inputs to specific skill executions.
• README.md: Documents the official integration table and provides the exact copy commands for each editor (lines 119-134).

These files are pure markdown, meaning you can edit them directly with any text editor to customize workflows without breaking the integration.

Summary

• PM Skills integrates with OpenCode, Gemini CLI, and Cursor through simple file copying, not plugin installation.
• OpenCode and Cursor use project-level directories (.opencode/skills/ and .cursor/skills/), while Gemini CLI uses a global directory (~/.gemini/skills/).
• The pm-*/skills/ directories contain markdown files that are editor-agnostic and require no compilation.
• Once copied, slash commands like /discover and /write-prd become immediately available in your AI assistant.
• The repository provides automation scripts in README.md lines 124-134 to handle the copy process for all supported editors.

Frequently Asked Questions

Do I need to install a separate plugin for each editor?

No. The phuryn/pm-skills repository contains no editor-specific runtime code. You only need to copy the skill folders from pm-*/skills/ into the appropriate directory for your chosen editor. The skills are pure markdown files that any compatible AI assistant can interpret directly.

Can I use PM Skills with multiple editors simultaneously?

Yes. Because the skills are simply markdown files, you can copy them to multiple locations without conflict. For example, you can maintain project-level skills in .opencode/skills/ for OpenCode while also copying them to ~/.gemini/skills/ for Gemini CLI global access. Each editor maintains its own copy of the skill definitions.

What commands become available after installing PM Skills?

Once installed, the AI assistant recognizes slash commands defined in files like pm-toolkit/commands/*.md. Common commands include /discover for requirements discovery and /write-prd for product requirements documentation. The exact command list depends on which pm-* plugins you have copied into your skills directory.

Do I need to restart the editor after copying the skills?

Generally, no. OpenCode, Gemini CLI, and Cursor scan their skills directories when the AI assistant is invoked. However, if commands do not appear immediately, restarting the editor or reloading the window will force a re-scan of the skills directories and resolve any caching issues.

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