Can pm-skills Be Used with OpenCode? Complete Integration Guide

Yes, pm-skills works with OpenCode by copying SKILL.md files into the .opencode/skills/ directory, making the framework AI-assistant-agnostic.

The phuryn/pm-skills repository provides a product management skills framework designed to be AI-assistant-agnostic. While the full marketplace experience runs natively in Claude Code, the skills only can be leveraged by any tool that reads the universal SKILL.md format, including OpenCode. This compatibility allows you to use pm-skills with OpenCode without modifying the source files.

How pm-skills Integrates with OpenCode

The Universal SKILL.md Format

Each skill in pm-skills is defined as a plain markdown file following the SKILL.md specification. According to the repository source code, these files live in pm-*/skills/*/SKILL.md paths (for example, pm-product-discovery/skills/brainstorm-ideas-new/SKILL.md). Because OpenCode interprets this standard format directly, no additional code changes are required to use pm-skills with OpenCode.

Project-Level Skill Discovery

OpenCode discovers skills by scanning the .opencode/skills/ directory at the project level. The README.md in the phuryn/pm-skills repository documents that copying a plugin's skills/ folder into this directory makes the skills immediately available to the OpenCode extension.

Installing pm-skills for OpenCode

Install All Plugin Skills

To populate your OpenCode project with every available pm-skills capability, copy the skills directories from all plugins:

# Example: install every skill from all plugins for an Open Code project

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

Install Specific Plugin Skills

For targeted workflows, copy only the skills you need. For example, to install only product discovery capabilities:

# Example: use a single plugin’s skills only

mkdir -p .opencode/skills/
cp -r pm-product-discovery/skills/* .opencode/skills/

# Now you can invoke discovery-related skills such as:

> brainstorm-ideas-new
> prioritize-assumptions

Using Skills in OpenCode

Once installed in .opencode/skills/, invoke skills by typing the skill name as a prompt in the OpenCode editor. OpenCode feeds the corresponding SKILL.md content to the LLM, returning structured output based on the template.

For example, after copying the skills:

# Example: run a skill from Open Code (after the copy above)

# In an Open Code editor, type the skill name as a prompt, e.g.:

> value-proposition

# Open Code will feed the corresponding SKILL.md content to the LLM,

# returning a structured value-proposition based on the template.

Key Architecture Components

Understanding the file structure helps clarify why pm-skills works seamlessly with OpenCode:

• README.md: Contains the central documentation describing OpenCode integration and provides the copy-script examples.
• pm-/skills//SKILL.md: Individual skill definitions (e.g., pm-product-discovery/skills/brainstorm-ideas-new/SKILL.md). These are the files copied into .opencode/skills/.
• .opencode/skills/: The generated directory where OpenCode looks for skill definitions; populated by the installation scripts above.

Summary

• pm-skills is AI-assistant-agnostic: While optimized for Claude Code, the skills work with any tool reading the SKILL.md format.
• Universal format compatibility: OpenCode interprets the plain markdown SKILL.md files directly without requiring modifications.
• Simple installation: Copy files from pm-*/skills/ to .opencode/skills/ to enable discovery.
• Immediate invocation: Type skill names as prompts in OpenCode to execute structured workflows.

Frequently Asked Questions

Is pm-skills exclusive to Claude Code?

No. While the full marketplace (including commands) runs natively in Claude Code and Claude Cowork, the skills themselves are designed to be AI-assistant-agnostic. Any tool that reads the universal SKILL.md format, including OpenCode, can leverage the pm-skills framework.

What file format does OpenCode expect for skills?

OpenCode expects skills in the SKILL.md format—plain markdown files that define structured prompts and workflows. The pm-skills repository stores these in pm-*/skills/*/SKILL.md paths, which you copy into your project's .opencode/skills/ directory.

Do I need to modify the SKILL.md files to use them with OpenCode?

No additional code changes are required. The skills are plain markdown files that OpenCode interprets directly. Simply copy the existing SKILL.md files from the pm-skills plugins into your .opencode/skills/ directory.

Can I mix pm-skills with other OpenCode skill libraries?

Yes. The .opencode/skills/ directory functions as a flat namespace where you can combine skills from pm-skills with other libraries following the same SKILL.md specification. Copy files from multiple sources into this directory to build a custom skill stack.

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