dsh-community-plugins
DeepSeek Harness (dsh) plugin: registers a global skill that teaches agents how to discover, evaluate and install community plugins from the GitHub dsh-plugin topic, dshmarket and npm. | DSH 社区插件生态指南 skill:让 agent 学会发现、评估、安装社区插件。
- Stars
- 4
- Language
- JavaScript
- Created
- Aug 15, 2026
- Updated
- Aug 16, 2026
Introduction
dsh-community-plugins
A DeepSeek Harness (dsh) plugin that registers a global skill for discovering, evaluating and installing community plugins — from the GitHub
dsh-plugintopic, the dshmarket GUI, and npm.
Looking for a DeepSeek Harness plugin to install? This bundle adds the dsh-community-plugins skill to every agent session: agents learn which marketplace tools are already installed (market_search, dshmarket), how to search the dsh-plugin ecosystem, how to vet a plugin before installing it, and how to install via dsh plugin (npm, GitHub, tarball, or link: development mode).
Why this plugin
DeepSeek Harness plugins provide capabilities through two complementary mechanisms: Tools and Skills.
Tool (e.g. market_search) | Skill (registered by this plugin) | |
|---|---|---|
| Nature | Capability channel: callable functions | Context knowledge: when, why, and how to call |
| Installed by | dsh-plugin-marketplace etc. | This plugin |
| Effect alone | Tool exists, but the agent does not recognize it | No marketplace interface to call |
Installing a marketplace tool alone is not enough. An LLM agent's behavior is driven by context knowledge:
web_searchhas an intuitive description and is any model's default generic approach;market_searchis a DSH-specific tool. Without this skill, the agent does not know it exists, does not associate it with installing plugins, and does not understand the local profile layout, the bundle mechanism, the vetting workflow, or the restart requirement.
Without this plugin, agents fall back to generic web search. With it, every new session's agent automatically knows which marketplaces and tools are installed, which structured channels to query first, how to vet sources, how to install through the official mechanism, and how to verify the result. In practice, on the same environment, agents relied on web search before the skill was active, and invoked market_search directly with accurate install commands on their first response afterwards.
Features
- Registers a global skill:
dsh-community-pluginsappears in every session's<available_skills>catalog - Teaches the agent to verify what is actually installed on this machine (read the profile manifest; never assume or promote uninstalled plugins)
- Provides neutral discovery channels: installed-market tools, directory indexes (
Oh-My-DSHdata/plugins.json,awesome-dsh-plugin), GitHubdsh-plugintopic, npm - Documents the official install methods plus speed-ups:
dsh plugincommand, npm-first, batch installs, hot-mount vs restart by plugin form - Documents the pnpm supply-chain policy (
minimumReleaseAge) and its workarounds - States the constraints: no modification of official shipped presets, restart rules, build-authorization boundaries
Install
Prerequisite: dsh CLI (or invoke apps/cli/lib/bin.js from the dsh install root). Choose one of the following:
# GitHub direct install (pure JS, no build scripts, no build authorization)
dsh plugin --profile web add github:HubaKing/dsh-community-plugins
# Gitee mirror (faster in mainland China)
dsh plugin --profile web add https://gitee.com/HubaKing/dsh-community-plugins.git
# tarball (works offline)
curl -LO https://github.com/HubaKing/dsh-community-plugins/releases/download/v0.1.2/dsh-community-plugins-0.1.2.tgz
dsh plugin --profile web add ./dsh-community-plugins-0.1.2.tgz
# source + link (development mode, edits take effect immediately)
git clone https://github.com/HubaKing/dsh-community-plugins.git "${DSH_HOME:-~/.dsh}/plugins/dsh-community-plugins"
dsh plugin --profile web add link:${DSH_HOME:-~/.dsh}/plugins/dsh-community-plugins
Restart dsh after installing (bundle layers are composed at startup). Installation succeeds when dsh-community-plugins appears in <available_skills> of a new session.
When
dshis not on PATH, usenode <dsh install root>/apps/cli/lib/bin.js plugin --profile web add <spec>.
How it works
| File | Responsibility |
|---|---|
index.js | Plugin entry: registers the skills/ directory into the global ctx.skills registry |
cordis.patch.yml | Bundle patch layer: the - insert: row mounts the plugin at profile startup |
skills/dsh-community-plugins/SKILL.md | The skill body the agent reads |
package.json | Declares the dsh.bundle.patch manifest |
Key points:
- Pure JavaScript, no build scripts: single dependency
yaml; GitHub direct install needs nopreparescript orallowBuildsauthorization (the build gate for TypeScript plugins, per the official docs) - Hot update:
index.jsre-reads from disk on every discovery; editingSKILL.mdrequires no restart or reinstall - Official plugin shape: function form
export const name+export function apply(ctx)+dsh.bundlemanifest
Modifying the skill content
Edit skills/dsh-community-plugins/SKILL.md; changes take effect on save, then git push to share with other users.
Layout
dsh-community-plugins/
├── index.js # Plugin entry (skill registration)
├── cordis.patch.yml # Bundle patch layer
├── package.json # dsh.bundle manifest
├── README.md # English
├── docs/
│ └── lang/
│ └── README_zh.md # 中文
└── skills/
└── dsh-community-plugins/
└── SKILL.md # The guide read by agents
Related docs
- DeepSeek Harness official repository
- Official docs (English)
- Official docs (简体中文)
- Quickstart (Web UI)
- First plugin — plugin shape,
apply/inject, lifecycle - Packaging and installing plugins — bundle manifest, profile install, build authorization
- Plugin configuration — Config/Schema conventions
- Plugins and lifecycle — Fiber state machine and automatic cleanup
- Event system — event modes and naming conventions
- Run from source (root README) — build and launch from source
- Source execution (CLI reference) — build and launcher behavior
- GitHub
dsh-plugintopic — community plugin aggregation
License
MIT