dsh-find-plugins

简体中文 | English

Just tell DSH “is there a plugin that can…”, and it will search all of GitHub’s dsh-plugin topic for candidates, explain the differences, and only install and verify after you’ve picked one.

Repo owner — personal or org — doesn't matter. Public repos with the dsh-plugin topic stay discoverable even after transfer.

Installation

Send this to DSH:

请从 https://github.com/Nagi-ovo/dsh-find-plugins 安装 dsh-find-plugins skill

For manual installation, copy the entire skills/find-plugins/ directory into $DSH_HOME/skills/ (default is ~/.dsh/skills/); to use it only in the current project, copy it to <项目根>/.dsh/skills/. To share with other agents, you can also place it in <项目根>/.agents/skills/. The directory watcher activates it immediately.

What It Does

The skill first runs a bundled script to fetch all public, non-archived, non-fork dsh-plugin repos. It only examines the few best-matching candidates and determines from the README, package.json, and repo files whether the installation should be done as a bundle, a Cordis plugin, or a skill.

After you pick one, it first checks the plugin's lifecycle scripts, outbound network and subprocess usage, session data and credentials it reads, and the repo's trustworthiness, then reports once regardless of outcome before asking if you want to continue. The plugin runs inside your DSH process — installing it is granting it permission.

For example, “I want to visualize my data and workflows” might find dsh-visualize; “I want to give my web UI that 2005-era internet vibe” might find dsh-ads. Any particular match here is pure coincidence.

dsh-external/hub can supplement categorization and installation info when accessible from the current account, but the GitHub topic remains the primary directory. Inspired by find-skills from vercel-labs/skills.

License: BSD-3-Clause