A marketplace is a curated catalog of installable plugins. Point 100xprompt at one - a hosted URL, a git repository, or a folder on disk - and every plugin it lists becomes searchable and one command away from installed. Publishing your own is just as simple: write a small listing file, host it, and share the source.

​
How a marketplace works

Think of a marketplace as an index. You add a source once, browse the plugins it advertises, then install the ones you want. Each installed plugin brings its bundled commands, agents, skills, hooks, and MCP servers into your workspace.
100xprompt ships with a built-in community catalog, so browse returns real, installable plugins even before you add a source of your own.

​
Marketplace commands

All marketplace management lives under 100xprompt plugin marketplace (aliases: market, mp).
CommandWhat it does
100xprompt plugin marketplace add <source>Register a marketplace source (URL, git, or local).
100xprompt plugin marketplace listShow every marketplace source you’ve added.
100xprompt plugin marketplace browseList every plugin available across your added marketplaces.
100xprompt plugin marketplace remove <source>Unregister a marketplace source.
100xprompt plugin install <source>Install a plugin from a source spec.
100xprompt plugin install <name> --from-marketplaceInstall a plugin by its listed name, resolving the source automatically.
marketplace has short aliases (market, mp), list accepts ls, and install accepts add. Use whichever reads best in your workflow.

​
Point at a source

A source spec tells 100xprompt where a marketplace - or an individual plugin - lives. The same three forms work everywhere a source is accepted.
A plain http(s) URL that points directly at a marketplace listing file hosted on any static host - a CDN, object storage, or a raw file link.
100xprompt plugin marketplace add https://plugins.example.com/marketplace.json
Git sources are fetched fresh when you browse, so a marketplace stays current as its author adds plugins - no re-adding required.

​
Add a marketplace

Suppose your team publishes its plugins to a shared git repo. Register it once, then everything it lists is a browse away.
1

Register the source

Add the marketplace by its URL, git spec, or local path.
100xprompt plugin marketplace add github:acme/plugins
2

Confirm it's registered

List your sources to verify it was added.
100xprompt plugin marketplace list
3

Browse what it offers

See every plugin advertised across all your marketplaces.
100xprompt plugin marketplace browse
Each entry shows the plugin name, which marketplace it came from, a short description, and the exact command to install it.

​
Install a plugin

1

Find a plugin

Browse your marketplaces and note the plugin you want.
100xprompt plugin marketplace browse
2

Install it

Install by name straight from your added marketplaces:
100xprompt plugin install devkit --from-marketplace
Or install directly from any source spec - no marketplace required:
100xprompt plugin install github:acme/plugins/devkit
3

Activate it

Restart 100xprompt (or reload your config) so the plugin’s commands, agents, skills, hooks, and MCP servers come online. Confirm with:
100xprompt plugin list
You can enable, disable, or remove any installed plugin later with 100xprompt plugin enable <name>, disable <name>, and remove <name> - disabling keeps it on disk so you can turn it back on instantly.

​
Publish your own marketplace

Suppose you want to share a set of plugins with your team or the wider community. Write a single listing file named marketplace.json (or 100xprompt-marketplace.json) at the root of a git repo, static host, or folder, then share that source. The file names your catalog and lists the plugins it offers.

​
Listing file fields

Top level:
FieldRequiredDescription
nameYesDisplay name of your marketplace.
descriptionNoOne-line summary shown alongside the catalog.
pluginsYesArray of plugin entries (see below).
Each entry in plugins:
FieldRequiredDescription
nameYesThe plugin’s name, used for install-by-name and de-duplication.
sourceYesWhere the plugin lives - a source spec (git, URL, or a path relative to a local marketplace).
descriptionNoShort summary shown when browsing.
versionNoVersion string for the plugin.
authorNoWho publishes the plugin.
installsNoUnique install count, if you track one.
When your marketplace is a local folder, a plugin’s source can be a relative path - it resolves against the marketplace root. Hosted and git marketplaces should use absolute source specs (a git spec or URL).

​
Example listing

marketplace.json
{
  "name": "acme-plugins",
  "description": "Curated plugins for the Acme engineering team",
  "plugins": [
    {
      "name": "devkit",
      "source": "github:acme/plugins/devkit",
      "description": "Everyday dev toolkit: changelog command, commit skill, and a destructive-command guard hook",
      "version": "1.0.0",
      "author": "acme",
      "installs": 1200
    },
    {
      "name": "release-tools",
      "source": "github:acme/plugins/release-tools@v3",
      "description": "Automated version bumps, tagging, and release-note drafting",
      "version": "3.1.0",
      "author": "acme"
    }
  ]
}
1

Write the listing file

Create marketplace.json with your catalog name and a plugins array.
2

Publish the source

Commit it to a git repo, upload it to a static host, or keep it in a shared folder.
3

Share the source spec

Give users the one line they need - for example 100xprompt plugin marketplace add github:acme/plugins. From there they can browse and install everything you offer.
Plugin names must be unique across all of a user’s added marketplaces - if two marketplaces list a plugin with the same name, only the first is shown. Choose distinctive names to avoid being shadowed.

Plugins

What plugins bundle - commands, agents, skills, hooks, and MCP - and how to build one.

Skills

Package focused capabilities as skills your agents can call on demand.