dsh-plugin-builder

A guarded, in-editor plugin workshop for DeepSeek Harness — a settings tab plus the cordis-plugin-development skill it hands to your agent.

English | 中文

What it does

DSH plugins are small Cordis packages: a Host half that registers services, tools or skills, and an optional browser half that adds UI. Writing one well means knowing the live API of the host you are running against, not the API from a blog post.

This package puts that workflow inside DSH:

• it registers the bundled cordis-plugin-development skill globally, so the agent can follow a guided design → prototype → implement → validate → package → install workflow;
• it adds a Settings → Plugins → workshop tab where you describe what you want in one box and pick an engine (Claude Code mode, Cordis mode, or standard mode); the tab opens a dedicated session with the skill prompt pre-filled instead of hijacking your current conversation;
• it ships the scaffolding and validation toolkit the skill calls: inspect-target.mjs (read the real host versions), scaffold-package.mjs (generate a buildable package), validate-package.mjs (check the package contract), plus the prototype contract and validation matrix references.

The tab never installs anything by itself. It creates a session, seeds the prompt, and leaves the confirmation gates to the agent and to you.

Requirements

• DeepSeek Harness 0.2.1-rc.5 (Cordis 4.0.5). The plugin is validated against that line: it type-checks against the published @deepseek-ai/*@0.2.1-rc.5 declarations, builds a ModuleLoader client bundle, and its unit tests run on Node 22/24.
• Node ^22.19.0 || ^24.0.0.
• A profile that composes the skills service (every standard DSH Web/Desktop profile does).

Install

dsh plugin --profile web add dsh-plugin-builder

Restart that profile. The row is mounted by the package's own cordis.patch.yml, so no manual edit of your profile patch layer is needed:

- insert:
    - id: dsh-plugin-builder
      name: dsh-plugin-builder

Use it

1. Open Settings → Plugins → workshop (the tab label follows your UI language).
2. Describe the plugin you want and choose an engine:
   • Claude Code mode (default) — a dedicated session on the local Claude Code agent;
   • Cordis mode — the Cordis creation preset;
   • Standard mode — the host's default agent.
3. Start it. The tab opens a fresh session in the current workspace, places /cordis-plugin-development … plus your requirement in the composer, and closes itself. It does not send the message for you.
4. Follow the skill's gates: design confirmed first, then implementation, then validation evidence, then an explicit confirmation before anything is installed into a profile.

If the selected preset is missing or broken, the tab reports it before creating a session, so you never end up with an empty session and a silent failure.

What is in the package

Path	Purpose
lib/index.js	Host entry: parses the bundled SKILL.md and registers it through ctx.skills.register()
lib/client.js	Browser bundle: window.__ModuleLoader__.load closure factory registering the settings.plugins.tab surface
lib/client-helper.js	Shared helper (placeSkillPromptInDraft, focusComposerSoon) exported for other tabs
skills/cordis-plugin-development/	The skill itself: SKILL.md, the prototype contract, the validation matrix, and the three toolkit scripts
lib/types/	Generated declarations

Skill precedence

DSH 0.2.1 already ships a skill named cordis-plugin-development with its agent presets. When that skill is present the plugin keeps it and skips its bundled copy, so load order can never decide which workflow the agent follows. On hosts that do not ship the skill, the bundled copy is registered instead. The workshop tab keeps working either way.

Compatibility notes

• The plugin runtime is validated against DSH 0.2.1-rc.5: the registration shape (name, description, invocation, source: 'bundled', provider, resourceBase, path, content) matches the 0.2.1 SkillRegistration type, and the client injects only shell-provided modules.
• The bundled reference material under skills/cordis-plugin-development/references/ was written against the 0.1.5-rc.2 interface line. The skill therefore tells the agent to call inspect-target.mjs first and to treat those references as background, not as an API contract. Read them the same way.

Development

npm install
npm run build      # esbuild host/client bundles + tsc declarations
npm run typecheck  # tsc against the published 0.2.1-rc.5 declarations
npm test           # unit tests (scaffold tests need DSH_SOURCE_CHECKOUT, see below)
npm run validate:package

The scaffold/validation tests exercise the toolkit against a real DSH source checkout. Point DSH_SOURCE_CHECKOUT at a deepseek-harness checkout to run them; without it that suite is skipped (the published package has no checkout).

Known limitations

• The workshop tab only starts a session; the agent still needs the session to have the cordis-plugin-development skill in scope (it is registered globally, so it is).
• Reference documents are version-stale by design (see above) and are scheduled for a 0.2.1 rewrite.
• Generated plugins are ordinary DSH bundles; installing one is always your explicit decision.

License

MIT © WilShi. The bundled skill and toolkit are part of this package.