dsh-plugins

dsh-plugins

简体中文 / English

A small pnpm monorepo for focused DeepSeek Harness plugins and shared libraries that do not need a repository of their own. Each package under plugins/ tests and releases on its own; bundles and native presets install through DSH.

The current workspace targets DSH 0.2.0-rc.2, with Cordis 4.0.4 and Schemastery 3.18.4. Development dependencies are pinned together; installed plugins use open host compatibility ranges and optional DSH peers. This source baseline does not change the versions already published on npm.

This README also catalogs klarkxy's public DSH plugins on npm, including packages maintained in other repositories. The browsable version is the plugin site. List preview releases in both READMEs; add a DSH plugin to site/catalog.json once npm has its latest release.

Published plugins

Package names link to npm or the package README; the last column provides the other entry point. Follow each plugin's documentation for installation, host compatibility, and configuration.

Install

Published plugins install with the DSH plugin manager, which pulls the package from the npm registry:

dsh plugin --profile web add @klarkxy/dsh-dev-index

Replace web with your profile name, and restart the profile after installing. Each plugin's page on the plugin site lists its own install commands in dependency order.

Creator mode uses dsh_docs_search/dsh_docs_fetch from dsh-dev-index to read live official DSH documentation and verify runtime contracts, and dsh_plugins_search/dsh_plugins_fetch to check plugin npm metadata before installing anything.

Plugin site

https://klarkxy.github.io/dsh-plugins/ lists every plugin in Chinese and English. Each plugin gets a detail page with install commands in dependency order, the package README, requirements, and version history; the site also publishes plugins.json and llms.txt for tools and agents.

site/catalog.json is the only hand-maintained data: slug, package, category, titles and summaries, README paths, and source repository. Versions, dates, dependencies, READMEs, and icons come from the npm registry and integrity-checked npm package archives at build time, so a release from another repository shows up without a commit here.

pnpm site:build   # fetch live data and write _site/
pnpm site:test    # offline rendering tests, also part of pnpm check

.github/workflows/pages.yml builds and deploys _site/ on every main push, after each npm publish run, and once a day. When npm cannot be reached or a package archive fails verification the build fails and the previous deployment stays online. Pages → Source must be GitHub Actions, and old development-index URLs such as /areas/*.html redirect to the official DSH documentation.

Development

Requires Node.js 24 or newer (26 verified; 26 is not yet LTS) and pnpm 10.

pnpm install
pnpm check

Each package owns its assets, tests, and release version. Native presets need no runtime plugin or build. The repository root is not a DSH bundle.

Plugin lifecycle

Packages move through an irreversible lifecycle: Draft → Testing → Published. See the release guide for the full rules.

License

SATA License 2.1

Editor public-plugin extraction

Portable packages extracted from Editor are now maintained under plugins/, keeping their package names, tool behavior, and persisted settings; Zhihu swaps its private UI dependency for a package-local structural control adapter. Manuscript, proofread, and application-private packages remain in Editor, and desktop preinstallation and offline startup are unchanged. Details, including the handoff and validation record, are in the migration document.