[DOCS] Describe process for creating private plugins

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/discover-plugins

Section/Topic

Plugins

Current Documentation

Discover and install prebuilt plugins through marketplaces

Find and install plugins from marketplaces to extend Claude Code with new skills, agents, and capabilities.

Plugins extend Claude Code with skills, agents, hooks, and MCP servers. Plugin marketplaces are catalogs that help you discover and install these extensions without building them yourself.
Looking to create and distribute your own marketplace? See Create and distribute a plugin marketplace.

What's Wrong or Missing?

Plugins are fantastic ways of bundling together Claude primitives.

In certain instances, however, plugins are not suitable for sharing. Consider plugins that might be specific for a team's internal workflow and contain proprietary information about process, etc.

The CLI UX and documentation are a little confusing because the statement that to install a plugin you should a) create a marketplace and b) install your plugin implies that:

1) There's no way to create and use a plugin that doesn't involve creating a marketplace (I think true!)
2) A "marketplace" strongly suggests that the marketplace is intended to be public

The docs does not mention "private" at all. I discovered that private plugins could be created by finding guides like this one on Google.

Suggested Improvement

A simply FAQ: how do I create a private plugin? What do I do if I don't want my plugin to be public?

Answer (weird workaround fro the moment): create a private marketplace. Then add your private plugin. Then install.

This procedure is itself kind of counterintuitive and there's a definite risk that's users would inadvertently add a private plugin to a public marketplace.

Impact

Medium - Makes feature difficult to understand

Additional Context

_No response_