maintaining-a-marketplace

Maintain opencode Plugin Marketplace consistency across plugin.json, marketplace.json, and CHANGELOG.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit helps maintain the opencode Plugin Marketplace by ensuring consistency across plugin.json, marketplace.json, and CHANGELOG.md, preventing sync drift and simplifying the release process.

Core Features & Use Cases

  • Marketplace Schema: Defines the marketplace.json schema for plugin catalogs.
  • Version Management: Guides on versioning plugins and marketplace entries.
  • Release Checklist: Provides a step-by-step process for releasing new plugin versions.
  • Changelog Conventions: Offers guidelines for writing effective changelogs.
  • Validation: Assists in validating marketplace consistency.
  • Creating a New Marketplace: Instructions for setting up new marketplaces from scratch.
  • Adding Plugins: Steps to add new plugins to existing marketplaces.
  • Distribution: Guidelines for distributing marketplaces via git repositories.
  • Team Configuration: Best practices for team configuration and private repositories.
  • Common Mistakes: Identifies and fixes common errors in the marketplace setup.

Quick Start

Use the maintaining-a-marketplace skill to update the version of a plugin and generate a changelog entry for the release.

Frequently Asked Questions about maintaining-a-marketplace

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

FAQPage Schema
How do I prevent version drift between my plugin and marketplace configurations?

Prevent version drift by ensuring consistency across your plugin.json, marketplace.json, and CHANGELOG.md files. Validating these configurations during the release process keeps metadata synchronized and installations reliable.

What is the best way to release a new plugin version to a marketplace?

The best way to release a new plugin version is following a step-by-step release checklist that updates the marketplace schema, manages version numbers, and generates a corresponding changelog entry for consistent distribution.

How do I set up a new plugin marketplace from scratch?

Setting up a new plugin marketplace involves defining the marketplace.json schema to catalog plugins, configuring the directory for git repository distribution, and establishing team configuration best practices for private repositories.

What changelog conventions should I use for plugin releases?

Effective changelog conventions for plugin releases require documenting changes clearly in the CHANGELOG.md file alongside version updates. This ensures users understand modifications and helps maintain marketplace consistency.

What are common mistakes when configuring an opencode plugin marketplace?

Common marketplace setup mistakes include failing to sync metadata between plugin.json and marketplace.json, neglecting changelog updates, and improper version management, which collectively cause sync drift and broken installations.