plugin-marketplace-setup

Designs skill and plugin marketplaces with manifests and install matrices for Cursor, Claude Code, Codex, and Zed.

2|Updated Aug 15, 2026
One-click install
npx skills add https://github.com/Arenukvern/shortly --skill plugin-marketplace-setup-arenukvern
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-marketplace-setup
Source: https://github.com/Arenukvern/shortly/tree/main/.agents/skills/plugin-marketplace-setup
Command: npx skills add https://github.com/Arenukvern/shortly --skill plugin-marketplace-setup-arenukvern

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Distributing agent skills and plugins across Cursor, Claude Code, Codex, Zed, and Open Plugin hosts involves incompatible manifest formats, install paths, and marketplace catalogs, and teams often confuse skills, plugins, and marketplaces or ship broken private registries. ## Core Features & Use Cases - Three-layer decision framework: Distinguishes skills (SKILL.md instructions), plugins (hooks/MCP wiring), and marketplaces (catalogs) with normative rules for when to use each. - Cross-agent install matrices: Provides manifest layouts, install commands, and path tables for Cursor, Claude Code, Codex, Zed, and npx skills, covering both public and private team distribution. - Repo-local copy/init pattern: Supplies a reusable layout and Dart script skeleton for product repos that need to generate local installers copying skills, host manifests, hooks, and marketplace files. - Use Case: A platform team needs to ship an internal plugin bundle to Cursor and Codex users; this Skill guides them to create .cursor-plugin/marketplace.json and .agents/plugins/marketplace.json with correct policy fields, plus a private Git distribution checklist. ## Quick Start Ask the agent to design a private plugin marketplace for Codex and Cursor team installs using this skill.

Frequently Asked Questions about plugin-marketplace-setup

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

FAQPage Schema
How do I set up a private plugin marketplace for Cursor or Claude Code?▼

For Cursor teams, create a private GitHub repo with .cursor-plugin/marketplace.json and import it via Dashboard Settings Plugins. For Claude Code, add a .claude-plugin/marketplace.json and use /plugin marketplace add with a token environment variable for auto-updates.

What is the difference between an agent skill and a plugin?▼

A skill is a portable SKILL.md instruction file installed with npx skills add, while a plugin adds runtime wiring such as hooks, MCP servers, and commands through a vendor manifest. Plugins reference skills by id rather than duplicating SKILL.md files.

How do I distribute skills to multiple agents with npx skills?▼

Run npx skills add owner/repo with agent flags like -a cursor -a claude-code -a codex -a zed to install into each agent's skills path. Use --skill to select one skill, -g for global scope, and --copy instead of symlinks.

Does npx skills install Cursor hooks or MCP servers?▼

No, npx skills installs instruction files only and does not wire hooks or MCP configuration. Cursor hooks require a .cursor/hooks.json file, and MCP wiring must ship through a plugin manifest or a repo-local init script.

Where do Codex marketplace files live?▼

Codex repo or team marketplaces live at $REPO_ROOT/.agents/plugins/marketplace.json, and personal marketplaces at ~/.agents/plugins/marketplace.json. Each entry needs policy.installation, policy.authentication, and a category, with source.path relative to the marketplace root.

When should I use a repo-local copy/init script instead of a marketplace?▼

Use a repo-local init script when skills must ship together with MCP config, hooks, commands, or assets that npx skills cannot install. The product repo owns the script and generated host payloads, and must document cache refresh and rollback steps.