Loading...
Loading...
Found 5 Skills
An executable Skill for developing, maintaining, distributing, and validating DeepSeek Harness (DSH) plugins. Covers host/client form judgment, bundle/profile contracts, Service and function plugins, tools, HTTP, persistence, slots, Conversation Nodes, client-side building, HMR, GitHub installation, and real combination verification.
When to use — build, extend, or debug a DeepSeek Harness (dsh) plugin — plugin naming/scope rules, the host/client entry split, cordis services, client slots/settings/locale, the apiproxy RPC, profiles and presets, self-contained bundle packaging/loading, the develop→load→reload loop, or proposing a change to dsh itself.
Use for DSH plugin compatibility, migration, upgrade, regression, or post-upgrade diagnosis, including read-only review of already-migrated plugin source and version-boundary, API, dependency, activation, or runtime compatibility problems. Inspection and diagnosis stay read-only; show a plan and obtain confirmation before any configuration, dependency, or source write.
This skill is used when users want to find plugins for DeepSeek Harness: such as asking 'Are there any plugins that can...', 'Help me install XX', or 'What interesting things are there in the ecosystem'. It discovers public repositories across individuals and organizations from the `dsh-plugin` topic on GitHub, filters candidates, waits for user confirmation, then determines the installation method from the repository declaration and verifies the mounting. It only handles finding and installing plugins; for developing new plugins, redirect to `make-dsh-plugin`.
Audit external compatibility between two DSH (DeepSeek Harness) versions and detect reverts, producing an upgrade-report directory; compares git tags with a source checkout, or published npm packages without one. Use whenever the user asks to check/compare/audit two DSH versions or whether upgrading is safe — e.g. "more changes or reverts in dsh-vX -> dsh-vY", "compare the breaking changes" — even with only two version numbers and no source location. Read-only outside the report directory; npm mode installs in isolation with --ignore-scripts.