skills.rest
open-hax
open-haxOFFICIAL
Explore all skills by this author →
GitHub

opencode-plugin-authoring

Automate OpenCode plugin scaffolding, packaging, and documentation alignment.

6|Updated Mar 11, 2026
Search Tags:#documentation#scaffolding#runtime#packaging#plugin#opencode
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill opencode-plugin-authoring
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opencode-plugin-authoring
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/opencode-plugin-authoring
Command: npx skills add https://github.com/open-hax/opencode-skills --skill opencode-plugin-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update OpenCode plugins with correct packaging, runtime behavior, and documentation to ensure smooth integration and consistent UX for plugin authors.

Core Features & Use Cases

  • Plugin scaffolding and packaging: Generate or update the plugin directory structure to meet OpenCode expectations.
  • Runtime contract enforcement: Align plugin runtime with OpenCode interfaces and expectations.
  • Documentation alignment: Produce and update user-facing docs and references to reflect current plugin behavior.
  • Use Case: When starting a new plugin, use this skill to bootstrap packaging and ensure docs are in sync.

Quick Start

Create or update a plugin scaffold under .opencode/skills/opencode-plugin-authoring and run the OpenCode plugin tooling to validate packaging.

Frequently Asked Questions about opencode-plugin-authoring

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

FAQPage Schema
How do I bootstrap and package an OpenCode plugin?▼

To bootstrap an OpenCode plugin, you generate the plugin directory structure under .opencode/skills and run OpenCode plugin tooling to validate the packaging layout and ensure correct runtime behavior.

What does runtime contract enforcement do for OpenCode plugins?▼

Runtime contract enforcement aligns your plugin's runtime behavior with OpenCode interfaces and expectations through structured validations, ensuring smooth integration and a consistent user experience.

How do I keep plugin documentation aligned with runtime behavior?▼

You keep plugin documentation aligned by producing and updating user-facing docs and references to reflect the current plugin behavior during the authoring and packaging process.

Can I update existing plugin packaging or is this only for new plugins?▼

You can update existing plugin packaging. This applies when creating new plugins, updating current packaging layouts, or aligning runtime behavior and docs within the existing plugin package directory.

Do I need any dependencies to scaffold OpenCode plugins?▼

No external dependencies are required to scaffold OpenCode plugins. You create or update the scaffold under the .opencode/skills directory and use the OpenCode tooling to validate it.

Related Skills

Explore More Software Engineering Skills→
cogni-workcogni-work
12

portfolio-setup

Initialize a cogni-portfolio project with company context and directory scaffolding.

Official
Intermediate
open-haxopen-hax
6

opencode-plugins

Build and validate OpenCode plugins with correct packaging and runtime contracts.

Official
Intermediate
NQ-lovecppNQ-lovecpp
6

docs-sync

Analyze main branch code changes to identify missing documentation in docs/.

Community
Intermediate
SterlingChinSterlingChin
1.0k

skill-creator

Scaffold new MARVIN skills with SKILL.md frontmatter and directory structures.

Community
Basic