DSH 插件社区

DeepSeek Harness（DSH）插件的社区——讨论、求助、展示、找方案。 市场负责「有什么插件」，这里负责「这个插件怎么样、怎么用、出问题找谁」。

本仓库不是一个插件市场。 它不托管插件、不提供安装器，只提供一个人和插件作者能对话的地方。

---

这里能做什么

我想…	去哪
看看别人做了什么插件	🧩 插件展示
用某个插件卡住了	🙋 求助
想要一个还不存在的插件	💡 想法与需求
汇报插件的 bug	优先去插件自己的仓库开 Issue；找不到仓库、Issue 关着、或提了没人管 → 本仓库 Issues
查某个插件已知的问题	🐞 已知问题
随便聊聊	🗣️ 闲聊

为什么 bug 走 Issues 而不是 Discussions：Issues 能关、能指派、能被作者订阅通知，是「待办」；Discussions 是「话题」，发完不一定要有人处理。能用 Issue 追踪的事不要开讨论帖。

---

怎么参与

浏览不需要登录。 GitHub 的公开 Discussions 对所有人可见——直接看就行。

发言需要一个 GitHub 账号。 这是唯一的门槛，也是本项目的刻意选择：把身份、反滥用、通知全都交给 GitHub，社区自己不做账号体系。

• 第一次来 → 先读 CONTRIBUTING.md
• 想推荐自己的插件 → 读 投稿指南
• 想汇报安全问题 → 读 SECURITY.md（不要开公开 Issue）

---

讨论分类

分类	用途	能标「答案」
📣 公告	索引更新、社区规则变更	—
🧩 插件展示	作者自荐，或推荐你用过的插件	否
🙋 求助	使用中遇到问题	是
💡 想法与需求	「我想要一个能做 X 的插件」	否
🐞 已知问题	bug 的汇总与绕行方案	否
🗣️ 闲聊	兜底	否

求助帖能标答案这件事很重要：一个被解决了的问题会留在搜索结果里，下一个人搜到就能直接用。解决了就请回来把答案标上。

---

行为准则

参与即表示同意 CODE_OF_CONDUCT.md。一句话版本：对插件苛刻，对人客气。

---

与市场的关系

DSH 的插件市场已经不止一个，而且都做得不错。社区不是第 N+1 个市场，也不会去重复它们的索引工作。

社区做的是市场做不了的事：

• 对话——市场能告诉你插件存在，不能告诉你它在你这种情况下会不会崩
• 沉淀——一个被回答过的问题，比一次性的 star 数有用得多
• 作者与用户的直接接触——插件作者能在这里看到真实反馈

如果你在维护一个市场或索引目录，欢迎来闲聊区打个招呼——我们更愿意合作而不是竞争。

---

English summary

DSH Plugin Community — a place for discussing DeepSeek Harness (DSH) plugins: showcasing them, getting help, asking for new ones, and recording known issues.

This repository is not a plugin marketplace. It hosts no plugins and ships no installer. It exists so that people and plugin authors have somewhere to talk.

Where to go

I want to…	Go to
See what plugins other people built	🧩 Plugin showcase
Get unstuck on a plugin	🙋 Ask for help
Ask for a plugin that does not exist yet	💡 Ideas & requests
Report a plugin bug	Open an issue in the plugin's own repository first. No repo, issues closed, or nobody responding → this repository's Issues
Look up a known problem	🐞 Known issues
Just chat	🗣️ General

Why bugs go to Issues and not Discussions: issues can be closed, assigned, and subscribed to by the author — they are a to-do list. Discussions are topics; nobody is obliged to act on one. Anything you want tracked should be an issue, not a discussion thread.

Taking part

Browsing needs no account. Public GitHub Discussions are visible to everyone — just read.

Posting needs a GitHub account. That is the only barrier, and it is deliberate: identity, abuse prevention, and notifications are all delegated to GitHub. The community runs no account system of its own.

• First time here → read CONTRIBUTING.md
• Want to submit your own plugin → read the submission guide
• Reporting a security problem → read SECURITY.md (never open a public issue for it)

Discussion categories

Category	Purpose	Can accept an "answer"
📣 Announcements	Index updates, rule changes	—
🧩 Plugin showcase	Authors self-promoting, or recommending a plugin you use	no
🙋 Ask for help	Trouble using something	yes
💡 Ideas & requests	"I wish a plugin could do X"	no
🐞 Known issues	Bug round-ups and workarounds	no
🗣️ General	Everything else	no

That help threads can accept an answer matters: a solved question stays in search results, and the next person finds it immediately. Once yours is solved, come back and mark the answer.

Forms are bilingual

Every issue form and discussion form in this repository carries Chinese and English in the same field (中文 / English), so you can fill them in either language. GitHub has no per-language form support, and shipping duplicate English forms would double the "new issue" list and let the two versions drift apart — so both languages live in one form.

Code of conduct

Participating means agreeing to CODE_OF_CONDUCT.md. The one-line version: be exacting about plugins, be kind to people.

Relationship to marketplaces

DSH already has more than one plugin marketplace, and they are good. This community is not marketplace number N+1 and will not duplicate their indexing work. What it does is what a marketplace cannot:

• Conversation — a marketplace tells you a plugin exists; it cannot tell you whether it will break in your situation
• Accumulation — a question that got answered is worth far more than a one-off star count
• Direct contact between authors and users — plugin authors can see real feedback here

If you maintain a marketplace or index, come say hello in General — we would rather cooperate than compete.

Licence

The repository itself (README, contribution guide, issue and discussion forms) is MIT, © 2026 moyuqing-man. It contains no executable code — see SECURITY.md — and every plugin discussed here carries its own author's licence.

---

Discussions in this repository carry the community content; each plugin's code and licence are its own author's responsibility.