Extensions & Marketplace

Applicable plans: Enterprise

Extensions & Marketplace is used to manage organization-approved plugins and skills. Admins can organize capabilities into collections via a private marketplace, control member visibility, and distribute them to Qoder or QoderWork members as needed.

Suitable for scenarios requiring team practice consolidation, enterprise tool integration, professional workflow reuse, or unified capability distribution.

Core Concepts

Concept	Description
Skill	A reusable capability for specific tasks, e.g., code review, test generation, API documentation generation
Plugin	An installable capability package that may contain skills, commands, MCP servers, etc. Displayed as Expert Kits in the QoderWork client marketplace
Private Marketplace	The entry point for organization members to discover and install enterprise-approved capabilities
Collection	A management unit in the Private Marketplace for organizing plugins or skills of the same category
Distribution	Admin pushes individual plugins or skills from a collection to members

For plugin directory structure, plugin.json, MCP server configuration, Hooks, packaging and distribution, see Plugins.

Private Marketplace

The Private Marketplace is managed by collections. Collections can apply to Qoder, QoderWork, or both.

When connecting to the Private Marketplace, only QoderWork currently supports displaying in the client marketplace; both Qoder and QoderWork support admin distribution. The current Private Marketplace supports QoderWork’s Skill Marketplace and Expert Kits Marketplace, where the Expert Kits Marketplace displays plugin content.

The content type of a collection determines which marketplace it appears in within QoderWork:

Content Type	Display Location in QoderWork
Skills	Skill Marketplace
Plugins	Expert Kits Marketplace

Collections

Collections are used to organize plugins and skills in the Private Marketplace. When creating a collection, confirm the following:

Field	Description
Collection name	The name visible to members or admins
Description	Explains the target team, scenario, or content boundary
Product	Whether the collection applies to Qoder, QoderWork, or both
Content type	Whether the collection contains plugins or skills
Marketplace visibility	Controls which members can discover this collection in the QoderWork client marketplace

Tip: A collection manages only one content type. Create separate collections for plugins and skills when both need management.

Uploading Plugins or Skills

Admins can upload enterprise-owned plugins or skills to the current collection. The uploaded content type must match the collection’s content type.

Content Type	ZIP Package Requirements
Plugin	ZIP root directory must contain a .qoder-plugin/ directory
Skill	ZIP root directory must contain a SKILL.md file

After uploading, the content appears in the current collection. Admins can continue to configure categories, view version information, or set up distribution.

Managing Content

Content in a collection can be configured with categories, distribution scope, and distribution strategy.

Categories help members understand and find content in the Private Marketplace. Use stable, easy-to-understand category names such as Code Review, Testing, Documentation, Data.

Removing content from a collection only removes its relationship with the current collection — it does not delete the original plugin or skill package.

Configuring Distribution

Distribution configuration applies to individual items within a collection. Both Qoder and QoderWork support admin distribution.

Distribution Scope	Description
Not distributed	Not distributed by admin; if the collection is visible to members, they can still self-install
Distribute to all	Distributed to all members in the organization
Distribute to groups	Distributed to specified member groups

Distribution Strategy	Description
Client configurable	Members can view and configure the content in their client
Force enabled	Content is displayed in the client and kept enabled
Silent enable	Content is not displayed in the client but enabled in the background

Marketplace visibility and distribution scope are two different concepts:

Scope	Controls	Effect
Marketplace visibility	Collection	Whether members can discover this collection in the QoderWork client marketplace
Distribution scope	Individual content	Whether members receive the admin-distributed content

If the distribution scope is larger than the marketplace visibility, some members may receive client content but cannot search for it in the QoderWork client marketplace.

FAQ

What is the difference between plugins and skills?

Skills are typically used to complete a specific task. Plugins are installable capability packages that can contain one or more skills, as well as commands, MCP servers, and other capabilities. In the QoderWork client marketplace, plugins are displayed as Expert Kits.

Is content in the Private Marketplace always distributed to members?

No. Private Marketplace visibility means members can discover content in the QoderWork client marketplace; whether it is distributed depends on the content’s distribution scope and strategy.

Does removing content from a collection delete the plugin or skill?

No. Removing content from a collection only removes its relationship with the current collection — it does not delete the original plugin or skill package.