authoring-plugin

Package Claude Code skills, commands, agents, hooks, and MCP servers into a distributable plugin.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/rocklambros/rcs --skill authoring-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authoring-plugin
Source: https://github.com/rocklambros/rcs/tree/main/skills/claude-code-meta/authoring-plugin
Command: npx skills add https://github.com/rocklambros/rcs --skill authoring-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from bundling multiple Claude Code artifacts into a publishable plugin, helping authors avoid ad hoc layouts, missing metadata, and unsafe releases.

Core Features & Use Cases

  • Plugin Scaffolding: Defines the standard Claude Code plugin structure, including the manifest and the auto-discovered artifact subdirectories.
  • Publication Readiness: Covers the required plugin metadata, marketplace entry, license file, changelog, and version pinning needed for distribution.
  • Security Review: Calls out the extra scrutiny required for bundled hooks, lifecycle scripts, and MCP servers before they are shipped.
  • Use Case: A team with several skills, commands, and a subagent can turn them into a single installable plugin instead of shipping each piece separately.

Quick Start

Use this skill to bundle my Claude Code skills, commands, agents, hooks, and MCP servers into a publishable plugin with the required manifest, marketplace entry, and security checks.

Frequently Asked Questions about authoring-plugin

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

FAQPage Schema
How do I package Claude Code skills and commands into a single distributable plugin?

To package Claude Code artifacts into a plugin, you need a .claude-plugin manifest and standard subdirectories for auto-discovered skills, commands, and agents to ensure proper distribution.

What is required to publish a Claude Code plugin to the marketplace?

Publishing a Claude Code plugin to the marketplace requires complete plugin metadata, a marketplace entry, a license file, a changelog, and strict version pinning for reliable distribution.

How do I perform a security review for bundled hooks and MCP servers in a plugin?

Performing a security review for bundled hooks and MCP servers requires explicitly documenting each artifact's risk surface and applying extra scrutiny to lifecycle scripts before shipping.

Can I bundle multiple Claude Code agents and MCP servers into one installable plugin?

Yes, you can bundle multiple Claude Code agents, hooks, and MCP servers into a single installable plugin, using a multi-artifact publishing workflow to ship them together instead of separately.

Why does my Claude Code plugin release need pinned versioning and a changelog?

Pinned versioning and a changelog are required for Claude Code plugin releases to ensure marketplace publication readiness, maintain license compliance, and track lifecycle changes safely.