dsh-skills-nexus
English | 中文
Skill lifecycle manager for DeepSeek Harness (DSH). Register any git-hosted SKILL.md repo, link external skill directories from other agent clients, pack skills for cross-machine transfer, or manage everything from the DSH web panel — all through one CLI.
dsh-skills-nexus is a community-maintained DeepSeek Harness plugin, not an official DeepSeek AI product.
3-Minute Quick Start
Pick one skill repo and get it into DSH:
# 1. Install
npm install -g dsh-skills-nexus
# 2. Add a skill repo
dsh-skills-nexus add github:owner/repo
# 3. Done — skills are picked up by the DSH filesystem provider automatically
That's it. For the three installation paths (npm registry, GitHub direct, or DSH plugin layer), npm 12 EALLOWGIT troubleshooting, and prerequisites — see Installation Guide.
What You Can Do
| Want to… | Run… |
|---|---|
| Add a skill from any git host | dsh-skills-nexus add github:owner/repo |
| Pin to a branch / tag / commit | dsh-skills-nexus add github:owner/repo#dev |
| Install one subdirectory from a collection repo | dsh-skills-nexus add github:owner/repo --subdir skills/foo |
| Link skills already installed in Trae / Qoder / CodeBuddy… | dsh-skills-nexus link trae-cn (or trae, qoder, codebuddy, workbuddy, kimi-code, cursor, claude-code, …) |
| Manage project links and toggle vendored skill directories | dsh-skills-nexus list --project · dsh-skills-nexus disable --project --files my-skill |
| List everything with status | dsh-skills-nexus list |
| Batch enable/disable by group | dsh-skills-nexus enable --group trae-cn |
| Move all skills to another machine | dsh-skills-nexus export --all -o migrate.zip → dsh-skills-nexus import migrate.zip |
| Health check with exit codes | dsh-skills-nexus doctor |
| Watch it all in the web panel | Register as DSH plugin → Settings → Skills Nexus |
Web Panel
When registered as a DSH plugin (dsh plugin add), the Settings page gets a Skills Nexus section with a full UI: browse entry cards, toggle groups, add skills by URL, import packages, run health checks, watch long operations stream progress. The Project skills tab covers manually entered folders (links) and host-registered workspaces (real directories), with reversible enable/disable toggles.
See the full panel description for every action the UI supports.
How It Works
CLI and Web Panel drive the same manifest, the same clones, and the same cross-process file locks. Mix both freely — an operation one side is working on shows as busy / locked on the other.
link trae-cn / link trae / link qoder etc. creates external entries that symlink to directories you already own (~/.trae-cn/skills/, ~/.trae/skills/, …). Nexus never clones, updates, or deletes those directories — remove only deletes the link and manifest entry.
Each client is an independent namespace. One skill installed in two clients becomes two entries, never shadowing each other. The default root can be overridden with --source-dir.
This or dsh plugin add?
| Installs… | Requires dsh.bundle.patch? |
Command |
|---|---|---|
| A pure SKILL.md content repo | No | dsh-skills-nexus add github:owner/any-skill |
| A real DSH plugin with Cordis wrapper | Yes | dsh plugin add github:owner/dsh-skills-nexus |
If your repo has both, your choice — nexus for managing the content, dsh plugin for managing the code wrapper. Full decision guide.
Roadmap & Known Limitations
- v0.10.x: Project-scope skills are experimental — CLI interaction may shift. Global skills are stable.
- v0.11: Opt-in anonymous usage statistics, so we know how many people actually use this.
- No first-run telemetry: nothing is sent by default — the project is silent unless you opt in.
- Skill content repos only: this is not a replacement for
dsh plugin addof real Cordis plugins.
Issues welcome — open one blank or pick a template.
Documentation Index
The full reference lives in README_FULL.md — every flag, every edge case, every gotcha. Here's where to jump:
| I want to… | Read… |
|---|---|
| Install it | Installation Guide |
Understand every dsh-skills-nexus subcommand |
Usage Reference |
All supported link sources (Trae / Qoder / CodeBuddy / …) |
Supported external sources |
| Use skills scoped to a project folder | Project skills |
| Move skills between machines | Export / Import / Adopt |
Use --json for scripting |
Options and --json |
| What the Web Panel can do | Web Panel |
| Uninstall completely | Uninstall |
| Test locally without GitHub or npm | Local testing steps |
| Architecture, source discovery, sparse checkout | Architecture |
| Build a tool on top of nexus | Building on nexus |
Nexus vs dsh plugin — which one to pick |
nexus vs plugin |
| Subdir design trade-offs | Subdir design |
Community verification walkthroughs: link sources · project skills · version lock · import/export · doctor · rollback · group operations · completions · purge · update pipeline · switch-version · add/update JSON
Uninstall
Three independent things to clean up — each uses a different command. See Uninstall for the annotated procedure.
dsh-skills-nexus remove '*' --yes # 1. Remove all skills (data)
dsh plugin --profile web remove dsh-skills-nexus # 2. Optional plugin layer
npm uninstall -g dsh-skills-nexus # 3. Global CLI
License
MIT.
No comments yet. Be the first to write one.