plugin-creator

Create and organize OpenCode plugins with SKILL.md frontmatter and load paths.

63|8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/different-ai/openwork-enterprise --skill plugin-creator-different-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-creator
Source: https://github.com/different-ai/openwork-enterprise/tree/main/.opencode/skills/plugin-creator
Command: npx skills add https://github.com/different-ai/openwork-enterprise --skill plugin-creator-different-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates consistent creation, organization, and loading of OpenCode plugins across project and global environments, reducing setup friction for plugin developers.

Core Features & Use Cases

  • Standardized plugin templates: Provide a reliable starting point for new OpenCode plugins.
  • Clear load paths: Document and guide loading from project plugins (.opencode/plugins) or global plugin directories.
  • Reference-friendly workflow: Aligns with OpenCode docs and runbooks to streamline plugin development and maintenance.

Quick Start

Create a new OpenCode plugin following the guidelines and place it under the appropriate plugin directory to enable loading.

Frequently Asked Questions about plugin-creator

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

FAQPage Schema
How do I create OpenCode plugins and organize their load paths?

To create OpenCode plugins, you can use standardized templates that ensure proper organization and loading from project-local (.opencode/plugins) or global (~/.config/opencode/plugins) directories.

What is the correct directory structure for OpenCode plugin development?

OpenCode plugin development uses a structure that includes SKILL.md frontmatter for metadata and optional directories for scripts, references, and assets to ensure plugins load correctly.

Can I use a standardized plugin template for both project and global OpenCode environments?

Yes, standardized plugin templates provide a reliable starting point that supports loading plugins in both project-local (.opencode/plugins) and global (~/.config/opencode/plugins) environments.

How do I ensure my OpenCode plugin metadata is complete and compatible?

You ensure OpenCode plugin metadata completeness by using SKILL.md frontmatter, which standardizes the plugin information and maintains compatibility with optional scripts and references directories.

What's the best way to automate OpenCode plugin creation across different environments?

Automating OpenCode plugin creation involves applying standardized templates and clear load path configurations, reducing setup friction across both project and global plugin ecosystems.

Why are my OpenCode plugins not loading from the .opencode/plugins directory?

OpenCode plugins may not load if the SKILL.md frontmatter is incomplete or if the plugin is not correctly placed within the .opencode/plugins or ~/.config/opencode/plugins directories.