zbsph/dsh-ppt-studio

dsh-ppt-studio is a native presentation-generation plugin built for the DeepSeek Harness runtime, distributed as the npm package dsh-ppt-studio and versioned at 1.1.5 with an installation footprint of roughly 890 kB after the 1.0.4 trim. It accepts natural-language requirements from the user, has the LLM first lock in an outline and per-slide layout, then generates each slide, runs an automated validation pass on every page, and finally delivers a .pptx file that opens in PowerPoint and remains fully editable downstream. The package declares a dsh.bundle.patch through the repository's cordis.patch.yml, so a single install command wires it into the host; the archive channel exposes the identical bytes as .tgz assets on the Releases page, with sha256 verification available to confirm the two channels match byte-for-byte.

The intended workflow starts with the user creating a new DSH session and selecting the "PPT Studio" preset, which is the only scope in which the plugin's capabilities are visible by default. That preset provisions a complete workbench: twenty-two ppt_* tools, the /ppt slash command, four bundled handbooks, and an injected workflow prompt block. Isolation is enforced by appending an absolute file:// self-locator row inside the preset's bundle composition, so the tool, skill, and prompt registrations only resolve inside that preset's registry layer; users who want the traditional profile-wide behavior can flip scope: profile in the cordis.patch.yml. A ppt_state call exposes presetDelivery.isolation, returning preset, profile-fallback, or profile to indicate the actual delivery mode.

Dependencies and operational limits are clearly bounded: Office, Edge/Chrome, and python-pptx are documented as optional enhancements, so the plugin still works without them but will explicitly degrade render, screenshot, and fallback engine capabilities and surface that fact in the delivery notes. The host must be DSH >= 0.1.7-rc.1; the desktop client uses an independent desktop profile managed exclusively by the Electron application, blocking CLI access to it and requiring the in-app plugin manager for installs and tarball URL fetches there due to a pnpm 11.7.0 + hoisted combination that triggers ERR_PNPM_MISSING_TARBALL_INTEGRITY. Freshly released versions may silently resolve back to a previous mature build during pnpm's approximately twelve-hour minimumReleaseAge window, so users who need the absolute latest must install via the .tgz path or wait out the window. The project is MIT-licensed, ships pre-built lib/ checked into git so repository-URL installs have a valid entry, and pairs each release with a Trusted Publishing (OIDC) push to npm alongside the GitHub Release asset to guarantee parity.