Preface

The extension capabilities of DeepSeek Harness (DSH) typically revolve around skills, MCP servers, and plugins. In practical use, these objects may originate from built-in presets, user directories, project directories, npm registries, or GitHub repositories. Their states are also distributed across multiple dimensions such as enabled/disabled status, scope, source, and version updates.

Checking each time whether a skill is enabled, whether an MCP is using stdio or streamable-http, or whether a third-party plugin can be updated can be cumbersome and fragmented. dsh-extension-hub provides a centralized management entry point: manage skills, MCP servers, and plugins within the DSH Web settings page, supporting import from tools like Claude/Codex, as well as browsing and installing plugins via the Plugin Market.

What Is This

dsh-extension-hub is maintained by Relistencode and is positioned as:

Manage DeepSeek Harness (DSH) skills and MCP servers from one place.

It includes a zero-dependency persistence core and CLI, along with an embedded persistent settings page UI in DSH Web. The core objective is to centralize common extension management actions in DSH: creating, editing, enabling, disabling, importing, updating, and uninstalling.

This plugin is licensed under MIT. The currently verified version is 0.2.19.

Core Features

Below are the verified commonly used capabilities.

  • List skills/MCP and view enabled state and scope.
  • Create, edit, and delete skills.
  • Enable or disable skills and MCP.
  • Create, edit, and delete MCP, supporting stdio and streamable-http.
  • Import skills and MCP from Claude/Codex and other tools.
  • Perform project-scope installation via folder picker.
  • Manage plugins, distinguishing between official and other plugins, supporting enabling, disabling, and uninstalling.
  • Provide Plugin Market: curated store (npm install) + GitHub search.
  • Check and update third-party plugins.
  • Provide dsh-myrules for editing host-wide global instructions.
  • Provide Add-on manager for installing, disabling, or uninstalling companion features, which update along with the main plugin.

Installation and Enabling

First, ensure the environment meets the prerequisites:

  • DSH is installed and operational, with dsh web available.
  • Node.js ≥ 22.
  • pnpm ≥ 10.

The installation command is as follows:

dsh plugin --profile web add dsh-extension-hub@0.2.19

After installation, restart DSH Web:

dsh web

Upon entering DSH Web, open:

Settings → Extension Management

If an upgrade is needed later, you can use the Check Updates button in the page header.

Typical Usage

Below are explanations based on common operational scenarios.

1. Managing Skills

In Extension Management, you can view the list of skills, including their enabled state and scope.

Common operations include:

  • Viewing the enabled state and scope of current skills.
  • Creating a new skill.
  • Editing an existing skill.
  • Deleting a non-built-in skill.
  • Enabling or disabling a skill.

Built-in skills are marked as Built-in/Preset. They cannot be edited, deleted, or have their state toggled.

If a built-in skill needs to be overridden, you can create a skill with the same name in the user or project directory to override it.

2. Managing MCP Servers

MCP servers can also be managed on the same page.

Supported capabilities include:

  • Listing MCP servers.
  • Creating a new MCP server.
  • Editing an existing MCP server.
  • Deleting an MCP server.
  • Enabling or disabling an MCP server.
  • Supporting both stdio and streamable-http types of MCP.

3. Importing from Claude/Codex

If you have previously maintained skills and MCP in Claude or Codex, you can use dsh-extension-hub to import them.

The verified import scope includes:

  • Importing skills and MCP from Claude.
  • Importing skills and MCP from Codex.
  • Importing skills and MCP from other tools.

This reduces the cost of reconfiguring existing extensions in DSH.

4. Installing to a Specific Directory by Project

For project-scope installation, you can use the folder picker to select the target directory.

This means you can install skills/MCP to the current project scope, rather than only placing them in user-level or host-level configurations.

5. Managing Installed Plugins

The Plugins tab is used to manage plugin rows in the DSH composition.

Verified operations include:

  • Distinguishing between official and other plugins.
  • Viewing plugin details.
  • Enabling or disabling plugins.
  • Uninstalling non-official plugins.
  • Checking for updates to third-party plugins.
  • Updating updatable plugins.

Official plugins can be disabled but cannot be uninstalled. cordis:include is part of the core and cannot be disabled or removed.

For non-official plugins, you can perform uninstall. If the plugin was installed via GitHub clone, uninstalling will also delete the local clone directory.

When disabling a plugin, a warning will be issued: unknown plugins may cause serious issues. Therefore, it is recommended to check unfamiliar plugins before enabling them.

6. Finding Plugins in the Plugin Market

The Plugin Market provides two types of entry points:

  • Curated store: Install curated plugins via npm.
  • GitHub search: Search GitHub repositories tagged with dsh-plugin.

During installation, if the plugin can be sourced from the npm registry, it will be prioritized; otherwise, GitHub clone can be used.

Note:

  • npm registry installs are managed by Extension Hub.
  • Continue using Extension Hub’s Check Updates to update these plugins later.
  • GitHub clone installs only support zero-dependency plugins.
  • Packages with npm runtime dependencies will be rejected, as there is no dependency installation step.

7. Using dsh-myrules

dsh-myrules is a companion feature for editing host-wide global instructions.

If you need to maintain DSH global instructions, you can find the relevant capabilities in the plugin management entry, and enable, disable, or uninstall them based on the current plugin state.

Limitations and Notes

Below are the boundary conditions before use.

Built-in Skills Are Read-Only

Built-in skills are marked as Built-in/Preset.

They belong to the deployment or preset layer, therefore:

  • They cannot be edited.
  • They cannot be deleted.
  • They cannot be enabled/disabled.

To override, please create a skill with the same name in the user or project directory.

Official Plugins and Core Items

Official plugins can be disabled but cannot be uninstalled.

Among them, cordis:include is a core item and cannot be disabled or removed.

Uninstalling GitHub Clone Plugins

Non-official plugins installed via GitHub clone will not only remove the plugin row from the configuration but also delete the local clone directory when uninstalled.

Please ensure there are no local modifications that need to be retained before proceeding.

Clone Installation Only Supports Zero-Dependency Plugins

GitHub clone installs only support zero-dependency plugins.

If the package depends on npm runtime dependencies, it will be rejected.

Update Method

Plugins installed via the npm registry should be uniformly managed by Extension Hub.

It is recommended to use the Check Updates button on the page for checking and updating, to avoid inconsistent update sources.

Pre-Installation Check

Plugins will run with the current dsh process permissions. Before installing third-party plugins, it is recommended to review the source code, license, dependencies, and entry logic.

dsh-extension-hub itself is MIT licensed. The licenses of third-party plugins need to be confirmed individually.

Who Is This For

If you frequently maintain DSH Web configurations, dsh-extension-hub is suitable for the following scenarios:

  • Need to view the enabled state and scope of skills/MCP in one place.
  • Need to create, edit, delete skills or MCP servers.
  • Need to import existing skills and MCP from Claude/Codex.
  • Need to manage official and third-party plugins.
  • Need to check and update third-party plugins.
  • Need to install zero-dependency GitHub DSH plugins.
  • Need to maintain host-wide global instructions.

The entry point is in DSH Web’s Settings → Extension Management.

GitHub URL:

https://github.com/Relistencode/dsh-extension-hub