DSH Plugins Marketplace

DSH Plugins

Plugins

/

dsh-plugins

S

dsh-plugins

Discovered

Self-maintained DeepSeek Harness plugins: one repo, one CI, one npm package per plugin with its own version.

dsh-plugins

Self-maintained DeepSeek Harness plugins and their companion tools: one repository, one CI, and one npm package per plugin with its own version.

Packages

PackageWhat it doesForm
dsh-plugin-mark-unreadAdds a manual "mark as unread" action to workspace session rows, with a self-retiring mechanism for when upstream ships ithost + Web UI, published to npm
dsh-linux-desktop-entryPuts the Linux desktop entrance under the harness's own controls: Settings page, agent tool and /desktop-entry commandhost + Web UI, private (installed from this repo)
linux-dsh-web-entryThe launcher kit the plugin drives: app-menu entry, trusted icon, optional systemd --user serviceshell kit, not a DSH plugin

The plugin ships a copy of the kit so a profile install stays self-contained; npm run verify fails if that copy drifts from packages/linux-dsh-web-entry.

Rules every package follows

These exist because a broken metadata field silently breaks discovery for everyone downstream — npm, the plugin catalog, and the in-app market all read them.

  1. Directory name equals the package name. For scoped packages, drop the scope: packages/dsh-foo for @scope/dsh-foo.
  2. repository carries both url and directory. Write "repository": { "type": "git", "url": "git+https://github.com/ShiTan-677/dsh-plugins.git", "directory": "packages/<name>" }. The catalog derives the source link from repository.url + repository.directory, so a missing directory points readers at the repository root — or at nothing.
  3. homepage points at the package directory, not the repository root.
  4. Every package ships its own bilingual README, its own SemVer, and its own npm publish. A release only touches the packages that changed.
  5. Every package must pass npm run verify from its own directory. The root pnpm verify fans out to all of them.

Usage

# verify every package (Node only — no dependency install needed)
pnpm verify

# install one package into a DSH profile
dsh plugin --profile web add dsh-plugin-mark-unread

Each package's README documents its own behaviour, settings, and compatibility range.

License

MIT — see LICENSE.

Comments

Loading…

Similar plugins

dsh-plugins

by wsxwj123

Independent plugins for DeepSeek Harness, organized as isolated packages in one monorepo.

UI & ExperienceManifest valid

★ 10

↓ 208/wk

MIT

JavaScript

Oct 1, 2026

dsh plugin --profile web add dsh-appearance-gallery

by builtin-pb

The single plugin you need for DSH — build, test, diagnose, and maintain DeepSeek Harness plugins and core.

Development & InfrastructureManifest valid

★ 7

MIT

JavaScript

Sep 19, 2026

dsh plugin --profile web add dsh-developer

by jwilson411

A minimal, tested template for DeepSeek Harness plugins.

Development & InfrastructureManifest valid

★ 0

MIT

JavaScript

Sep 1, 2026

dsh plugin --profile web add dsh-plugin-kit

by icedrop-lab

Independent DeepSeek Harness plugins: cost metrics + browser_use tool. One pnpm monorepo, independently installable and vendable.

Manifest valid

★ 0

MIT

JavaScript

Sep 12, 2026

dsh plugin --profile web add @icedrop-ai/dsh-plugins

by dsh-so

Find DeepSeek Harness plugins from the dsh.so registry — like find-skill, but for dsh plugins.

Tools & CapabilitiesManifest valid

★ 0

Apache-2.0

JavaScript

Sep 11, 2026

dsh plugin --profile web add @dsh-so/dsh-plugin-advisor

by bobby-sheng

Search, inspect, update, and install DeepSeek Harness plugins from DSH Get.

Tools & CapabilitiesManifest valid

★ 0

MIT

JavaScript

Aug 19, 2026

dsh plugin --profile web add dshget-plugin