I installed 7 plugins in DeepSeek Harness. Then I built a control hub for them.
说明与用途
为 DeepSeek Harness 创建统一的插件管理中心,整合路由表、状态检查和来源记录,简化插件安装后管理。
问题
Managing multiple DeepSeek Harness plugins becomes difficult after installation due to scattered entries, uncertain status, trust management, and lack of manifest tracking.
结果
Unified control hub reduces complexity, ensures accurate status reporting, enforces trust, and maintains a clear provenance record for all DeepSeek Harness plugins.
工作流
- Install plugins with
dsh plugin --profile desktop add <pkg> - Create a unified skills directory and junction it to
%USERPROFILE%\.dsh\skills - Implement dsh-plugin-hub skill with routing table, status command, and manifest updates
- Use
status.ps1to verify plugin readiness before dispatch - Run Cisco's skill-scanner before installing new skills
- Record any installation refusals and reasons in the manifest
证据
Installing is easy: dsh plugin --profile desktop add <pkg> with HMR mounting it live. The pain starts after
I built the governance layer itself as a skill: dsh-plugin-hub (open source, MIT).
One routing table. The SKILL.md is a table: user intent → which tool → current state.
One status command. status.ps1 checks everything in one shot: profile plugins, tool files on disk, services up/down, where the skill junctions point.
All my skills live in one directory (easy to back up and sync), junctioned into %USERPROFILE%\.dsh\skills so DSH hot-loads them.
Every install/remove updates a table: version, source, license, how it was verified.
- 记录日期: 2026-10-24T13:11:26.095Z