List and inspect marketplaces

stable

Read the local marketplace registry: list every entry with its plugin counts, then open one by ID for a per-plugin table of names, versions, and state.

Author: Poul Kjeldager
Usage: pks marketplace list && pks marketplace show <ID>
Category: infrastructure

Examples

$ pks marketplace list

See every registered marketplace and its counts

$ pks marketplace show my-marketplace

Read one marketplace plugin by plugin

pks marketplace list and pks marketplace show are the read side of the registry. Both are local: they print what was captured at the last add or refresh and make no network call, so what you see is a snapshot, not the live state of the source.

1. Prerequisites

  • At least one registered marketplace. Register one first with pks marketplace add. With an empty registry, list prints a hint instead of a table.

2. List everything

pks marketplace list

The output is a table with one row per marketplace: ID, label, source, an enabled-of-total plugin count, and the date the entry was added. Use it to find the exact ID that the other subcommands require.

3. Inspect one marketplace

Pass the ID from the list to show:

pks marketplace show my-marketplace

You get the label, the source type together with its URL or its repository and ref, the added and last-fetched timestamps, and a per-plugin table of name, version, enabled state, and description. This is the view to read before running enable or disable, because plugin names must match exactly.

Options

Neither command takes flags.

CommandArgumentRequiredDescription
pks marketplace listNo arguments.
pks marketplace showIDyesMarketplace ID.

Troubleshooting

show exits with "not found". The ID is the marketplace name from the fetched document, or the --label override supplied at add time — not the source URL or the owner/repo string. Run pks marketplace list and copy the ID from the first column.

An empty list after adding something. A registry file that cannot be parsed is treated as empty rather than raising an error, so a damaged ~/.pks-cli/claude-marketplace.json reads back as nothing registered. Re-add the marketplace to rebuild the file.

The empty-registry hint names the wrong command. When nothing is registered, list prints a hint referring to pks claude marketplace add. That path is stale in the source message. The real command is pks marketplace add.

The plugin list looks out of date. It is a snapshot. Run pks marketplace refresh to re-fetch the source before trusting the table.

Next steps