DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Hermes Dsh Collab — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
H

hermes-dsh-collab

Hermes Dsh Collab

将 DeepSeek Harness 接入您的 Hermes 流程:提供 dispatch-spec 模板、模型层级路由、质量门禁和 Git 单一写入者规则,作为可安装的技能包。

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:Cavan-Ou/hermes-dsh-collab#459f8753a5e2dc3e2455182b9c89dda79202e655
README兼容性版本

兼容性与来源证明

Hermes Dsh Collab 以 hermes-dsh-collab 发布,当前版本为 0.3.1。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/9/11

版本

0.3.1stable
2026/9/11

相关插件

正在加载相关插件…

最新版
0.3.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
github
GitHub
★ 6
周下载
0
最近提交
2026/9/11
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 developer-tools 分类下经过校验的插件。

Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Sdk Minimal@deepseek-ai/dsh-sdk-minimal独立的最小 SDK 配置包:JSON-RPC、一个 DeepSeek 适配器、持久化 Shell 和 JSONL 会话Sdk App@deepseek-ai/dsh-sdk-appdsh SDK 配置包:基于 dsh-base 提供 stdio JSON-RPC 服务和进程生命周期管理Subagent Codex@deepseek-ai/dsh-subagent-codex基于官方 app-server 协议的一次性 Codex 子代理提供程序

README

hermes-dsh-collab

Hook DeepSeek Harness into your Hermes pipeline: automated dispatch, execution, and verification — with quality gates that don't trust self-reports.

简体中文版见 README.zh.md

Your AI assistant can work all day. The question is whether you can walk away.

This skill makes it safe to: Hermes writes the dispatch spec, DSH executes it, Hermes verifies it — and you only step in when a quality gate actually fails. Distilled from a real 14-day pipeline (30 commits, 7/7 stages shipped without rework).

Dependencies: DSH 0.1.x (headless profile) + any orchestrator agent (built and tested with Hermes).


Why this exists

Hermes is your personal assistant. DSH is a capable executor. The gap is the operating contract between them: what a good dispatch spec looks like, which model tier to use for which stage, who is allowed to commit, and how verification actually happens.

Most pipelines skip that contract and pay for it in rework. Recent work (COPE) shows planner/executor separation works — but only when the executor's behavior is controlled. This skill encodes those controls, from a pipeline where they were tested:

  • Model-tier routing — Flash (reasoning: max) for routine stages and for looking at images (the main model is natively multimodal — no vision tier, no vision patch), Pro for multi-file refactors and long synthesis (its channel is currently down upstream; the table says so instead of pretending otherwise). When in doubt: try Flash once — rework means escalate.
  • Spec 3 iron rules — Plan first · test first (TDD red→green) · scope declaration. A spec missing any of these is not shippable.
  • Git single-writer — only the orchestrator commits. The executor never touches git, so history stays linear and auditable.
  • Quality gates owned by the orchestrator — full test suite + build + diff-vs-scope audit + real browser walkthrough. Self-reports are not evidence.
  • Write-back via cwd — cd <project> && dsh --profile headless "task" writes straight back. No /tmp mirrors, no patch handoffs.
  • Pitfalls with receipts — every entry is a real incident: patch config replaces whole sections (not deep-merge), read chokes on binaries while read_image needs the model to declare image input, stale backend processes invalidate green tests…

Quick start

# via dsh plugin (bundle — recommended)
dsh plugin --profile headless add github:Cavan-Ou/hermes-dsh-collab

# or copy the skill pack directly (lightweight, any profile)
git clone https://github.com/Cavan-Ou/hermes-dsh-collab
cp -r skills/hermes-dsh-collab "$DSH_HOME/skills/"   # default: ~/.dsh/skills/

Either way, the next DSH session loads it automatically (bundle registers a skill provider; the copy is picked up by the skills scanner).

Verify with three checks:

  1. A new session lists hermes-dsh-collab in its skills
  2. Say "write me a dispatch spec" — the skill triggers on the scenario
  3. Ask "can the executor git commit?" — it says no, and explains why (single-writer rule)

What's inside

skills/hermes-dsh-collab/
├── SKILL.md                      # judgment guide: blocking rules → decision tables → What NOT to do
└── references/                   # loaded on demand; keeps the guide lean
    ├── spec-template.md          # copyable dispatch-spec template (3 iron rules + no-commit clause)
    ├── model-routing.md          # tier table, patch mechanics, and the 2 patch traps
    ├── quality-gates.md          # 4-step gate commands + rework/escalation chain
    └── pitfalls.md               # canonical list of 12 real incidents (symptom → cause → fix)

Shaped like DeepSeek's own repo skills (see .agents/skills in deepseek-ai/deepseek-harness): guidance rather than a checklist · points at sources of truth instead of restating them · a dedicated "What NOT to do" section.

Install forms: both supported — bundle (dsh plugin add, official distribution path, verified on DSH 0.1.0-rc.6) and direct copy to $DSH_HOME/skills/ (lightweight, no build).

Observed results

ResultEvidence
Quality gates catch systemic errors automaticallyIn one long-synthesis run (74 design docs, ~600K tokens), verification surfaced 3 inverted negative-features and a "universe feature" (hairline borders: 78–100% across all five style families) — mistakes that would take hours of manual review and would likely slip through
Routine stages on Flash ship without rework3/3 stages — TDD red→green, all gates green, real-browser walkthrough passed
The skill changes behaviorLive session: after loading, DSH refuses to commit and restates the single-writer rule with reasons

Where you (the human) step in: only on the escalation chain — a quality gate fails, or the same stage retries twice. Everything else runs unattended.

Documentation

  • SKILL.md — the judgment guide itself (read this first)
  • REPORT.md — build report: design decisions, self-test methodology (isolated DSH_HOME verification), open items

Roadmap: bundle packaging (dsh plugin add support) · per-workspace failure isolation · live routing-table refresh from the observations card · English mirror of references

Portability note: the skill's "sources of truth" point at workspace-specific paths (e.g. ~/.dsh/profiles/headless/*.patch.yml). The rules are portable — update the paths to match your workspace.

Contributing

This skill is meant to grow from real use. Hit a pitfall not listed here? Open an issue with the incident (symptom → root cause → fix). PRs welcome in Chinese or English.

License

MIT


Built by running a real pipeline, not by reading docs.