Introduction

If you have already placed Claude-side configurations in the user home directory or project root, such as .claude/skills, .claude/rules, .mcp.json, CLAUDE.md, and do not wish to copy these files and manually connect them to DSH, the plugin below is introduced: The accurate name of dsh-claude-maurator is dsh-claude-migrator. It loads the aforementioned configurations as DSH capabilities and provides a panel to view Skills, Rules, MCP, and connection status.

What is it

The positioning of dsh-claude-migrator is “Claude → DeepSeek Harness (DSH) Configuration Migration Plugin (Universal Template)”. Documentation indicates it is a clean, publishable template that does not carry specific project skills/rules/MCP.

The license is MIT. The engines requirement in package.json is:

"node": ">=18"

The repository path is huanghouchun/dsh-claude-migrator; the author field in package.json is sanmao5, and it has not been confirmed whether the two refer to the same person.

Core Capabilities

Automatic Skills Loading

SKILL.md files in the following locations will enter the DSH skill registry, and models will be automatically loaded based on whenToUse:

  • User directory: ~/.agents/skills
  • User directory: ~/.claude/skills
  • Project root: .claude/skills
  • Plugin-related directory: .dsh/dsh-claude-migrator/skills/

Automatic Rules Conversion

.claude/rules/*.md files are automatically converted into skills, and whenToUse preserves the paths path semantics.

Real MCP Connection

.mcp.json files at the user, project, and plugin levels are dynamically registered as dsh-mcp-client instances at startup, utilizing real connections, and possess the ability to automatically reconnect.

Keys support ${VAR} placeholders, which are automatically expanded to environment variables. Servers with unset keys will automatically skip registration and will not block DSH startup.

CLAUDE.md Support

CLAUDE.md requires no additional processing. DSH’s dsh-agent-instructions is loaded by default; candidate files include:

  • AGENTS.md
  • CLAUDE.md

Workspace Isolation

Skill activation uses the provider mechanism and is isolated based on the current session workspace. Project-level .claude/skills can be used normally and will not interfere across projects.

Configuration Panel

Panel entry points include:

  • Sidebar “Claude Configuration Center”
  • Workspace “⋯” menu

The panel displays:

  • Skills list
  • Rules list
  • MCP list
  • Connection status

Each skill, rule, and MCP card carries a “Global / Project / Plugin” badge to distinguish the configuration source.

The panel follows the current workspace switch; after switching projects, the dashboard refreshes in real-time.

The three sections of Skills, Rules, and MCP can be collapsed independently; they are collapsed by default, and the manual expanded or collapsed state is preserved after refresh.

Colors use CSS variables:

--dsh-cm-*

and switch automatically between dark and light themes with:

body[data-ds-dark-theme]

Installation and Activation

Installation command:

dsh plugin --profile web add dsh-claude-migrator

Restart dsh web to apply changes after installation.

Verify if the plugin is loaded:

dsh --profile web --dump-config | grep -i "claude-migrator"

If loaded successfully, you should see the dsh-claude-migrator plugin line.

Uninstall command:

dsh plugin --profile web remove dsh-claude-migrator

Typical Usage

  1. Original configurations in the project root take effect directly
    Existing .claude/, .mcp.json, and CLAUDE.md in the project root do not require moving files.

  2. Global configurations are automatically merged
    From the user home directory:
    - ~/.agents/skills
    - ~/.claude/skills
    - ~/.dsh/dsh-claude-migrator/

will automatically enter the dashboard and registry.

  1. View the results
    Open the dashboard from the sidebar “Claude Configuration Center” entry to view the Skills, Rules, MCP lists, and connection status.

  2. Configure MCP
    .mcp.json can be placed in the project root or in:

   ~/.dsh/dsh-claude-migrator/.mcp.json

Servers will automatically register as real connections at startup. It is recommended to continue using ${VAR} placeholders for keys, expanded by environment variables.

  1. Add a new skill
    Pay attention to the following when adding a new skill:
    - Directory names should use kebab-case
    - SKILL.md must contain name and description
    - Only scan one level of directory
    - Restart dsh web after changes

Applicable Scenarios and Notes

This plugin is suitable for developers who are already using Claude configurations and wish to integrate these configurations into DSH. It unifies the loading paths of skills, rules, MCP, and CLAUDE.md to the DSH side and provides a panel for viewing status.

It is recommended to confirm the following before use:

  • License is MIT
  • The plugin runs with the permissions of the current dsh process; you should check the source code and license before installing
  • This repository is a template and does not contain specific project skills/rules/MCP
  • If using the file: installation method, the plugin will be copied; you need to re-add the plugin after changing the source code
  • DSH’s plugin ecosystem emphasizes “everything is a plugin”; the community directory is an independent site with no official affiliation with DeepSeek / Hypothesis

Reference Links

GitHub:

https://github.com/huanghouchun/dsh-claude-migrator

Directory page, URL obtained from clues, without scraping the directory page content for verification:

https://www.skillhub.cn/plugins/huanghouchun/dsh-claude-migrator