Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Describe process for creating private plugins

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

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:

Fix Action

Fix / Workaround

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

RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

Update the documentation to include information on creating and using private plugins, clarifying that a private marketplace is a workaround for hosting private plugins.

Guidance

  • Add a section to the documentation that explicitly explains how to create and use private plugins, addressing the current lack of information on this topic.
  • Consider adding a FAQ section with answers to common questions, such as "How do I create a private plugin?" and "What do I do if I don't want my plugin to be public?"
  • Emphasize the distinction between public and private marketplaces, and the implications of each, to avoid user confusion.
  • Review the current documentation for any language that may imply that creating a marketplace is the only way to install a plugin, and revise as necessary to reflect the possibility of private plugins.

Example

No code snippet is provided as the issue is related to documentation and user experience.

Notes

The current workaround of creating a private marketplace to host a private plugin may be counterintuitive and poses a risk of accidental public exposure. A clear and concise documentation update can help mitigate this issue.

Recommendation

Apply workaround: Update the documentation to include information on private plugins, as this will provide clarity and guidance for users without requiring significant changes to the underlying system.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#model download#tokenizer error#prompt formatting#chain error#conversation history

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] Describe process for creating private plugins