← ClaudeAtlas

dsh-plugin-publisherlisted

Publish a validated DSH plugin package (`@deepseek-ai/dsh-*` or `@lovstudio/dsh-*`) to npm, git, or tarball channels and verify it loads in the DeepSeek Harness. Use when the user asks to publish, release, or ship a plugin. 触发:发布插件 / 上架插件 / release dsh 插件。
lovstudio/dsh-plugin-publisher-skill · ★ 1 · AI & Automation · score 70
Install: claude install-skill lovstudio/dsh-plugin-publisher-skill
# dsh-plugin-publisher Publish one validated DSH plugin package to the DeepSeek Harness distribution channels and verify each channel can load it. Input is the finished package source produced by `dsh-plugin-creator`; this skill owns everything after the commit: validation, repo gates, per-channel release, and load verification. There is **no official DSH plugin marketplace**. The three supported channels are npm, git, and tarball; GitHub's `dsh-plugin` topic is the discovery mechanism. Publish the same plugin across as many channels as the user's distribution intent needs, keep channel state out of canonical source, and report evidence per channel. ## Triggers ### Activate when - 用户说“发布这个 DSH 插件”“上架插件”“推到 npm”“打个 release”“导出 tarball 给用户装”。 - The user asks to publish, release, distribute, upload, or package an existing DSH plugin. ### Do not activate when - 用户要新建、实现或修改插件;交给 `dsh-plugin-creator`。 - 用户只是要本地验证插件可加载(`dsh --profile demo --dump-config`),并没有发布意图。 ## Product boundary - Input is a local plugin package that already passes `dsh-plugin-creator`'s gates: `package.json` invariants hold, `dsh.bundle.patch` (or `dsh.plugin.json` for the yoda-style registry channel) is present, and no stale build artifacts sit in the tree. - When the user does not name a channel, default to npm for `@lovstudio/dsh-*` plugins whose `publishConfig.access` is `public`, and to git for plugins meant to be consumed from source. Do not ask a channel-selection question when the r