Preface¶

In DSH’s plugin ecosystem, community plugins typically come from more than one source: installed marketplace tools, directory indexes, GitHub topics, npm, and more. For an agent, the mere existence of a marketplace tool doesn’t mean it will prioritize using that tool, nor does it mean the agent knows how to verify what’s installed locally, how to evaluate plugin sources, or how to execute installation according to DSH’s installation mechanism and verify results.

What dsh-community-plugins addresses is precisely this contextual gap: it registers a global skill that writes the rules for discovering, evaluating, and installing community plugins into every session’s available skills directory. This ensures that when the agent provides plugin installation recommendations, it first consults the local profile manifest and installed tools rather than assuming or promoting uninstalled plugins.

What This Is¶

dsh-community-plugins is maintained by HubaKing and licensed under MIT. It is not a standalone plugin store, but rather a DSH plugin that registers the community plugin ecosystem guide as a skill.

After installation, dsh-community-plugins appears in the <available_skills> directory of every session. Once the agent reads this skill, it becomes aware of built-in marketplace capabilities such as dshmarket / dsh-plugin-marketplace and learns how to discover, evaluate, and install community plugins.

Core Features¶

The capabilities listed below are all derived from verified sources:

Registers a global skill: dsh-community-plugins appears in the <available_skills> directory of every session.
Teaches the agent to verify what is actually installed locally: read the profile manifest, and do not assume or promote uninstalled plugins.
Provides neutral discovery channels: installed marketplace tools, directory indexes (Oh-My-DSH data/plugins.json, awesome-dsh-plugin), GitHub dsh-plugin topic, npm.
Documents official installation methods and acceleration approaches: dsh plugin command, npm-first, batch installation, and choosing hot-mount or restart based on plugin type.
Documents pnpm supply chain policy (minimumReleaseAge) and how to work around it.
Declares constraints: does not modify official built-in presets, respects restart rules, and acknowledges build authorization boundaries.

Installation and Enablement¶

Prerequisites¶

A working dsh CLI is required. If dsh is not in PATH, you can use the CLI entry point located in the dsh installation root directory.

Direct Installation via GitHub¶

First add the plugin directly via GitHub:

dsh plugin --profile web add github:HubaKing/dsh-community-plugins

This approach suits environments with direct access to GitHub. The source confirms it is pure JavaScript with no build scripts; GitHub direct install requires no prepare script or allowBuilds authorization.

Gitee Mirror¶

If using a Gitee mirror repository:

dsh plugin --profile web add https://gitee.com/HubaKing/dsh-community-plugins.git

Tarball¶

When using a release tarball, download the file first, then add it locally:

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

Development Mode¶

In development mode, first clone to the plugins directory, then add using the link: approach:

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 and Verification After Installation¶

After installation, restart dsh. The documentation states that bundle layers are composed at startup, so a restart is required after installation.

Verification is done by checking a new session: when dsh-community-plugins appears in <available_skills>, the installation is successful.

If dsh is not in PATH, use the CLI entry point in the dsh installation root instead:

node <dsh install root>/apps/cli/lib/bin.js plugin --profile web add <spec>

Typical Usage¶

Confirm the skill is available in a new session.

Look for dsh-community-plugins in <available_skills>. If present, the session can read the guide.

Have the agent find community plugins.

Following the skill’s guidance, the agent should first check installed marketplace tools, directory indexes, the GitHub dsh-plugin topic, npm, and other channels, while cross-referencing the profile manifest to confirm what is actually installed locally.

Choose the installation path based on plugin type.

Documented installation methods include the dsh plugin command, npm-first, batch installation, and choosing hot-mount or restart based on plugin type.

Modify skill content.

Edit:

skills/dsh-community-plugins/SKILL.md

Changes take effect after saving. To share with other users, run:

git push

Applicable Scenarios and Notes¶

Suitable for the following scenarios:

Using DSH and wanting stable community plugin discovery within agent sessions.
Wanting the agent to verify the local profile manifest before providing installation recommendations, rather than assuming uninstalled plugins already exist.
Needing to unify discovery channels such as marketplace tools, directory indexes, GitHub topics, and npm into the agent’s context.
Needing to document installation rules including npm-first, batch installation, hot-mount or restart, pnpm minimumReleaseAge and its workarounds.

Points to note:

Plugins run with the permissions of the current dsh process. Review the source code and license before installation. dsh-community-plugins is licensed under MIT.
The documentation lists multiple installation methods, and the verified sources do not uniquely identify a single official installation command. In practice, choose any one of them and use the appearance of dsh-community-plugins in <available_skills> in a new session as the verification criterion.
Do not treat the community plugin directory as an official app store. References such as dshmarket / dsh-plugin-marketplace, Oh-My-DSH data/plugins.json, awesome-dsh-plugin, the GitHub dsh-plugin topic, and npm should be treated as discovery channels.
This plugin declares that it does not modify official built-in presets, respects restart rules, and documents build authorization boundaries. These constraints should be followed when in use.

Links and Closing¶

The value of dsh-community-plugins lies in embedding “discover plugins, evaluate plugins, install plugins, verify plugins” into the agent session context, reducing the likelihood of the agent falling back to generic searches due to a lack of DSH context.

dsh-community-plugins: A Guide to Discovering and Installing Community Plugins for DSH Sessions