Your agent stops inventing DSH plugin APIs.
The DeepSeek Harness plugin-development knowledge base, installed as an agent skill — official docs, a version-compatibility matrix, migration seams and battle-tested pitfalls, plus a scaffolder/checker CLI.
dsh plugin --profile web add dsh-plugin-guideThen just ask: "Use the dsh-plugin-guide skill to build me a … plugin."
Official repository. This is the only official repository of dsh-plugin-guide, maintained by PerryLink. Same-name repositories under other accounts are not affiliated.
English · 简体中文 · Español · Português · हिन्दी
dsh plugin --profile <name> add dsh-plugin-guide- npm channel (published releases — the default; start here):
dsh plugin --profile web add dsh-plugin-guide. The published tarball already containsdist/, so no build step runs. - git channel (latest
main, or an unreleased commit):dsh plugin --profile web add github:PerryLink/dsh-plugin-guide#<sha>— pin a commit for reproducibility.⚠️ dist/is not committed, so pnpm must run this package'sprepareand will refuse until the build is allowlisted; add it to the profile'sallowBuilds(see publish.md). - tarball channel:
pnpm packin this repo, thendsh plugin --profile web add ./dsh-plugin-guide-<version>.tgz. - uninstall:
dsh plugin --profile web remove dsh-plugin-guide.
Because the official docs are written for someone who already knows which page to open, and DSH ships a prerelease every 1.7–2.8 days with breaking changes. This plugin closes the three gaps that costs authors the most time:
| Gap | What this plugin adds |
|---|---|
| "Which DSH am I even targeting?" | A version matrix: the four different values that all call themselves "latest", the frozen sub-package latest tags, the breaking-change seams, and how to pick a peerDependencies range. There is no stable line — every published version is a prerelease. |
| "What does this break?" | A migration guide covering 0.1.6-alpha.2 → 0.2.1-alpha.2 as citable seams with symptom and fix, each with its official source — including a data-loss hazard and a change that makes prompts fail before a model request is built. |
| "Is my plugin actually correct?" | A zero-dependency CLI (dsh-plugin-dev new / check / verify) plus an offline verbatim mirror of the official docs, so your agent can cite the exact page instead of guessing. |
Prove it works in 60 seconds:
dsh plugin --profile web add dsh-plugin-guide
npx dsh-plugin-guide new hello-plugin # scaffold a plugin
cd hello-plugin && npx dsh-plugin-guide check --json # 16 static checks📖 Prefer reading it as a site? perrylink.github.io/dsh-plugin-guide — every chapter as its own page, plus a machine-readable llms.txt for assistants.
Also on the 1024 store channel: npm i -g dsh1024, then dsh1024 plugin --profile web add dsh-plugin-guide (counts toward the deepseek1024.com install ranking).
这个插件是 DSH 插件家族的一员（95 个，全部 Apache-2.0）。如果你在用，给个 star —— 它不会解锁任何功能，但会让下一个人在搜索里更容易找到它。
English: part of a 95 plugin family for DeepSeek Harness. If it is useful, a star helps the next person find it — nothing is gated behind it.
Everything you need to build DeepSeek Harness plugins.
Official docs archive · Cordis primer · community deep-dives · battle-tested pitfalls · agent skill · CLI toolchain
Workflow overview: request → policy / review → verdict. The examples below use the real command surface.
content counts as stated in the README (What you get)
| Surface | Status |
|---|---|
| Harness | DeepSeek Harness dsh-v0.2.1-alpha.2 (d743267388641bc76f17c45ce8b4c231aed1d32c, the newest master tag and master HEAD, 2026-10-09); npm latest = next = 0.2.0-rc.2, alpha = 0.2.1-alpha.2. There is no stable line — all 31 npm versions and all 26 GitHub Releases are prereleases. The official-docs mirror is pinned to that same commit (429 md pages, re-synced 2026-10-13; see references/official-docs/SNAPSHOT.md). guide/migration-0.2.md covers 0.1.6-alpha.2 → 0.2.1-alpha.1 in §0–§12 and 0.2.1-alpha.1 → 0.2.1-alpha.2 as 19 citable seams in §13; the 20 breaking-change guides added since the previous baseline (19 under v0.2.1-alpha.1 plus one backfilled into v0.2.0-rc.2) are all in the mirror. |
| Node | `^22.19.0 |
| Platforms | All (plain ESM bundle; no native code, no network) |
| Model | Any (no model interaction) |
dsh-plugin-guide is the DSH plugin-development knowledge base plus a CLI toolchain, packaged as one installable bundle. The knowledge base registers as the dsh-plugin-guide agent skill (visible in every session catalog, loading workflow steps, official docs, and community deep-dives on demand); the dsh-plugin-dev CLI adds three mechanical layers on top of it.
- Plugin contract & hard rules — effects/disposers, waterfall
next(), host-owned session events,MessageSourceMap, the weakest-mechanism ordering, Schemastery config, UI and performance rules. - Official docs archive — a verbatim copy of the official repo docs (EN + ZH), byte-identical to upstream at the last verified snapshot, including the pages that never reach the documentation site.
- Version adaptivity — guide/version-matrix.md: the five different "latest" values, the frozen sub-package
latesttags, the four breaking-change seams, the canonical peer range and how to pick one, the session-format lineage V0→V4, and the 19 breaking changes that landed in0.2.1-alpha.2. - Migration guide — guide/migration-0.2.md: every breaking change from
0.1.6-alpha.2to0.2.1-alpha.1(session format V4, the settings rebuild, invariant removal,readBytes, new slots, retiredpluginmessage source), each with its official source and a 12-item checklist. - Official in-repo skill, distilled — references/official-plugin-dev-skill.md: the harness's own
cordis-plugin-developmentworkflow, prohibitions, display-metadata checklist, practices, and UI/performance rules. - Cordis primer — the five concepts and the mechanism timeline (repository-plugin introduced 0809, removed 0811; the two install channels).
- Verified issue index — guide/unfixed-issues.md: 22 unfixed + 11 newly verified items with
path:line, workarounds, fixing commits, design-vs-bug table, and an explicit "unreproducible" section. - 30+ real-world pitfalls with root cause + fix (cordis dual copies, tsconfig trio, multi-frame zstd sessions, Windows junctions, stale npm
latest,file:installs loading a copy, live patch writes, …). - Community deep-dives — 114 community repositories archived (15 deep-dived), plus a full source index where every fact links to its origin.
- CLI toolchain —
dsh-plugin-dev new / check / verify: scaffold, static-check (including display metadata and multi-patch manifests), and pack-verify DSH plugins; every check links back to the skill section it enforces.
| Path | What it is |
|---|---|
SKILL.md |
The dsh-plugin-guide agent skill: hard rules + task-based development paths |
package.json · cordis.patch.yml · index.js · locale/ · icon.svg |
The installable DSH bundle: dsh.bundle.patch manifest, entry point that registers the skill, and the display metadata Plugin Manager reads |
guide/plugin-dev-guide.md |
The complete development guide (10 chapters) |
guide/version-matrix.md |
Version adaptivity matrix: the five "latest" values, frozen sub-package latest tags, breaking-change seams, peer-range selection, session-format lineage, and the 19 changes in 0.2.1-alpha.2 |
guide/migration-0.2.md |
Breaking-change migration guide for the 0.2 generation |
guide/unfixed-issues.md |
Source-verified bug index + fixed-on-master list + design-vs-bug table |
guide/quick-reference.md |
One-page cheat sheet (5 languages) |
guide/links.md |
Curated URL index: official dev docs (site ↔ local copies) + community doc links + repo-only pages |
guide/when-to-retire-a-plugin.md |
Retiring and freezing plugins: the criteria and the measured data behind a portfolio audit (EN + ZH) |
guide/choosing-a-plugin.md |
Choosing a plugin: who leads each capability surface, with the measured numbers and the verification caveats (EN + ZH) |
references/official-docs/ |
Verbatim copy of the official repo docs (EN + ZH) |
references/official-plugin-dev-skill.md |
Distilled official in-repo plugin-development skill |
references/*.md |
Research reports: repo docs, website, Cordis, the paper, community ecosystem, 114-repo archive (15 deep-dived) |
scripts/ |
Idempotent download scripts + integrity checker + topic snapshot generator |
bin/ · src/cli/ · dist/ |
The dsh-plugin-dev CLI: scaffolder, checker, verifier (TypeScript, tsdown-bundled) |
templates/ |
TS + JS scaffold skeletons: contract template, Config, tests, cordis.patch.yml, locale metadata, icon, five-language READMEs |
downloads/ |
Raw snapshots — generated by scripts/, not committed |
The bundle ships the zero-runtime-dependency dsh-plugin-dev CLI (bin/ → tsdown-bundled dist/dsh-plugin-dev.js). Each check cites the skill section it enforces, so an agent can keep auditing manually.
dsh-plugin-dev new <name> [--lang ts|js] [--dir <path>] [--force] [--git]
dsh-plugin-dev check [--cwd <dir>] [--json] [--strict]
dsh-plugin-dev verify [--cwd <dir>] [--dsh <bin>] [--pnpm <bin>]
dsh-plugin-dev seams <query> | --since <version> # is this API in my target host?| Subcommand | What it does |
|---|---|
new <name> |
Scaffolds a TS or JS plugin repo: src/index.ts contract template, Schemastery Config, tests, tsdown/vitest, commented cordis.patch.yml, five-language READMEs. Idempotent; refuses non-empty targets without --force. |
check |
Static checks: cordis.patch.yml validity, package.json metadata (dsh.bundle.patch pointer, peer deps, engines, files whitelist), five-language README consistency, engineering red-line patterns. Emits CI-consumable JSON. |
verify |
pnpm pack, then install/start/uninstall the bundle in a clean mkdtemp DSH_HOME profile (aligned with verify:self-contained). Failures report the log tail plus suggestions. |
The CLI has no hardcoded tunables — each is a flag or an environment variable.
| Tunable | Flag | Env | Default |
|---|---|---|---|
| Templates directory | — | DSH_PLUGIN_DEV_TEMPLATES |
<package>/templates |
| dsh binary | --dsh |
DSH_PLUGIN_DEV_DSH |
dsh |
| pnpm binary | --pnpm |
DSH_PLUGIN_DEV_PNPM |
pnpm |
| Install/pack timeout | --timeout |
DSH_PLUGIN_DEV_TIMEOUT |
300000 ms |
| Headless smoke timeout | --smoke-timeout |
DSH_PLUGIN_DEV_SMOKE_TIMEOUT |
120000 ms |
dsh-plugin-dev is an upstream candidate for the official plugin-development CLI (planned item C12): the scaffolder/checker/verifier are the mechanical layers, while SKILL.md + guide/ stay the cognitive layer.
# 1. install the bundle into your profile — npm first
dsh plugin --profile web add dsh-plugin-guide
# 2. restart and verify the row
dsh --profile web --dump-config | grep -A3 'id: dsh-plugin-guide'dist/ is not committed, so pnpm has to run this package's prepare build script — which pnpm 10+ blocks
until you explicitly allowlist it (allowBuilds). That is a documented pitfall of git installs, not a
defect, but it makes the git channel a poor first experience. See Install & uninstall
for the git and tarball channels when you specifically want an unreleased commit.
Then just ask your agent: "Use the dsh-plugin-guide skill to build me a … plugin."
Or drive the CLI directly:
npx dsh-plugin-guide new hello-plugin # scaffold a TS plugin repo
npx dsh-plugin-guide check --json # static-check it
npx dsh-plugin-guide verify # pack + clean-profile smokeYou can also copy the whole folder into your agent's skill directory (relative paths stay intact):
# Windows (PowerShell)
pwsh -File scripts/install-skill.ps1 `
-Target "$env:USERPROFILE\.deepseek\skills\dsh-plugin-guide" # or <project>\.agents\skills\dsh-plugin-guide# macOS / Linux
pwsh -File scripts/install-skill.ps1 -Target ~/.deepseek/skills/dsh-plugin-guide # or <project>/.agents/skills/dsh-plugin-guideThe installer skips downloads/ (generated) and .github/, then verifies every copied file byte-for-byte. A manual Copy-Item -Recurse of the whole folder also works.
These are the plugin's real entry points; install once, then call one.
Command
dsh-plugin-dev seams L3Output
1 seam(s):
L3 webRuntime service replaced by webStartup
kind service-renamed
lands in 0.2.1-alpha.2
confidence documented
official docs/upgrade-guide/v0.2.1-alpha.1/web-listener-trust-config/guide.md
removed service webRuntime; row web-runtime; ctx.webRuntime.lanAddresses; wildcard --host
instead webStartup (row web-startup), concrete host literals
detectable yes — inspect: src/**/*.ts, cordis.patch.yml
Observed from README.md:152 (CLI toolchain); src/cli/commands/seams.ts:54; data/seams/index.json:44
Input
node bin/dsh-plugin-dev.js seams no-such-seam-xyz
Output
no seam or capability matches "no-such-seam-xyz". This is an absence of evidence in the knowledge base, not evidence that the API is absent from your target host — check references/official-docs/ before concluding either way.
Observed from plugins/dsh-plugin-guide/src/cli/lib/seams.ts:122-130; plugins/dsh-plugin-guide/src/cli/commands/seams.ts:87-92; plugins/dsh-plugin-guide/tests/seams.test.ts:88-90
The skill bundle exposes no Schemastery Config — it registers the knowledge base as an agent skill with no tunable keys. The dsh-plugin-dev CLI reads its tunables from flags and DSH_PLUGIN_DEV_* environment variables (see CLI toolchain).
| Surface | Kind | Notes |
|---|---|---|
dsh-plugin-guide |
skill | Registered via ctx.skills; loads SKILL.md + ./guide/ + ./references/ on demand |
dsh-plugin-dev |
bin (CLI) | new / check / verify subcommands; not a DSH plugin row |
- Permissions: declares
filesystem:readin its workshop manifest. - Data: read-only — reads its own bundled
guide/andreferences/files. No network requests, no writes, no model calls.
- Read-only knowledge base. The bundle only reads its own files; it never writes, never calls the network, and never invokes a model.
- Official docs are verbatim copies.
references/official-docs/is never edited here; report issues upstream and re-sync only withscripts/sync-official-docs.ps1. - Distribution boundaries. Bundled third-party content keeps its upstream license; see NOTICE.md (e.g.
downloads/is local-only;awesome-dsh-pluginsmust not be redistributed).
- Official docs are a snapshot. Re-sync with
scripts/sync-official-docs.ps1when upstream moves; the freshness stamp and commit hash referencereferences/official-docs/SNAPSHOT.md. downloads/is generated, not committed. Raw snapshots (community repo archives, Discussions, articles) must be generated with the scripts before use.awesome-dsh-pluginscontent is local-only. Its upstream declares an internal-use constraint, so it is not redistributed with the repo.
Every channel resolves from this repository or from npm, so one tag reaches all of them; only the Gitee mirror is a scheduled copy:
| Channel | Source of truth | How it updates |
|---|---|---|
npm (dsh-plugin-guide) |
this repo's package.json |
.github/workflows/release.yml on a v* tag: verify-kit gate → CHANGELOG section check → npm publish --provenance (skipped when the version already exists) |
| GitHub Release | the same tag | the same workflow creates it idempotently from the tag |
| Discovery badges (npm version, GitHub tag, DSH Market, dsh-doctor) | live lookups | nothing to publish — they read npm/the registry on each render |
| Gitee mirror | this repo | a read-only scheduled mirror, not a publish target: it is force-aligned to the GitHub tip (--force-with-lease) by the family's gitee-sync workflow, so main is normally one scheduled run behind. Gitee never receives a tag push from here; compare git ls-remote against GitHub before reporting the mirror stale |
| DSH Desktop Market / dsh1024 | npm | the market installs the npm package, so a published version is immediately installable; no per-version submission |
pwsh -File scripts/sync-official-docs.ps1 # verbatim docs copy from a local checkout
pwsh -File scripts/download-sources.ps1 # official site/docs, Cordis, paper
pwsh -File scripts/download-community-repos.ps1 # community repositories (codeload tarballs)
pwsh -File scripts/download-community-articles.ps1 # zh/en/HN community articles
pwsh -File scripts/archive-discussions.ps1 # official Discussions (needs $env:GH_TOKEN)
pwsh -File scripts/gen-topic-snapshot.ps1 -OutDir <dir> # dsh-plugin topic census
pwsh -File scripts/verify-kit.ps1 -Checkout <checkout> # critical paths + link scan + docs driftThe skill bundle (index.js) is plain ESM with no build step; the dsh-plugin-dev CLI is TypeScript built by tsdown. Gates:
pnpm install --frozen-lockfile
pnpm run typecheck && pnpm run typecheck:ci
pnpm test
pnpm run build
pnpm run verify:artifacts # dogfood self-check + scaffold smoke (no network)
pnpm run verify:self-contained # pack + clean-profile install/start/uninstall smoke
pnpm run check:readmes # five READMEs share section structure
pnpm run check:parity # translations have identical block counts
pnpm run check:facts # self-stated numbers match data/facts.json
pnpm run check:ps1-bom # PowerShell scripts keep their UTF-8 BOM
pnpm pack
pwsh -File scripts/verify-kit.ps1 # critical paths + link scan (+ docs drift with -Checkout <checkout>)dsh, deepseek-harness, dsh-plugin, cordis, agent-skill, plugin-development, knowledge-base, cli, scaffold, checker
- PerryLink — creator and maintainer: knowledge-base content, the installable-bundle transformation, ecosystem submissions, and community engineering.
- @Yisa-yi — product manager. Took part in the whole design arc, from the first outline to the shipped bundle, and owned the shape of the product rather than its code: the call to ship it as an installable bundle that registers an on-demand agent skill (the docs site renders those same sources rather than carrying a separate content set), the information architecture of the 10-chapter guide, the "every fact links to its origin" rule, and the split between the cognitive layer (
SKILL.md+guide/) and the mechanical layer (dsh-plugin-dev new / check / verify). Set the evidence standard behindguide/unfixed-issues.md—path:lineagainst a named host commit, a design-vs-bug table, and an explicit unreproducible section — and the freeze/retire criteria inguide/when-to-retire-a-plugin.md. Held the scope line (read-only, no network, no model calls, no tunable keys) and the five-language README parity requirement. - Day-to-day maintenance is assisted by DeepSeek Harness agents (they hold no GitHub account and are listed here for transparency, not as contributors).
This project is part of the DeepSeek Harness plugin family from PerryLink. The roster stays collapsed below so every README keeps a short first screen; expand it to see every row and its status.
Expand all plugins
Community-maintained, not an official DeepSeek product. DeepSeek Harness is in developer preview and ships breaking changes; when in doubt, the official docs in references/official-docs/ are the source of truth.
All PerryLink plugins are browsable in the built-in DSH Desktop Market: Market → Sources → add source → paste https://perrylink-dsh-catalog.perrylink.workers.dev/catalog-source.json → select it. Installation still goes through the Market's npm-identity verification and your confirmation.
Apache License 2.0 © 2026 dsh-plugin-guide contributors — our own text (SKILL.md, guide/, references/, scripts/, this README) is Apache-2.0; bundled third-party content is documented in NOTICE.md.