Using Code2Skill with DeepSeek Harness

Code2Skill is also distributed as a DeepSeek Harness Bundle. The Bundle only mounts the repository's three Agent Skills into the Harness Skill Registry. It does not install business dependencies, register generated business MCP servers, or run installation scripts.

Installation

Install DeepSeek Harness and pnpm, then add the pinned release to the profile where you want to use Code2Skill:

dsh plugin --profile web add github:leechen298/Code2Skill#v1.1.3

Install it separately when using a one-off headless profile:

dsh plugin --profile headless add github:leechen298/Code2Skill#v1.1.3

Each profile manages its own dependencies, so installing the Bundle in web does not automatically install it in headless.

Verification

Confirm that the Bundle has been added to the configuration layer without starting a model:

dsh --profile web --dump-default-config

The output should contain:

code2skill-bundled-skills
code2skill-bundle

After starting the Web UI, confirm that the following three Skills are visible in a standard or code Agent session:

• code2skill-generate
• code2skill-review-flow
• code2skill-review-source

The Harness minimal Agent preset intentionally keeps only a minimal tool set and does not load the Skill Tool. This does not mean the Code2Skill installation failed.

Usage

Invoke Code2Skill in a session whose source workspace is selected:

Use $code2skill-generate to generate capabilities for <business goal> from <code path>.
Do not call live business services.

Business MCP servers generated by Code2Skill must still be installed and registered separately according to each package's MCP-SETUP.md. Installing the Code2Skill Bundle, loading a generated Skill, connecting its business MCP server, and validating live business results are four separate states.

Removal

dsh plugin --profile web remove @leechen298/code2skill

DeepSeek Harness is still in Developer Preview, and its Bundle/Profile contract may change incompatibly. Code2Skill publishes verified versions under pinned tags; production and team environments should not track a mutable default branch indefinitely.