Configuring dsh-skills-manager
DeepSeek Harness exposes the plugin options at Sidebar → Plugins → Skills Manager, in the host’s plugins.bundle.config slot.
| Key |
Default |
Behaviour |
sidebarEntry |
false |
Adds or removes a persistent Skills entry under Plugins. The normal Settings → Skills view remains available. |
onlineUpdate / updater |
true |
Controls npm update checks and installation. When disabled, the update button is hidden and update API requests return HTTP 403. |
A Cordis configuration bundle patch can set updater: false or onlineUpdate: false for restricted environments.
How dsh-skills-manager behaves
DeepSeek Harness loads the plugin in a profile such as web. The manager groups content into Global Skills, Project Skills, Discover and Trash, with search, status filters and source groups. It can create skills and import folders, ZIP archives or SKILL.md files into the global user root or a registered workspace. Categories are stored as metadata: dragging or ordering a skill does not move its file.
External agent sources can be pointed at another folder from the panel. DSH and Shared Agent source locations remain controlled by the host. Shared Agent skills are displayed read-only. Soft deletion moves skills into the manager’s Trash view, where restoration retains provenance and update history.
Updates and repositories
The Discover view can browse skills from ClawHub and skills.sh. GitHub repositories can be subscribed to with incremental diff inspection and backups. The header’s Check for updates action checks the npm package when online updates are enabled. Disabling the setting also guards the update endpoint rather than only hiding the control.
Requirements and compatibility
A working DeepSeek Harness installation is required. Version 1.2.21 is tested with DeepSeek Harness 0.2.0-rc.1 through 0.2.1-rc.3 and accepts the documented >=0.2.0-rc.1 <0.3.0-0 range. DeepSeek Harness rejects legacy versions and the 0.3.0 generation; users on 0.1.x are directed to plugin 1.1.23. The README documents support for prefix-stripping reverse proxies, resolving API and update endpoints against document.baseURI.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub