Introduction

It is very common to use several Agents on a single machine: Claude Code, Codex, Cursor, and Kimi each maintain their own set of skills directories, located at ~/.claude/skills, ~/.codex/skills, ~/.cursor/skills, etc., which are not interoperable. If you want to switch to or use DeepSeek Harness (DSH) alongside them, you have to reinstall the original skills or manually copy them—you also have to handle directory structures, naming conflicts, and duplication yourself.

The DSH Skill Mover introduced below is designed for this purpose: automatically scan the skills installed on your local machine for various Agents, check them off, move them into DSH, and they will be ready to use immediately after migration.

What is this

DSH Skill Mover (Skill Moving Assistant), repository mjylfz/dsh-skill-mover, author mjylfz, MIT License, current version 1.0.3.

One-sentence positioning: Move skills already installed on other Agents on your computer into DeepSeek Harness with a single click.

The plugin is divided into two halves: the Host half is responsible for scanning, conflict planning, and migration execution, while the Client half provides the settings page interface. The author explains in the README that the plugin is pure JavaScript with no external dependencies on the Host side (hand-written frontmatter parser, path utilities) and works via DSH’s ctx.fs / ctx.shell services.

Core Features

Scanning: 14 Platforms plus the Shared Layer

Open “Settings → Skill Migration”, and the page will automatically scan the skills directories of various Agents on your machine, displaying them grouped by platform. It supports Cursor, Claude Code, Codex, OpenCode, Hermes, OpenClaw, Kimi, Trae, Trae CN, CodeBuddy, Qwen Code, Qoder, Qoder CN, and QoderWork—14 platforms in total—plus the shared layer ~/.agents/skills, which DSH can read natively.

Several typical paths (macOS / Linux):

Shared Layer        ~/.agents/skills
Claude Code   ~/.claude/skills
Codex         ~/.codex/skills
Cursor        ~/.cursor/skills

On Windows, corresponding directories exist under C:\Users\<username>\ (some platforms like Hermes are under AppData\Local). For the complete path table, see docs/agent-skills-migration-research.md in the repository; the README states that these paths have been verified against official documentation or source code.

Checking, Migration, and Deduplication

  • Select the skills you want to migrate by checking them; you can batch migrate multiple skills at once.
  • If the same skill exists in multiple Agents, it will automatically be merged into a group, migrating only one copy; you can choose the source yourself (default recommends the shared layer or the highest-priority source).
  • It can identify duplicate skills—including the same copy simply linked to the shared layer—so they won’t be duplicated during migration.
  • Non-standard skill names will be automatically changed to a format recognized by DSH to ensure they are usable after migration.

Rollback and Security Boundaries

  • The migration result page allows for a one-click “Remove This Migration” rollback that does not affect other installed skills.
  • Fixed copy mode: DSH maintains an independent copy, the original directory remains unchanged, and the original Agent continues to function normally.
  • The plugin will not automatically execute dependency installation commands (to prevent skills from untrusted sources from randomly installing things). Skills with dependencies will be installed by the AI according to instructions in the skill or manually.

Cross-Platform and Effectiveness After Migration

  • Supports macOS / Linux / Windows: path rules for Windows, robocopy copying, and junction links have all been adapted.
  • After migration, DSH automatically discovers new skills without the need to restart.

Installation and Activation

One command for permanent installation (recommended):

dsh plugin --profile web add github:mjylfz/dsh-skill-mover

After installation, restart DSH and open “Settings → Skill Migration” to use. Note that a restart is required here; you do not need to restart when migrating skills later, so do not confuse the two “restarts”.

You can also try it without installation (session-level): send the repository link https://github.com/mjylfz/dsh-skill-mover to the DSH assistant and say “help me install this plugin and run”. The assistant will read the plugin files and load them; after approval to run, use them in “Settings → Skill Migration” as well. Session-level plugins require reloading after a restart.

Typical Usage

  1. Open “Settings → Skill Migration”; the page automatically scans the skills directories of various Agents on your machine and displays them grouped by platform.

  2. Expand a platform card to view the list of skills and check the skills you want to migrate. For skills with multiple sources of the same name, you can expand them to switch the source; checking a version from any platform selects that platform’s source, and the other platform columns will update accordingly.

  3. Click “Migrate Selected N Skills” at the bottom.

  4. After migration, DSH automatically discovers new skills without the need to restart. You can directly say, “Use baoyu-cover-image to generate a cover for this article.”

There are a few default rules worth knowing when checking:

  • Skills in the shared layer marked as “DSH Natively Supported” are checked by default—DSH can use them directly.
  • Skills that are already in DSH are not checked by default to avoid duplicate installation; if you want to update or overwrite them, check “Override Installed”.
  • Skills that are actually the same as the shared layer (for example, simply linked over) are not checked by default, as moving them would also result in duplication.

After the steps above, the skills have been migrated and are stored in the ~/.dsh/skills/ directory. If you migrated incorrectly, click “Remove This Migration” on the migration result page to delete the skills from this migration; the original directories will not be affected.

Can I Use Them Directly After Migration

Yes. A skill is essentially a “manual + supporting materials,” not an installation package. After migration, the AI will automatically open the manual and follow the instructions when encountering relevant tasks without requiring extra operation; if it is not triggered automatically, simply state “please use xx skill.”

Some skills require libraries, such as Python libraries or Node.js packages. For security reasons, the plugin will not silently execute installation commands. Pure instruction-based skills are directly usable; for skills with script dependencies, the AI will automatically install them according to the instructions within the skill. The migration result page will also indicate which skills have dependency declarations, allowing for manual installation if necessary.

Suitable Scenarios and Notes

Suitable for whom: people who have multiple Agents installed on one machine with skills scattered across various directories and who now primarily use DSH. If you only use DSH as a single tool, this plugin is not very useful.

A few notes:

  • Migration is a copy, not a move; the original Agent continues to function normally.
  • If skills cannot be found or do not work after migration: first check if the skill appears in the ~/.dsh/skills/ directory. The plugin automatically fixes non-standard skill names during migration, so you can confirm that the documentation file format is correct; finally, try opening a new session.
  • The plugin runs with the permissions of the current dsh process. It is recommended to review the repository source code and license (MIT) before installation to ensure the source is trustworthy.

Summary

For users of multiple Agents, this plugin turns “reinstalling skills when switching tools” into a simple scan and check, handling details like naming conflicts, duplicates, and rollbacks for you. Repository address: https://github.com/mjylfz/dsh-skill-mover, plugin directory page: https://www.skillhub.cn/plugins/mjylfz/dsh-skill-mover. The directory is a community-maintained independent site and has no official affiliation with DeepSeek or Hypothesis (Xuanfang).