Submit a plugin
Submitting a plugin only proposes it for listing — it is reviewed by a human and published only after the dsh field + README checks pass. Nothing goes live automatically.
How submission works.Fill in the form → your card preview renders live → on submit, a ready-to-paste GitHub Issue body is produced → a maintainer verifies the dsh field / README → on approval the plugin is added to plugins.json and re-generated.
Ready — nearly there
Copy the Issue body below and open it in any accepting repository, or use the direct Issue link once the maintainer enables SUBMISSION_URL. Submissions are queued for human review — not auto-listed.
Paste the copied body into a new GitHub Issue on the plugin's own repository (or the directory's issue tracker) and a maintainer will review it.
SubmitSubmission channel not configured yet. The site owner needs to set SUBMISSION_URL to enable the one-click Issue link. Until then, the submit button copies the Issue body and you paste it into any GitHub repository that accepts plugin submissions.
Review before listing
- Human verifies this is a real DSH plugin by checking package.json dsh field (dsh.bundle.patch or dsh.client).
- README (or package metadata) shows real plugin evidence, not just a topic tag.
- Install / usage instructions are documented and executable.
- License and obvious credential / destructive-op risks are recorded before listing.
- Approved entries are written to plugins.json and the static site is re-generated — never auto-published.
Remember: This is a static site with no backend. Submission ≠ listing. A human merges approved plugins. Never share API keys or secrets in the form.