skills.rest
racurry
racurryCOMMUNITY
Explore all skills by this author →
GitHub

plugin-design

Design Claude Code plugins and package components for distribution.

1|Updated Nov 15, 2025
Search Tags:#claude code#packaging#plugin#ai tools#marketplace#distribution#mcp server
One-click install
npx skills add https://github.com/racurry/neat-little-package --skill plugin-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-design
Source: https://github.com/racurry/neat-little-package/tree/main/plugins/forge/skills/plugin-design
Command: npx skills add https://github.com/racurry/neat-little-package --skill plugin-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill guides you in designing and packaging Claude Code plugins for effective distribution and sharing, ensuring your bundled components (agents, commands, skills, hooks) are discoverable, installable, and maintainable, saving development and deployment time.

Core Features & Use Cases:

  • Plugin Architecture & Structure: Clarifies the critical directory structure and plugin.json manifest requirements to ensure successful plugin installation and functionality.
  • Secure MCP Server Configuration: Provides best practices for configuring Model Context Protocol (MCP) servers within plugins, emphasizing security (no hardcoded secrets) and proper documentation.
  • Marketplace Distribution: Explains how to structure marketplace.json for sharing your plugins, enabling easy installation for teams and the community.
  • Use Case: You've developed a suite of Git-related agents and commands. This skill helps you package them into a git-tools plugin, configure its plugin.json, ensure any MCP servers are securely set up, and prepare it for distribution via a marketplace.

Quick Start: Use the plugin-design skill to help me create a new plugin for my custom code analysis tools.

Frequently Asked Questions about plugin-design

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

FAQPage Schema
How do I structure a Claude Code plugin for distribution?▼

Structure your plugin with components at the root directory level, not nested in .claude-plugin/. Define plugin.json with manifest details, configure any MCP servers securely without hardcoded secrets, and organize agents, commands, skills, and hooks for discoverability. This ensures successful installation and marketplace compatibility.

What goes into a plugin.json manifest file?▼

plugin.json declares your plugin's metadata, dependencies, and component locations. It specifies plugin name, version, description, entry points for agents and commands, and MCP server configurations. Proper manifest setup is critical for Claude Code to recognize and load your plugin correctly.

How do I package existing tools and agents into a Claude Code plugin?▼

Gather your components (agents, commands, skills, hooks), organize them at the plugin root with clear directory structure, create plugin.json to reference each component, and configure any MCP servers with secure credentials management. Packaging consolidates your tools for shared distribution.

Can I share my Claude Code plugin on a marketplace?▼

Yes. Structure marketplace.json alongside plugin.json with metadata for discoverability and installation instructions. Follow official docs for format, ensure all components are properly declared in plugin.json, and verify MCP servers are securely configured. This enables teams and the community to install your plugin easily.

What security practices should I follow when configuring MCP servers in plugins?▼

Never hardcode secrets, API keys, or credentials in MCP server configurations. Use environment variables or secure credential stores for sensitive data. Document authentication requirements clearly in plugin.json so users understand what credentials and permissions are needed during installation.

Why should components be placed at the plugin root instead of nested directories?▼

Root-level placement ensures components are discoverable by Claude Code during installation and invocation. Nesting components in .claude-plugin/ or subdirectories breaks the installation mechanism. Enforcing root structure prevents configuration conflicts and aligns your plugin with official packaging standards.

Related Skills

Explore More Software Engineering Skills→
pluginagentmarketplacepluginagentmarketplace
1

plugin-architecture

Design plugin architectures and validate Claude Code plugin structures.

Community
Advanced
ronnycodingronnycoding
20

create-claude-plugin

Create Claude Code plugins bundling skills, agents, commands, hooks, and MCP servers.

Community
Intermediate
Invictusprime7Invictusprime7
1

MCP Integration

Integrate MCP servers into Claude Code plugins via .mcp.json or plugin.json.

Community
Advanced
emdashcodesemdashcodes
13

claude-code-plugins

Plan, package, and distribute Claude Code plugins and marketplaces.

Community
Intermediate