What is required in a plugin manifest?

A plugin requires a plugin.json file located in a .claude-plugin directory, containing metadata like name, version, and author information.

Do Claude Code plugins support MCP?

Yes, plugins can include .mcp.json configurations to integrate external Model Context Protocol servers for expanded tool access.

Can I share plugins with my entire team?

Yes, by configuring marketplaces in your project's .claude/settings.json file, plugins can be automatically distributed to team members who trust the folder.

What is a Claude Code plugin?

A plugin is a specialized extension that adds custom slash commands, agents, skills, or hooks to Claude Code, allowing for domain-specific task automation.

How do I install a plugin from a marketplace?

You can add a marketplace using '/plugin marketplace add [source]' and then install specific plugins using the '/plugin install [name]' command.

Plugin & Marketplace Management

Name: Plugin & Marketplace Management
Author: reggiechan74

byreggiechan74

Developer Tools

Streamlines the creation, installation, and distribution of custom Claude Code plugins and centralized marketplaces.

About

This skill provides a comprehensive framework for extending Claude Code's core functionality through a modular plugin system. It guides users through building custom slash commands, specialized agents, and MCP server integrations while managing their distribution via JSON-based marketplaces. Whether you are developing local tools for personal productivity or architecting organization-wide automation workflows, this skill ensures standardized versioning, easy team onboarding, and seamless discovery of new capabilities within the Claude Code environment.

Key Features

Automated team distribution through repository-level settings
Support for agents, hooks, and Model Context Protocol (MCP) integrations
Custom slash command definition using Markdown-based logic
0 GitHub stars
Plugin lifecycle management including creation, installation, and updates
Centralized marketplace discovery via GitHub, Git, or local paths

Use Cases

Creating custom slash commands for project-specific automation
Managing and versioning AI-driven developer utilities across multiple repositories
Standardizing internal development workflows across engineering teams

About

Key Features

Automated team distribution through repository-level settings
Support for agents, hooks, and Model Context Protocol (MCP) integrations
Custom slash command definition using Markdown-based logic
0 GitHub stars
Plugin lifecycle management including creation, installation, and updates
Centralized marketplace discovery via GitHub, Git, or local paths

Use Cases

Creating custom slash commands for project-specific automation
Managing and versioning AI-driven developer utilities across multiple repositories
Standardizing internal development workflows across engineering teams