Preface¶
DeepSeek Harness (DSH) adopts “everything is a plugin” as its extension method, allowing third-party plugins to enter the same Harness process. Third-party plugins may not be consistent in terms of manifest, source code structure, naming, and permission boundaries, making compatibility issues common during development or deployment.
dsh-plugin-design is a Plugin Design / Migration / Compliance Agent for the DSH third-party plugin ecosystem: it first discovers and inspects plugins, then performs static analysis against the DH-TP-SDK, generating design.md; after user confirmation, it proceeds to the modification, backup, and rollback workflow.
It belongs to the DSH third-party plugin ecosystem; the directory page can serve as an entry point, but it does not represent the DeepSeek official app store.
What is it¶
dsh-plugin-design is a specification analysis and modification helper plugin for DSH third-party plugins. It is maintained by huabai-flowerwhite, licensed under the MIT license, with package.json version 1.1.0.
It does not replace human judgment, nor does it provide authoritative certification. It organizes common check items into a two-stage workflow: Stage 1 is read-only analysis, and Stage 2 executes after confirmation.
Core Features¶
- Discover third-party plugins and check their source code and configuration.
- Perform static analysis against DH-TP-SDK engineering specifications.
- Generate
design.md, documenting the proposed modifications. - After user confirmation, modify the plugin items one by one.
- Support backup and rollback.
- The Host side provides 10
dshpd_*model tools:
dshpd_discover
dshpd_inspect
dshpd_analyze
dshpd_design
dshpd_approve
dshpd_backup
dshpd_apply
dshpd_rollback
dshpd_status
dshpd_report
- The Client side provides a Settings page to demonstrate usage, the two-stage workflow, the tool list, and security boundaries.
- Provide DH-TP-SDK specification smoke test:
npm test
Equivalent to:
node --test
Automatically discovers .test.mjs under tests/.
Note: The Bronze/Silver/Gold, P0–P4, and S0–S4 levels in DH-TP-SDK are engineering specification levels, not official DeepSeek certification.
Installation and Enablement¶
After obtaining the plugin directory, execute the installation command:
git clone <your-repo> dsh-plugin-design
cd dsh-plugin-design
bash install.sh
After installation completes, restart DSH:
Ctrl+C then re-run npx dsh web / dsh web
After restart, you can use it fully:
- The chat box has 10
dshpd_*tools; - “Settings → dsh plugin design” appears as a settings page, used to select folders to scan for third-party plugins.
Compatibility Information:
- Aligned with
@deepseek-ai/dsh0.1.1-rc.2. - Harness version requirement is
>=0.1.1-rc.2. apiLevelis1.
Typical Usage¶
You can directly provide the task scope in the chat box:
Use the dsh plugin design plugin to output a design.md file for modifying the <plugin-name> plugin according to specifications, then ask for my opinion before making the modifications.
The two-stage workflow is as follows.
Stage 1 (Read-only analysis):
discover → inspect → analyze → design
This stage generates design.md without modifying the source code.
Stage 2 (Execute after confirmation):
approve → backup → apply → rollback / report
Here, approve acts as a gate, backup is for backup, apply is for atomic replacement item-by-item, and rollback can be used if the operation fails. The report can output the results.
Applicable Scenarios and Notes¶
Suitable for use in the following scenarios:
- Taking over a DSH third-party plugin and wanting to first view its specification differences;
- Need to perform a standardized modification on a plugin but do not want to directly modify it blindly;
- Want a
design.mdbefore modification, a backup before modification, and the ability to rollback if it fails; - Need to use static analysis results as the basis for modification, rather than directly treating them as certification conclusions.
Things to know before use:
- This plugin runs with the current DSH process permissions; you should check the source code and license before installing.
- Security Level is
S2, Permission Level isP2: read/write access to the target plugin’s workspace files is required. - Network/subprocess/shell/credentials are disabled by default:
network.outbound: false
subprocess.enabled: false
shell.enabled: false
credentials.access: false
- Does not modify Core, does not use private APIs, and does not modify
globalThis/prototypes. - Static analysis is based on heuristic rules, not authoritative certification.
- Manifest parsing is heuristic parsing, not a complete YAML parser.
- Task status (
approval,backup,journal) is in-memory state within the process and becomes invalid after process restart. - Git status/test execution depends on the Agent-side shell tools; the plugin itself does not run shell commands directly.
- When multiple plugins coexist, it is necessary to ensure global uniqueness of package name/row id/slot id, model tool names, and HTTP route prefixes.
- This plugin has not yet migrated to the “Plugin Configuration Card” tier; currently, it is a pure information page.
Closing¶
The value of dsh-plugin-design lies not in “automatically getting it right”, but in breaking down the third-party plugin modification into reviewable steps: analyze first, then design, then confirm, then backup, then execute, and finally rollback if necessary.
- Directory page: https://www.skillhub.cn/plugins/huabai-flowerwhite/dsh-plugin-design
- GitHub: https://github.com/huabai-flowerwhite/dsh-plugin-design