Contributing to Awesome DSH Plugins

August 26, 2026 · View on GitHub

Thanks for considering a contribution. We are strict about verification but fast about merging (target under 7 days to a first response on every PR).

Entries from ZeroPointRepo

Some entries in this list are built by ZeroPointRepo: transcriptapi and zillapi, both under Live data APIs. They are held to the same rules as every other entry, and to a higher bar on one point:

  • Same entry format as everyone else. No bold, no emoji, no "featured" styling.
  • At most one per category.
  • A higher acceptance bar: no verified install path, no real docs, it does not go in. StayingAPI is not listed for exactly that reason, its key could not be verified live at the time of writing.
  • A competing entry is never rejected or downranked to protect one of ours.

The top slot rotates on merit, roughly one plugin in six from a strong batch. It is not a permanent house slot. A plugin earns it by being an unusually good answer to a real job, having a verified install command, and being active. Maintainers pick it; there is no separate application.

Starter combos

A combo is a small set of plugins that answers one job together. It is not a "best of" shortlist and not a place to get a second entry in.

  • Every member is already a listed entry, using the same install command, character for character. CI compares the combo block against the catalog and fails the run if the two drift apart.
  • Two or three members. If a fourth is only loosely related, it does not belong.
  • Each member does something the others do not. A combo whose members overlap is padding.

Suggest one in an issue: the job it solves, and why those specific plugins.

Adding a plugin entry

Open a PR that adds one entry, in the right category, in this exact format:

- **What it does for the reader, as a short action phrase** with
  [name](repo-url) by [author](author-url). A factual one-line description. N★, LICENSE.

  <details>
  <summary>Install</summary>

  ```sh
  dsh plugin --profile <profile> add <package>
```

One entry, one lead phrase, one description, one collapsed install block. No tags, no extra sub-bullets, nothing else in the visible line.

Acceptance bar (we merge if all of these are true)

  1. It installs. A real dsh plugin add (or documented DSH-native equivalent, like the --patch config files this list uses for remote MCP servers) that you copied out of the project's own README or docs, not one you guessed. We will check it against that project's own documentation before merging, same as every existing entry.
  2. The GitHub repo resolves, is not archived, and is not a same-named coincidence with an unrelated project.
  3. It is not already listed.
  4. The category is right. If it spans two, pick the primary use case; a maintainer will move it rather than bounce the PR over this alone.

We reject only for: no working install command, dead or archived link, no real substance, pure spam, or exact duplicate. We always reply, even to a rejection, and we will say exactly what would get a resubmission in.

An honestly empty category beats a padded one. If your plugin doesn't clear the bar yet, tell us in the PR or an issue and we will say plainly what is missing, instead of listing a command that doesn't work.

Style

  • One entry per line plus its command block, no sub-bullets beyond that.
  • No affiliate links, no UTM parameters, no tracking redirects.
  • Keep descriptions under about 120 characters where you can.
  • No em dashes. Use a period, comma, or colon instead.