plugins-management

Create and validate Claude Code and OpenCode plugin structures for marketplace submission.

119|10|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/CodeAlive-AI/ai-driven-development --skill plugins-management-codealive-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugins-management
Source: https://github.com/CodeAlive-AI/ai-driven-development/tree/main/skills/plugins-management
Command: npx skills add https://github.com/CodeAlive-AI/ai-driven-development --skill plugins-management-codealive-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Plugins for Claude Code and OpenCode often require strict, platform-specific structure, manifests, and validation steps, plus careful handling of install/uninstall and marketplace submission workflows.

Core Features & Use Cases

  • Create plugins with correct scaffolding: Generate the base directory structure and optional components (commands, agents, skills, hooks, MCP config).
  • Manage plugin marketplaces: Initialize marketplaces, add plugins, and ensure marketplace manifests follow the expected format.
  • Validate plugin structure before release: Run validation for plugin.json and required files to reduce broken installs.
  • Prepare official directory submissions: Gather repo/SHA/metadata needed for Anthropic directory submission.
  • Safe deletion and uninstall workflow: Enforces explicit user confirmation (via AskUserQuestion) before any removal actions.

Quick Start

Use plugins-management when you want to create a new Claude Code or OpenCode plugin from scratch and publish it after validation.

Frequently Asked Questions about plugins-management

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

FAQPage Schema
How do I create a Claude Code plugin from scratch?

Creating a Claude Code plugin requires scaffolding the base directory structure and a plugin.json manifest, then defining optional components like commands, agents, skills, hooks, and MCP config to ensure correct installation behavior.

How do I validate plugin structure before submitting to a marketplace?

Validating plugin structure involves running checks on your plugin.json manifest and required files to ensure they follow expected formats, which reduces broken installs and enforces consistent discovery behavior across agent ecosystems.

What is needed to prepare an OpenCode plugin for official directory submission?

Official directory submission requires gathering your repository URL, commit SHA, and necessary metadata to satisfy deterministic plugin lifecycle requirements for registration and distribution.

Can I manage a plugin marketplace and add new plugins to it?

Yes, you can initialize a plugin marketplace, add plugins to it, and ensure the marketplace manifests follow the expected format for consistent discovery and installation behavior across supported agent ecosystems.

Is it safe to uninstall or delete agent plugins?

Deleting or uninstalling agent plugins is safe because the process enforces explicit user confirmation before executing any removal actions, preventing accidental data loss during plugin lifecycle management.

What components can I define when authoring an agent plugin?

When authoring an agent plugin, you can define commands, agents, skills, hooks, and MCP config within the plugin.json structure to establish the plugin's functional behavior across platforms.