dsh-plugin-capabilities
Skills & MCP section in Settings: browse, create, edit and delete skills with live directory watching, toggle loading of any on-disk skill through frontmatter policy keys, register local folders or GitHub repos as extra skill scan roots, edit the MCP server rows in the profile patch, import MCP config from Claude Code or Codex, and install from a curated market of skill repos and MCP servers.
On this page
Review info: an independent structural review record is available for install structure, README, lifecycle scripts and runtime-artifact evidence. This is not a full code security audit.
Community signals
Category
Development & Runtime
GitHub stars
15
npm downloads
2,093
Discovery registry added
2026-08-24
Review information
Scanner status
auto-resolved
Review mode
automatic
Last checked
2026-09-21T12:51:21.444Z
Build approval required
No
Lifecycle scripts
prepare
Runtime artifacts committed
No
Documented profiles
web
exact-npm-tarball-verified-for-automatic-install
Why this site does not provide the install command
A third-party DSH plugin is executable local code. Even when structural review evidence exists, registry data, stars and metadata cannot prove the code is non-malicious. Read the current author repository and perform your own review in a disposable environment.
Install and usage source
This site links to the author's source, npm page and community registry instead of redistributing commands. A plugin may add Web UI, Settings, agent tools or background capabilities; follow the author README for the actual entry point.
Minimum checks before install
- Confirm package.json, the bundle patch and README belong to the same author repository.
- Inspect preinstall/install/postinstall/prepare, child_process, shell, filesystem, network calls and credential access.
- First install into a disposable profile/workspace without production credentials or an important repository.
- If pnpm asks for allowBuilds/build approval, treat it as permission to execute third-party code during installation; do not approve mechanically.
- For reproducibility, pin an exact npm version or Git commit yourself instead of depending on main/latest.
“Third-party” only means the plugin is not an official DeepSeek plugin. Structural checks improve transparency but cannot prove business logic is non-malicious or fully audit dependencies, future updates or runtime behavior.