dsh-plugin-template

1. 安装并启动 DeepSeek Harness：npx @deepseek-ai/dsh web
2. 在终端执行上面的安装命令（CLI 会解析插件并核验来源）
3. 用 dsh plugins list 确认已安装，必要时重启 Harness 生效

插件以当前 dsh 进程的权限运行，安装时可能执行代码。请先通读仓库源码与许可证，确认无破坏性命令与越权访问；本站只做索引，不对第三方插件安全性作担保。

事实信息来自公开插件目录快照（2026-10-03），介绍文案由本站再加工。

以下为插件仓库 README 全文（原始内容，由公开目录抓取整理）。

# dsh-plugin-template

English | [中文](README.zh.md)

A minimal TypeScript [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin bundle. It prints `hello world` when Harness loads it.

## Start from a fork

```sh
git clone https://github.com/YOUR-USER/dsh-plugin-template.git
cd dsh-plugin-template

pnpm install
pnpm run check
dsh plugin --profile hello add .
dsh --profile hello --dump-config | grep dsh-plugin-template
dsh --profile hello
```

A successful run includes this line in the Harness output:

```text
[dsh-plugin-template] hello world
```

For development, edit `src/index.ts`, run `pnpm run build`, then restart the profile. The generated `lib/` directory is included in the package so direct Git installs can load the built JavaScript entry.

If you rename the package, keep these values in sync:

- `package.json` → `name`
- `src/index.ts` → `name`
- `cordis.patch.yml` → both `id` and `name`

Remove it with:

```sh
dsh plugin --profile hello remove dsh-plugin-template
```

## The whole plugin

```text
package.json       # declares the dsh.bundle patch and built entry
src/index.ts       # TypeScript Cordis plugin entry
lib/index.js       # generated Harness entry
cordis.patch.yml   # registers the package in a profile
tsconfig.json      # TypeScript type-checking configuration
pnpm-lock.yaml     # locked development dependencies
```

`package.json` is the only manifest Harness needs: `dsh.bundle.patch` makes the package an installable profile bundle. `cordis.patch.yml` inserts the plugin row, and `src/index.ts` is compiled to the ordinary Cordis `name`/`apply` entry point. This template uses TypeScript and `tsdown`, but intentionally has no React Client bundle, Remote contract, or test framework. Add those only when the plugin actually needs them.

## Discoverability

Add the GitHub topic [`dsh-plugin`](https://github.com/topics/dsh-plugin) to your fork. The topic is repository metadata, not a file in the repository:

```sh
gh api --method PUT repos/YOUR-USER/dsh-plugin-template/topics \
  -H 'Accept: application/vnd.github+json' \
  -f 'names[]=dsh-plugin'
```

## License

MIT