marketplace-dev

Manage plugin marketplace development with version synchronization and naming standards.

2|Updated Feb 22, 2026

Search Tags:#versioning #documentation #validation #configuration #plugin development #marketplace

Ready to run

npx skills add https://github.com/dylan/claude --skill marketplace-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: marketplace-dev
Source: https://github.com/dylan/claude/tree/main/skills/marketplace-dev
Command: npx skills add https://github.com/dylan/claude --skill marketplace-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the development and maintenance of the plugin marketplace, ensuring consistency and adherence to best practices for adding, updating, and managing plugins.

Core Features & Use Cases

Version Synchronization: Enforces matching plugin versions across manifest files.
Path and Naming Conventions: Guides the correct use of relative paths and marketplace naming.
Codebase Auditing: Facilitates updates to architecture documentation after code changes.
Use Case: When adding a new plugin, this Skill ensures all configuration files are correctly updated and versioned, and reminds you to document the changes.

Quick Start

Run the marketplace validation command to check your changes before committing.

Frequently Asked Questions about marketplace-dev

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

FAQPage Schema

How do I manage plugin version synchronization across marketplace manifest files?▼

Plugin version synchronization is managed by enforcing matching plugin versions across manifest files during the development lifecycle. This ensures consistency and adherence to best practices when adding or updating plugins in the marketplace.

What path and naming conventions do I need for plugin marketplace configuration?▼

Plugin marketplace configuration requires adherence to specific relative path conventions and marketplace naming standards. These conventions guide the correct use of paths to maintain consistency across the marketplace.

How do I add a new plugin to the marketplace without breaking existing configuration?▼

Adding a new plugin requires correctly updating and versioning all marketplace configuration files. This process includes validating changes and updating architecture documentation to ensure no existing configurations break.

When should I run marketplace validation during plugin development?▼

Marketplace validation should be run to check your changes before committing. This validation enforces version synchronization, path conventions, and naming standards to ensure public repository safety and consistency.

Does updating marketplace plugins require architecture documentation updates?▼

Yes, updating marketplace plugins requires architecture documentation updates. The codebase auditing process facilitates updates to architecture documentation after code changes to maintain accurate records.