managing-plugins

Automate Claude Code plugin creation, bundling, and manifest generation.

Updated Nov 26, 2025
One-click install
npx skills add https://github.com/thoeltig/claude-code-toolkit --skill managing-plugins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-plugins
Source: https://github.com/thoeltig/claude-code-toolkit/tree/main/plugins/claude-code-capabilities/skills/managing-plugins
Command: npx skills add https://github.com/thoeltig/claude-code-toolkit --skill managing-plugins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the complex lifecycle of Claude Code plugins, from initial creation and manifest generation to bundling, validation, and distribution. It eliminates manual errors and streamlines the process of sharing reusable AI capabilities across projects and teams.

Core Features & Use Cases

  • Plugin Lifecycle Automation: Create, bundle, validate, and pack plugins with manifest generation and directory structuring.
  • Component Integration: Seamlessly integrate commands, skills, hooks, and Model Context Protocol (MCP) servers into a single, cohesive plugin unit.
  • Marketplace & Distribution: Configure plugins for marketplaces and prepare them for team-shared or public distribution, ensuring easy access and updates.
  • Use Case: A development team wants to share a set of custom git commands and a code-review skill. This Skill can automatically bundle all git-* components and the code-review skill into a single plugin, generate its manifest, validate it against best practices, and prepare it for distribution to a team marketplace, saving hours of manual setup for each team member.

Quick Start

Use the managing-plugins skill to create a new plugin named 'my-dev-tools' and bundle all components prefixed with 'dev-'.

Frequently Asked Questions about managing-plugins

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

FAQPage Schema
How do I automate plugin creation and manifest generation for Claude Code?

Plugin manifest generation automates the creation of plugin.json files that define your plugin's structure, components, and metadata. This Skill bundles commands, skills, hooks, and MCP servers into a single plugin unit, then generates and validates the manifest against best practices, eliminating manual configuration errors.

What's the best way to bundle multiple components into a single Claude Code plugin?

Bundling integrates related commands, skills, hooks, and agents by directory prefix matching—for example, all `git-*` commands and a `code-review` skill into one plugin. This Skill automates component discovery, packaging, and manifest generation to create a cohesive, distributable plugin unit.

How do I prepare a Claude Code plugin for team distribution or marketplace sharing?

Plugin distribution preparation involves validating your plugin structure, generating marketplace configuration, and packaging components for shared access. This Skill handles directory setup, manifest validation, and marketplace generation to ensure your plugin meets distribution requirements and team members can easily install it.

Can I validate my plugin structure against Claude Code best practices?

Plugin validation checks your manifest, component organization, and directory structure against plugin-spec.md and validation-rules.md. This Skill discovers components by prefix, validates the bundle, and flags configuration issues before distribution.

What components can I bundle into a Claude Code plugin?

Claude Code plugins bundle commands, skills, hooks, and Model Context Protocol servers into a single distributable unit. This Skill discovers and packages these components by directory prefix, integrates them into the plugin structure, and generates the required manifest for marketplace or team deployment.

Do I need to manually configure plugin.json, or can it be generated automatically?

Plugin manifest files can be automatically generated by component discovery and bundling. This Skill scans your plugin directory, identifies commands, skills, hooks, and MCP servers, generates plugin.json with correct metadata, and validates it against marketplace requirements—eliminating manual configuration.