DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to list your DSH plugin in the community catalog with DSH Plugin Shop

Add the right keyword and metadata to your npm package so the daily build discovers and lists it.

Who it is forA plugin author who has built a DeepSeek Harness plugin and wants other dsh users to find it.

The problemAuthors need to know how discovery works and what makes a plugin fail the screening checks before it appears in the shop.

The outcomeYour plugin appears in the catalog after the daily build, or the build report tells you the specific reason it was excluded.

What you need first

  • Node.js installed, with npm available
  • DeepSeek Harness (dsh) installed globally with npm install -g @deepseek-ai/dsh pnpm, or run through npx
  • A dsh profile name to use (the README uses web as the example)
  • Willingness to trust installed plugins, since they have full access to ctx including the filesystem and shell

Steps

  1. Add dsh-plugin to the keywords in package.json, and make sure package.json includes a dsh.bundle field.
  2. Add a license and a source repository, since the build cannot review a plugin without them.
  3. Publish the package to npm, for example with npm publish. (inferred, check the README)
  4. Wait for the next daily build, then check the rejection report if your plugin is missing.

Prompt for your agent

Check the package.json of the plugin at <plugin-path> for the dsh-plugin keyword, a dsh.bundle field, a license, and a source repository, as listed in the LivXue/dsh-plugin-shop README. Report any missing item and whether an optional dsh.catalog section is present.

Caveat. The catalog is rebuilt daily, and eligible plugins are listed the next morning, so a new release will not appear immediately.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page