🐳 dsh-plugin-guide

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-guide

Then 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

---

Install & uninstall

• npm channel (published releases — the default; start here): dsh plugin --profile web add dsh-plugin-guide. The published tarball already contains dist/, 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's prepare and will refuse until the build is allowlisted; add it to the profile's allowBuilds (see publish.md).
• tarball channel: pnpm pack in this repo, then dsh plugin --profile web add ./dsh-plugin-guide-<version>.tgz.
• uninstall: dsh plugin --profile web remove dsh-plugin-guide.

Why not just read the official docs?

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).

⭐ 如果它帮到了你

…