一個 Apache-2.0 的 Cordis 插件，讓 DeepSeek Harness（dsh）運作者透過 Exposed / Progressive / Blocked 三檔為 MCP 工具與 Skill 分級，借助 `meta_search` / `meta_invoke` 控制上下文佔用。
DSH 整合
原生執行環境
作者聲明
安全稽核
未稽核
最後核實
2026-08-30
授權條款
Apache-2.0
01它能幫你完成什麼？
Manage the exposure level (context footprint) and execution mode of MCP tools & skills in DeepSeek Harness through Exposed / Progressive / Blocked tiers.
A unified capability catalog (`ctx.meta`) plus two meta-tools — `meta_search` (discover Tool/Skill) and `meta_invoke` (execute tool / load skill) — so the model pulls capabilities on demand instead of loading everything into one request.
DeepSeek Harness (dsh) operators running many MCP tools/skills who want to cap token and context usage per request without forking upstream.
Review and tune the three-tier capability policy from the DeepSeek Harness settings UI.
A 'Capability Menu' tab (Settings / General) listing MCP tools (grouped by server, collapsible) and Skills with tri-state dots and per-tier counts; switch a capability's tier with one click and changes apply live, no restart.
Operators and admins who prefer a GUI over editing the YAML policy file by hand.
02如何將外掛接入 DeepSeek Harness？
先決條件
- Node.js installed
- dsh CLI installed (`dsh plugin` forwards to pnpm internally)
安裝步驟
- 01
$ dsh plugin --profile web add @daweifu/capability-menu
- 02
$ dsh plugin --profile web add @daweifu/capability-menu-web
驗證整合成功
- Run `dsh --profile web --dump-config | grep -E 'capability-menu'` — the README says you should see this package's own patch layer (capability-menu-registry / -search / -invoke / -policy).
復原
- dsh plugin --profile web remove @daweifu/capability-menu
- dsh plugin --profile web remove @daweifu/capability-menu-web
03DSH 整合程度與能力邊界
Installed as a Cordis plugin via the dsh CLI (`dsh plugin --profile web add @daweifu/capability-menu`) and runs inside the DeepSeek Harness runtime; exposes `ctx.meta`, `meta_search` and `meta_invoke` without forking upstream.
Unified capability catalog (ctx.meta)
MCP tools and skills registered in the DeepSeek Harness runtime→a single capability directory (`ctx.meta`) indexed by `ctx.tools` / `ctx.skills`
does not modify upstream source — combines into the same runtime via the Cordis plugin mechanismTwo meta-tools: meta_search & meta_invoke
a capability query or invocation request from the model→`meta_search` lists/details capabilities (Tool/Skill); `meta_invoke` executes tools through the full `ctx.tools` pipeline or loads skill bodies
`meta_invoke` performs real tool execution; blocked tools are rejectedprogressive tools/skills stay out of context until invokedExposed / Progressive / Blocked three-tier policy
a policy config of tools/skills exposed / progressive / blocked rules→controls what the model sees per request (full schema vs catalog-only vs hidden) and how each capability executes
progressive tools/skills are removed from the model's context payload until invokedblocked tools are rejected by meta_invoke
04適合誰？何時不該用？
適合
- DeepSeek Harness (dsh) operators running many MCP tools/skills who want to cap token and context usage per request without forking upstream.
- Operators and admins who prefer a GUI over editing the YAML policy file by hand.
不適合
- Native (non-`mcp__`) tools such as `bash` / `read` / `write` / `edit` / `read_image` / `glob` / `grep` are NOT cataloged by the plugin — they are not indexed by `meta_search`, not dispatched by `meta_invoke`, and do not appear in the capability list. They only keep model visibility by being listed in `tools.exposed`.
- The meta-tools `meta_search` / `meta_invoke` are always Exposed and cannot be blocked; listing either in `blocked` fails loud (the policy errors out).
05相容性、維護與安全提醒
- Native (non-`mcp__`) tools such as `bash` / `read` / `write` / `edit` / `read_image` / `glob` / `grep` are NOT cataloged by the plugin — they are not indexed by `meta_search`, not dispatched by `meta_invoke`, and do not appear in the capability list. They only keep model visibility by being listed in `tools.exposed`.
- The meta-tools `meta_search` / `meta_invoke` are always Exposed and cannot be blocked; listing either in `blocked` fails loud (the policy errors out).
Apache-2.0; no tagged release yet (latest_release is null); last push 2026-08-25; repo created 2026-08-19
06常見問題
如何用 dsh CLI 安裝 dsh-capability-menu？
先裝好 Node.js 與 dsh CLI，再執行 `dsh plugin --profile web add @daweifu/capability-menu` 與 `dsh plugin --profile web add @daweifu/capability-menu-web`（伺服器端與「能力選單」tab）。`dsh plugin` 內部會轉發給 pnpm。
它如何接入 DeepSeek Harness？
它是 Cordis 插件，透過 Cordis 插件機制與 Harness 組合進同一個執行期，不會修改上游原始碼；提供統一能力目錄（`ctx.meta`）與兩個元工具（`meta_search` / `meta_invoke`）。
Exposed / Progressive / Blocked 三檔分別是什麼？
Exposed = 完整 schema 常駐模型上下文，可直接呼叫；Progressive = 不進上下文（零成本），僅在使用時經 `meta_search`/`meta_invoke` 取用；Blocked = 不被發現且被 `meta_invoke` 拒絕。這是你設定的駐留策略，而非依使用次數自動統計。
如何驗證安裝是否成功？
執行 `dsh --profile web --dump-config | grep -E 'capability-menu'`，README 說明應能看到本套件自己的 patch 層（capability-menu-registry / -search / -invoke / -policy）。
如何復原 / 解除安裝？
用 `dsh plugin --profile web remove @daweifu/capability-menu` 與 `dsh plugin --profile web remove @daweifu/capability-menu-web` 移除兩個套件。
07相關的 DSH 工作流程
dsh-routing-suite
作者 yjh051108
DeepSeek Harness（dsh）路由套件：先裝執行時注入器，再載入任務感知的推理模式路由預設（已實測 P1-P23）。
brooks-lint
作者 hyhmrright
基於 12 本經典工程書籍的 AI 程式碼評審工具，提供腐化風險診斷、書籍引用、嚴重度標籤及 6 種分析模式。
oh-dsh
作者 hust-open-atom-club
一套 DSH runtime，Desktop、Web 與 TUI 三種開發體驗。
perfect-web-clone
作者 ericshang98
網頁畫素級克隆工具：貼上 URL，即可得到一份精確測量還原的 Vite + React 復刻頁面。
08資料與來源
为 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 提供统一的能力目录（`ctx.meta`）、两个元工具（`meta_search` / `meta_…
它不修改上游源码，通过 Cordis 插件机制与 Harness 组合进同一个运行时
此頁面根據專案公開文件、儲存庫中繼資料與 DSH Plugins 的結構化解析所產生；最後核實於 2026-08-30。發現錯誤？提交更正。
最佳 DeepSeek Harness 外掛
從全目錄挑出的 12 個值得優先安裝的外掛，涵蓋各個分類。