DSH Plugins
返回列表
🖥️

dsh-plugin-template

客户端 更新于 2026.08.15

在终端中运行以下命令:

dsh plugin install ZhijiangTang/dsh-plugin-template

将以下提示词粘贴到 DeepSeek Harness 对话框中:

在 DeepSeek Harness 终端中执行 dsh plugin install ZhijiangTang/dsh-plugin-template 即可安装本模板插件,源码详见 https://github.com/ZhijiangTang/dsh-plugin-template

插件介绍

Building a tool plugin from scratch for the DeepSeek Harness ecosystem is far more involved than writing a single function. The schema DSL demands property-level required instead of a top-level array, pnpm enforces a 24-hour maturity gate on newly published versions, and local file: install is the only reliable way around Node resolving symlinked @deepseek-ai/* modules. Miss any of these and your plugin silently parks in PENDING or crashes with ERR_MODULE_NOT_FOUND. dsh-plugin-template bakes all these battle-tested pitfalls into a minimal working skeleton so you can go straight to business logic.

The template is pure ESM, zero-dependency, and requires no build step. It ships a complete hello_world placeholder tool exercising every critical surface: parameter schema, output schema (demonstrating property-level required and oneOf-null patterns), render, and execute. A mount self-check runs through the real ctx.tools.execute pipeline, and the README packs a first-batch gotcha cheat-sheet covering local install, schema expression, allowBuilds, and PENDING silence alongside the hard rules every tool must follow.

If you are drafting your first contribution to the Harness ecosystem or simply want to validate a quick pipeline-integration idea, fork this template, swap the placeholder comments in package.json and index.js, and you land on a structurally valid, pipeline-verified starting point that beats assembling the skeleton line by line from the official docs.

使用场景

  • 从零起步:克隆模板后替换占位注释即可跑通 mount 自检管道
  • 快速验证:用 hello_world 骨架先确认 schema、render、execute 全链路再叠加业务逻辑
  • 学习规范:通过 note 字段与 gotcha 速查表直接掌握属性级 required、oneOf-null 等 schema DSL 事实

适合人员

  • 首次向 DeepSeek Harness 生态贡献工具插件的开发者
  • 想跳过重复模板组装、直接写业务逻辑的插件作者
  • 需要团队统一插件骨架结构再走 npm 发布流程的工程负责人