I installed 7 plugins in DeepSeek Harness. Then I built a control hub for them.

Description and use

A unified hub skill for DeepSeek Harness consolidates plugin routing, status checks, and provenance tracking, simplifying post‑installation management.

Problem

Managing multiple DeepSeek Harness plugins becomes difficult after installation due to scattered entries, uncertain status, trust management, and lack of manifest tracking.

Outcome

Unified control hub reduces complexity, ensures accurate status reporting, enforces trust, and maintains a clear provenance record for all DeepSeek Harness plugins.

Workflow

• 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.ps1 to verify plugin readiness before dispatch
• Run Cisco's skill-scanner before installing new skills
• Record any installation refusals and reasons in the manifest

Evidence

Installing is easy: dsh plugin --profile desktop add <pkg> with HMR mounting it live. The pain starts after

Source

I built the governance layer itself as a skill: dsh-plugin-hub (open source, MIT).

Source

One routing table. The SKILL.md is a table: user intent → which tool → current state.

Source

One status command. status.ps1 checks everything in one shot: profile plugins, tool files on disk, services up/down, where the skill junctions point.

Source

All my skills live in one directory (easy to back up and sync), junctioned into %USERPROFILE%\.dsh\skills so DSH hot-loads them.

Source

Every install/remove updates a table: version, source, license, how it was verified.

Source