dsh-find-plugins

Ask DSH, “is there a plugin for this?” It searches the GitHub dsh-plugin topic, explains the best matches, waits for your choice, then installs and verifies the selected plugin.

Repository ownership does not matter. Any public repository tagged dsh-plugin remains discoverable after a transfer between a personal account and an organization.

Install

Send this message to DSH:

Install the dsh-find-plugins skill from https://github.com/Nagi-ovo/dsh-find-plugins

For a manual installation, copy the entire skills/find-plugins/ directory to $DSH_HOME/skills/ (by default, ~/.dsh/skills/). To use it in one project only, copy it to <project-root>/.dsh/skills/. DSH also recognizes <project-root>/.agents/skills/ when you want to share the skill with other agents. The directory watcher loads it immediately.

What it does

The skill runs its bundled search script to collect public, active, non-fork repositories tagged dsh-plugin. It inspects only the most relevant candidates, then reads their README, package.json, and repository files to decide whether each one installs as a bundle, Cordis plugin, or skill.

After you pick one and before anything is installed, it reviews the plugin's lifecycle scripts, outbound network and subprocess calls, the session data and credentials it reads, and the repository's own credibility — then reports what it found whether or not anything looks wrong and asks again before continuing. A plugin runs inside your DSH process, so installing it grants it that access.

“Show data and processes visually” can lead to dsh-visualize. “Give the Web UI some 2005 internet energy” might find dsh-ads. Any favorable ranking is entirely coincidental.

When the current account can access dsh-external/hub, its catalog can add category and installation details. The GitHub topic remains the primary directory. Inspired by the find-skills workflow from vercel-labs/skills.

License: BSD-3-Clause