creating-a-plugin

Guide developers in creating opencode plugins with structured directories and plugin.json manifests.

8|1|Updated Feb 25, 2022
One-click install
npx skills add https://github.com/ayubun/dotfiles --skill creating-a-plugin-ayubun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-a-plugin
Source: https://github.com/ayubun/dotfiles/tree/main/configs/opencode/skills/ed3d-extending-opencode/creating-a-plugin
Command: npx skills add https://github.com/ayubun/dotfiles --skill creating-a-plugin-ayubun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating and organizing new opencode plugins, providing a structured guide for file organization, manifest format, and component definitions.

Core Features & Use Cases

  • Plugin Structure: Offers a detailed directory structure for commands, agents, skills, hooks, and MCP servers.
  • Manifest Format: Provides guidance on creating a plugin.json file with essential information.
  • Component Definitions: Defines how to create and integrate commands, agents, skills, hooks, and MCP servers.
  • Use Case: Ideal for developers looking to distribute reusable components across multiple projects in the opencode ecosystem.

Quick Start

Start by creating a directory for your plugin and define its manifest file 'plugin.json'.

Frequently Asked Questions about creating-a-plugin

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

FAQPage Schema
How do I create an opencode plugin with the correct directory structure?

The plugin manifest format requires creating a `plugin.json` file containing essential information about your plugin. This file defines how your structured directory integrates commands, agents, skills, hooks, and MCP servers for cross-project component reuse.

What components can I integrate when developing an opencode plugin?

Component definitions in opencode plugins specify how to create and integrate commands, agents, skills, hooks, and MCP servers. These definitions are organized within a structured directory to support cross-project component reuse.

Do I need to understand the opencode plugin architecture before building a plugin?

Yes, creating opencode plugins requires understanding the opencode plugin architecture and component definitions. This prerequisite knowledge ensures you can correctly structure your directory and define the manifest format.

What is the best way to organize reusable components for multiple opencode projects?

The best way to organize reusable components is by creating an opencode plugin with a structured directory and a `plugin.json` manifest file. This format packages commands, agents, skills, hooks, and MCP servers for cross-project distribution.