dsh-skills-nexus

dsh plugin --profile web add dsh-skills-nexus

dsh-skills-nexus






English | [中文](README_CN.md)

⭐ If this project helps you, welcome to Star for support!

DSH skill lifecycle manager — from git repo cloning, external directory linking, package import/export, to group management, health checks, and cross-machine transport. Keeps up with the latest DSH version, compatible with the official filesystem provider.

dsh-skills-nexus is a community-maintained DeepSeek Harness (DSH) plugin, not an official DeepSeek AI product.

Capabilities

Direction · What you get · Entry point

Git-backed installs · Any SKILL.md repo from any git host, pinned to a branch, tag or commit; collection repos install one subdirectory with partial clone + sparse checkout; wrapper detection runs before registering · add

Version management · Refresh branch-tracked clones, preview remote changes without a checkout, move a clone to another ref, undo the last version change · update / diff / switch-version / rollback

External references · Register skills that already live in another agent's directory — no clone, no copy, no writes there · [link](#supported-external-sources-link) / remove --group

Cross-machine transport · Package entries with their provenance, rebuild them elsewhere (optionally at the exact recorded commit), give a frozen entry its git source back · export / import / adopt

Grouping and toggles · Group by source or a custom L1 name; enable or disable one entry or a whole group prefix · enable / disable / --group

Health and cleanup · Read-only checkup of the manifest, links and clones, with an optional remote update check; purge accumulated artifacts · doctor / purge

Automation · Version-1 JSON reports on stdout, stable exit codes, name-only listing · --json / list --names

Web panel · Browse entry cards, preview and link a local source, run the health check, adopt a source-less entry, search and filter · [panel](#web-panel-optional-plugin-side)

Shell completion · Generated completion script for bash, zsh, fish or PowerShell · completions

Why

dsh plugin --profile <name> add "github:owner/repo" forwards to pnpm, and

only packages with dsh.bundle.patch are activated as profile layers. A

content repo with just SKILL.md + references/ + scripts/ has no Cordis

wrapper, so this path doesn't work. dsh-skills-nexus fills the gap:

command · installs · requires dsh.bundle.patch?

dsh plugin add github:owner/dsh-skills-nexus · nexus itself (once) · yes

dsh-skills-nexus add github:owner/any-skill · pure SKILL.md content repo · no

Not sure which command fits your repo? Read

[nexus vs dsh plugin — when to use which](docs/nexus-vs-plugin.md).

Short version: repo has SKILL.md → nexus; repo is a pure plugin

(cordis.patch.yml / dsh.bundle.patch, no SKILL.md) → dsh plugin;

has both → your choice (nexus = content, plugin = code).

Install nexus

Optional: register as a DSH plugin

To register nexus in the DSH web profile, run the following (replace web

if you use a different profile):

dsh plugin --profile web add "github:xiaxi626/dsh-skills-nexus"

In a web session this adds the [Skills Nexus settings panel](#web-panel-optional-plugin-side)

along with its /skills-nexus/* HTTP routes; in non-web hosts the layer stays

dormant. It still **does not provide a global CLI command and is not a

prerequisite for the CLI install below** — skip it if you only need the CLI

to manage skills.

Install the CLI globally

Install the CLI globally — this is what puts the dsh-skills-nexus command

on your shell PATH (provided npm's global command directory is already on PATH):

npm 12: after confirming that you trust the repository and its dependencies,

explicitly allow Git dependencies for this installation:

npm install -g --allow-git=all github:xiaxi626/dsh-skills-nexus

Older npm versions (where Git dependencies are not blocked): the original

command works. Choose one of these two commands based on your version and policy:

npm install -g github:xiaxi626/dsh-skills-nexus

Troubleshooting EALLOWGIT

If the original command reports:

npm error code EALLOWGIT
npm error Fetching packages of type "git" have been disabled

npm's Git dependency policy blocked the installation before download; this

is not a missing Nexus installation or a repository build failure. Starting

with npm 12, allow-git defaults to none instead of allowing Git dependencies.

A github:owner/repo spec is a Git dependency and therefore requires explicit

permission. Check your version with npm --version; on npm 12, check the

active policy with npm config get allow-git.

The stricter default reduces supply-chain risk: Git dependencies access remote

repositories and may introduce configuration the project does not control.

**This error does not mean npm detected malicious code in Nexus, no

…(truncated)