# AI use cases for DSH Plugin Shop (LivXue/dsh-plugin-shop)

Repo: [LivXue/dsh-plugin-shop](https://github.com/LivXue/dsh-plugin-shop) | Use cases: 4 | Page: https://dedupedai.com/use-cases/livxue-dsh-plugin-shop/

A plugin shop for DeepSeek Harness that lets you browse, install, enable, disable, and update dsh plugins from a catalog that is rebuilt daily and tracked in Git.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Install the plugin shop and browse DSH plugins: https://dedupedai.com/use-cases/livxue-dsh-plugin-shop/install-plugin-shop-in-dsh/
- Have an agent install the shop and verify it loads: https://dedupedai.com/use-cases/livxue-dsh-plugin-shop/agent-installs-shop-and-verifies/
- List your DSH plugin in the community catalog: https://dedupedai.com/use-cases/livxue-dsh-plugin-shop/list-plugin-in-catalog/
- Pull the catalog index to audit plugin counts and rejections: https://dedupedai.com/use-cases/livxue-dsh-plugin-shop/audit-catalog-index-data/

## How to install the plugin shop and browse DSH plugins with DSH Plugin Shop

Repo: [LivXue/dsh-plugin-shop](https://github.com/LivXue/dsh-plugin-shop) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Add the DSH Plugin Shop package to your dsh profile and open the shop page in the sidebar.

**Who it is for:** A developer who runs DeepSeek Harness and wants one place to find, install, and manage community plugins.

**The problem:** Finding and installing dsh plugins by hand means searching npm and GitHub separately and checking each one's compatibility yourself.

**The outcome:** The Plugin shop appears in the dsh sidebar, where you can browse listed plugins and see which ones are marked Incompatible.

### Steps

1. Install the tools: `npm install -g @deepseek-ai/dsh pnpm`, then confirm with `dsh --version` and `pnpm --version`.
2. Run `dsh plugin --profile web add dsh-plugin-shop@0.9.0`, replacing web with your profile name.
3. Restart dsh so it loads the new plugin.
4. Open Plugin shop in the left sidebar and browse the catalog.

### Prompt to paste into your agent

```text
Install the dsh-plugin-shop plugin from the LivXue/dsh-plugin-shop repo into the dsh profile <profile> using `dsh plugin --profile <profile> add dsh-plugin-shop@0.9.0`. Report the output of `dsh plugin --profile <profile> list --depth 0` and confirm that dsh-plugin-shop is listed.
```

### Caveat

The README pins version 0.9.0 on purpose because pnpm 11 may otherwise install an older release, so use the pinned version unless you have checked for a newer one.

Risk, remote script: pnpm can run build scripts from packages it installs, so decide whether to allow build scripts before you install a plugin from the shop.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/livxue-dsh-plugin-shop/install-plugin-shop-in-dsh/

## How to have an agent install the shop and verify it loads with DSH Plugin Shop

Repo: [LivXue/dsh-plugin-shop](https://github.com/LivXue/dsh-plugin-shop) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Let an agent run the non-interactive install steps and confirm the plugin is in the profile.

**Who it is for:** A team lead or developer who wants an agent to set up DSH Plugin Shop on a machine without manual steps.

**The problem:** Setup has several steps that are easy to skip, such as the required --profile option and checking the installed version.

**The outcome:** The agent reports the profile it used, the installed plugin version, and whether DSH Plugin Shop is listed for that profile.

### Steps

1. List available profiles with `ls -1 "${DSH_HOME:-$HOME/.dsh}/profiles" | grep -v '^node_modules$'`.
2. Add the pinned version with `dsh plugin --profile <profile> add dsh-plugin-shop@0.9.0`. (inferred, check the README)
3. Verify with `dsh plugin --profile <profile> list --depth 0`, checking that DSH Plugin Shop is in the output. (inferred, check the README)
4. Restart the profile with `dsh --profile <profile>`. (inferred, check the README)

### Prompt to paste into your agent

```text
For the LivXue/dsh-plugin-shop repo, list the profiles in ${DSH_HOME:-$HOME/.dsh}/profiles, then run `dsh plugin --profile <profile> add dsh-plugin-shop@0.9.0`. Expect a list output from `dsh plugin --profile <profile> list --depth 0` that includes dsh-plugin-shop, and also check that dsh.profile.bundles in <profile>/package.json includes the plugin.
```

### Caveat

The README says exit code 0 only means pnpm resolved the package, so the list check is required to confirm the plugin is really installed.

Risk, credentials: The agent runs commands in your profile directory, and a plugin it installs can read your filesystem and shell, so limit the profile's access before you let an agent run this.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/livxue-dsh-plugin-shop/agent-installs-shop-and-verifies/

## How to list your DSH plugin in the community catalog with DSH Plugin Shop

Repo: [LivXue/dsh-plugin-shop](https://github.com/LivXue/dsh-plugin-shop) | Difficulty: Advanced | Time: 1 hour | Basis: From the README

Add the right keyword and metadata to your npm package so the daily build discovers and lists it.

**Who it is for:** A plugin author who has built a DeepSeek Harness plugin and wants other dsh users to find it.

**The problem:** Authors need to know how discovery works and what makes a plugin fail the screening checks before it appears in the shop.

**The outcome:** Your plugin appears in the catalog after the daily build, or the build report tells you the specific reason it was excluded.

### Steps

1. Add dsh-plugin to the keywords in package.json, and make sure package.json includes a dsh.bundle field.
2. Add a license and a source repository, since the build cannot review a plugin without them.
3. Publish the package to npm, for example with `npm publish`. (inferred, check the README)
4. Wait for the next daily build, then check the rejection report if your plugin is missing.

### Prompt to paste into your agent

```text
Check the package.json of the plugin at <plugin-path> for the dsh-plugin keyword, a dsh.bundle field, a license, and a source repository, as listed in the LivXue/dsh-plugin-shop README. Report any missing item and whether an optional dsh.catalog section is present.
```

### Caveat

The catalog is rebuilt daily, and eligible plugins are listed the next morning, so a new release will not appear immediately.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/livxue-dsh-plugin-shop/list-plugin-in-catalog/

## How to pull the catalog index to audit plugin counts and rejections with DSH Plugin Shop

Repo: [LivXue/dsh-plugin-shop](https://github.com/LivXue/dsh-plugin-shop) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Read the published index.json and its data files to review what the catalog lists and rejects.

**Who it is for:** A researcher or maintainer who wants a snapshot of the DSH plugin ecosystem without browsing the shop.

**The problem:** The shop UI does not show download counts or reviews, so a structured view of listed and rejected plugins takes manual effort.

**The outcome:** A summary of the listed count, the rejected total, the build time, and the plugins in each category.

### Steps

1. Fetch the index with `curl -s https://LivXue.github.io/dsh-plugin-shop/v1/index.json`. (inferred, check the README)
2. Read the count, rejected, and builtAt fields from the response.
3. Use the content hashes in the index to fetch the matching plugins.<hash>.json data file.
4. If a data URL returns 404, fetch index.json again, because it is cached for ten minutes.

### Prompt to paste into your agent

```text
Fetch https://LivXue.github.io/dsh-plugin-shop/v1/index.json and report the schemaVersion, builtAt, count, and rejected fields. Then fetch one plugins data file named in the index and confirm it parses as JSON.
```

### Caveat

The README says each source serves identical data, so a cached or stale index may point to files that no longer exist, and the fetched numbers may differ from the current build.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/livxue-dsh-plugin-shop/audit-catalog-index-data/