[Feature Request] Open marketplace JSON submission/review process for community plugins

Problem / Motivation

Currently, Kimi Code CLI supports a rich plugin ecosystem via the /plugins command and marketplace JSON. The marketplace can be customized via KIMI_CODE_PLUGIN_MARKETPLACE_URL or /plugins marketplace <source>, which is great for personal or team use.

However, there is no documented way for community developers to submit their plugins to the official marketplace. This creates a barrier for plugin authors who want to share their work with the broader Kimi Code CLI user base. As a result, many useful community plugins remain undiscoverable unless users manually install them via GitHub URL.

Request

I would like to request one of the following (or a combination):

1. Open a submission/review channel for marketplace JSON entries — similar to how VS Code extensions or Homebrew formulas are submitted. Plugin authors could submit a PR or fill out a form to have their plugin reviewed and added to the official marketplace.json.

2. Document the criteria and process for getting a plugin listed in the official marketplace. For example:

   • What metadata fields are required/recommended?
   • What trust tier (kimi-official, curated, third-party) applies to community submissions?
   • Are there security review requirements?

3. Provide a community marketplace JSON — a separate marketplace file (e.g., community-marketplace.json) that accepts submissions with lighter review, while the official marketplace remains for vetted plugins.

Why this matters

• Plugin discoverability: Users browsing /plugins won't find community plugins unless they are in the marketplace JSON.
• Ecosystem growth: Lowering the barrier to entry encourages more developers to build and share Kimi Code CLI plugins.
• Trust signals: A curated marketplace gives users confidence when installing third-party plugins, compared to installing arbitrary GitHub URLs.

Related

• The marketplace JSON format is partially documented at Plugins | Kimi Code Docs, showing the version, plugins array with id, displayName, and source fields.
• The trust badges (kimi-official, curated, third-party) are mentioned in the docs but the process to achieve curated status is unclear.

Would love to hear the team's thoughts on this! Happy to help draft submission guidelines or contribute a prototype workflow if there's interest.

Start with the Plugins documentation and the current official marketplace JSON, including the /plugins command and its marketplace source behavior. The issue does not choose between a submission channel, documented criteria, or a community-marketplace.json, so completion would require an agreed scope and process before implementation.