返回目录

dsh-capability-menu

编辑精选维护状态: 活跃

pkufudawei/dsh-capability-menu

统一能力菜单插件:通过 Exposed / Progressive / Blocked 三级策略管理 MCP 工具与技能的暴露程度(上下文占用)与执行模式。

前往 GitHub
$ dsh plugin --profile web add @daweifu/capability-menu

62

星标

0

Fork

TypeScript

语言

Apache-2.0

许可证

2026-08-19

创建于

2026-08-25

最近推送

一个 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)

安装步骤

  1. 01

    $ dsh plugin --profile web add @daweifu/capability-menu

  2. 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 适配与能力边界

DSH 适配原生运行时

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 runtimea 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 mechanism
  • Two 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 invoked
  • Exposed / Progressive / Blocked three-tier policy

    a policy config of tools/skills exposed / progressive / blocked rulescontrols 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).
2026-08-192026-08-25作者未说明

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` 移除两个包。

08数据与来源

  • 作者声明github.com4351e91b77e6…

    为 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 提供统一的能力目录(`ctx.meta`)、两个元工具(`meta_search` / `meta_…

  • 作者声明github.com4351e91b77e6…

    它不修改上游源码,通过 Cordis 插件机制与 Harness 组合进同一个运行时

页面基于项目公开文档、仓库元数据和 DSH Plugins 的结构化解析生成;最后核验于 2026-08-30。发现错误?提交更正。

🏆

最佳 DeepSeek Harness 插件

从全目录挑出的 12 个值得优先安装的插件,覆盖各个分类。

DSH Plugins 是独立的 DeepSeek Harness 插件市场,与 DeepSeek 官方无关,也不代表官方背书。第三方插件未经安全审计,安装前请审查源码。

每周获取最新的 DeepSeek Harness 插件,绝不滥发。