dsh-plugin-hub

DSH users juggle Skills, MCP servers, and native plugins across separate entry points, and keeping track of them gets tedious fast. Plugin Hub pulls everything into a single native panel: open it from the corner icon, manage resources in place, close it and you are back in your session. For workflows that lean on a dozen or so Skills and several MCP services daily, that removes the constant window-hopping.

The panel is organized around three resource types. The Skill section offers workspace filtering, search, toggling, and directory access, with bodies rendered through DSH native Markdown components so edits are immediately visible. The MCP section covers JSON/YAML editing and formatting, environment-variable references, per-field help, toggling, reconnection, standalone connection tests, and deletion; validation rules are read directly from the running DSH instance to avoid config drift. The Plugin section lists non-official native plugins with version and origin, and on desktop surfaces a native management-window hint. An experimental area also handles Agent Teams enablement and toggling, available in the browser and on desktop builds that expose the required API.

Plugin Hub is built for power users who treat DSH as their daily driver and rely on multiple Skills and MCP services at once, especially in teams that need consistent bilingual configuration conventions. Every management action is scoped to the current instance profile: toggling a Skill never touches shared files, and deleting an MCP entry only removes the definition created by the Hub or that profile. Those clear boundaries make it safe to explore configurations without risking a global misfire.