plugin-creator

Guide developers to create OpenCode plugins and configure their load paths.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/acedergren/oci-self-service-portal --skill plugin-creator-acedergren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/acedergren/oci-self-service-portal/tree/main/.opencode/skills/plugin-creator
Command: npx skills add https://github.com/acedergren/oci-self-service-portal --skill plugin-creator-acedergren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create OpenCode plugins and know where to load them, simplifying plugin development and deployment.

Core Features & Use Cases

  • Guides plugin development with a minimal, reusable template.
  • Explains local vs. global plugin loading paths and npm integration.
  • Provides a clear reference to official OpenCode plugin documentation for further learning.

Quick Start

Create a new plugin under .opencode/plugins and reference it in opencode.json, then run your app to load and test it.

Frequently Asked Questions about plugin-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set the load order for multiple OpenCode plugins?

You set the OpenCode plugin load order by configuring the load paths in your opencode.json file. Proper load path configuration ensures that multiple plugins, whether local templates or npm-based, are discovered and initialized in the correct sequence.

How do I create an OpenCode plugin and configure its load path?

To create an OpenCode plugin, place a new plugin file under the .opencode/plugins directory and reference it in opencode.json. This load path configuration ensures the application discovers and loads your custom plugin correctly during startup.

What is the difference between local and global OpenCode plugin loading?

Local OpenCode plugin loading applies to project-scoped scenarios using local templates, while global loading applies to broader environments. Both approaches support npm-based plugins, allowing you to configure load paths based on your specific project or system requirements.

How does YAML frontmatter discovery work for OpenCode plugins?

YAML frontmatter is used for OpenCode plugin discovery and configuration. When you create an OpenCode plugin, including YAML frontmatter allows the system to properly identify, load, and apply your plugin according to the defined load order and project scope.

Can I use npm-based plugins with OpenCode project-scoped configurations?

Yes, npm-based plugins are fully supported in OpenCode project-scoped configurations. You can integrate npm packages alongside local templates by configuring the appropriate load paths in opencode.json, allowing both local and global plugin scenarios to work together seamlessly.

How do I set the load order for multiple OpenCode plugins?

You set the OpenCode plugin load order by configuring the load paths in your opencode.json file. Proper load path configuration ensures that multiple plugins, whether local templates or npm-based, are discovered and initialized in the correct sequence.