How to Integrate pm-skills with OpenCode, Gemini CLI, or Cursor: Complete Setup Guide

Yes, pm-skills can be integrated with OpenCode, Gemini CLI, and Cursor by copying the skill folders from each plugin into the editor-specific skills directory, as the skills are pure markdown files that work across all three editors without additional configuration.

The phuryn/pm-skills repository provides a collection of AI-powered project management skills distributed across multiple plugins. Because the core functionality ships as skill folders containing pure markdown files rather than runtime code, you can import these skills directly into any compatible editor. This setup requires only shell commands to copy files from pm-*/skills/ directories into editor-specific locations.

How pm-skills Integration Works

Unlike traditional IDE plugins, pm-skills does not ship with editor-specific runtime code. Instead, each plugin (such as pm-toolkit) stores its capabilities as markdown skill definitions inside skills/ directories.

According to the repository's source code, these skill files follow a universal format that any AI coding assistant can parse. When you copy these folders to your editor's designated skills directory, the AI assistant automatically discovers the available commands and workflows. The repository contains 68 skills and 42 chained workflows that become immediately accessible after copying the files.

OpenCode Integration

OpenCode uses project-level skill configurations stored in the .opencode/skills/ directory.

Run the following shell commands from your project root to import all pm-skills plugins:

# Create the OpenCode skills directory if it doesn't exist

mkdir -p .opencode/skills/

# Copy every skill from each pm-* plugin into the OpenCode folder

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

After execution, OpenCode will discover skill files and expose commands like /discover and /write-prd when you invoke the AI assistant. No additional configuration is required because the markdown format is editor-agnostic.

Gemini CLI Integration

Gemini CLI stores skills globally in the ~/.gemini/skills/ directory, making them available across all projects.

Use this shell snippet to install pm-skills for global access:

# Create the global Gemini skill directory

mkdir -p ~/.gemini/skills/

# Copy every skill from each pm-* plugin into the global directory

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

This places the skill definitions in Gemini CLI's global path, allowing you to access commands from any directory on your system.

Cursor Integration

Cursor follows a project-level approach similar to OpenCode, using the .cursor/skills/ directory within your workspace.

Execute these commands to enable pm-skills in Cursor:

# Create the Cursor skills directory

mkdir -p .cursor/skills/

# Copy every skill from each pm-* plugin

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

Once copied, Cursor's AI assistant will expose the 68 skills and 42 chained workflows as slash commands available in your chat interface.

Key Files and Structure

Understanding the repository structure helps troubleshoot integration issues:

• README.md (lines 119-134): Contains the official integration table and ready-to-run shell snippets for each editor
• pm-toolkit/skills/ (and pm-*/skills/): Store the actual markdown skill definitions that get imported
• pm-toolkit/commands/*.md: Define the slash-command interfaces that appear once skills are loaded
• AGENTS.md / CLAUDE.md: Document Claude-specific usage; not required for OpenCode, Gemini CLI, or Cursor integration but clarifies the broader ecosystem

The skills reside as standalone markdown files within each plugin's skills/ directory, which is why the simple copy operation works across all three editors without modification.

Summary

• pm-skills integrates with OpenCode, Gemini CLI, and Cursor through simple file copying rather than complex plugin installation
• Each editor requires copying pm-*/skills/ folders to specific directories: .opencode/skills/, ~/.gemini/skills/, or .cursor/skills/
• The integration provides access to 68 skills and 42 chained workflows including /discover and /write-prd
• Skills are pure markdown files stored in paths like pm-toolkit/skills/, making them editor-agnostic
• No runtime dependencies or additional configuration is required after copying the skill files

Frequently Asked Questions

Does pm-skills require any special configuration after copying the skill files?

No additional configuration is required. Once you copy the skill folders to the editor-specific directory (such as .opencode/skills/ or ~/.gemini/skills/), the AI assistant automatically discovers the markdown skill definitions. The skills work immediately without editing configuration files or installing runtime dependencies.

Can I use pm-skills with multiple editors simultaneously?

Yes. Because the skills are pure markdown files stored in plugin directories like pm-toolkit/skills/, you can copy the same files to multiple editor locations (.opencode/skills/, .cursor/skills/, and ~/.gemini/skills/) without conflicts. Each editor maintains its own copy of the skill definitions.

What commands become available after integrating pm-skills with these editors?

After integration, your AI assistant gains access to 68 distinct skills and 42 chained workflows including commands like /discover for exploring capabilities and /write-prd for generating product requirements documents. These slash commands are defined in pm-toolkit/commands/*.md and become available immediately after the skills are copied.

Where are the official integration instructions documented in the repository?

The official integration table and copy-scripts are documented in README.md at lines 119-134, which provides the exact shell commands for OpenCode, Gemini CLI, and Cursor. This documentation confirms that skills only (not runtime code) are supported across these three editors.

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