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

opencode-plugins

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenCode plugin development often lacks a clear, repeatable packaging and runtime contract, leading to broken plugins and inconsistent deployments.

Core Features & Use Cases

  • Plugin packaging: ensure plugins are packaged with correct runtime expectations and metadata.
  • Plugin modification: update plugin code and tests while maintaining compatibility.
  • Use Case: When adding a new plugin, ensure packaging and runtime behavior align with OpenCode plugin docs.

Quick Start

Create a new OpenCode plugin project using the plugin scaffold and validate packaging with the plugin docs.

Frequently Asked Questions about opencode-plugins

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

FAQPage Schema
How do I package an OpenCode plugin for local and CI environments?▼

To package an OpenCode plugin, you must enforce correct frontmatter metadata and runtime contracts. This ensures your plugin maintains consistent deployment behavior and packaging expectations across both local development and CI environments.

Why does my OpenCode plugin break during runtime after modification?▼

OpenCode plugin runtime breaks occur when modifications violate established runtime contracts or frontmatter metadata. Validating plugin code and tests against OpenCode plugin docs ensures compatibility and prevents inconsistent deployment behavior.

What is the best way to validate OpenCode plugin packaging before deployment?▼

The best way to validate OpenCode plugin packaging is to check frontmatter metadata and runtime behavior against the plugin docs. This enforces correct runtime expectations and prevents broken plugins from reaching deployment.

Do I need specific frontmatter metadata to build OpenCode plugins?▼

Yes, correct frontmatter metadata is required to build OpenCode plugins. Enforcing this metadata ensures your plugin meets the necessary runtime contracts and packaging requirements for reliable deployment.

Can I use the OpenCode plugin scaffold to test existing plugin code?▼

Yes, you can use the plugin scaffold to test and modify existing plugin code. It enforces runtime contracts and frontmatter metadata validation, ensuring your modified plugin maintains compatibility during testing and deployment.

Related Skills

Explore More Software Engineering Skills→
xjiang77xjiang77

skill-packager

Package skills into a distributable Claude Code plugin with metadata and commands.

Community
Intermediate
ThejanaJayalathThejanaJayalath

ai-regression-testing

Automate regression testing for AI-assisted development with Vitest and Next.js.

Community
Advanced
tyronerosstyroneross
1

plugin-tests

Validate Claude Code plugin structure and integrity with static analysis tests.

Community
Intermediate
open-haxopen-hax
6

opencode-plugin-authoring

Automate OpenCode plugin scaffolding, packaging, and documentation alignment.

Official
Intermediate