Plugin Markets & Managers

dsh-snapmarketing

xDylanLong/dsh-snapmarketing · ★ 2

xDylanLong

dsh-snapmarketing is a thin DeepSeek Harness surface for discovering, installing, and managing allowlisted plugins.

License
Apache-2.0
Added
2026-08-16
Maintenance
active
Install kind
github
Manifest details
Manifest status
Not verified
Manifest path
-
Manifest checked
2026-08-19
Lifecycle scripts
None found

Static manifest checks report declarations only; they are not compatibility or security review.

安装

dsh plugin --profile web add github:xDylanLong/dsh-snapmarketing

GitHub 源码安装:首次需按提示配置 allowBuilds 构建授权后重试

For install and environment setup, plus plugin development tutorials, see DSH community docs ↗

README

Source README · body: en · Read Chinese README

Table of contents
  1. SnapMarketing
  2. Install
  3. What you get
  4. How it works
  5. Security and boundaries
  6. Development
  7. Catalog and documentation
  8. License

SnapMarketing

中文 | English

License: Apache-2.0

The marketing plugin center for DeepSeek Harness: discover, search, install, and manage marketing-focused plugins inside Harness.

SnapMarketing is a thin layer on top of Harness. It reuses Harness profiles, the existing installer, and the plugin runtime, so marketing plugins remain part of Harness's normal lifecycle.

Install

dsh plugin --profile web add @snapmarketing/dsh-plugin-center

Restart dsh web, then open Settings → Plugin Market.

For the product overview and interface, visit the dsh-snapmarketing website. This repository contains the installation and runtime code for Plugin Center.

What you get

  • Marketing plugin catalog — a curated, package-shipped catalog with names, descriptions, categories, versions, repositories, and install sources.
  • Search and filtering — search by plugin name or description to find tools for a marketing workflow.
  • One-click install and uninstall — select a catalog entry and let Harness perform the real package operation; the UI shows progress and the operation result.
  • Actual installed state — reads the active Harness profile inventory instead of treating a button click as proof that a plugin is live.
  • UI and capability plugins — catalog metadata clarifies the expected role; UI plugins own their surface, while capability plugins are used through Harness, Agent, or their declared workflow.
  • Clear refresh guidance — when Harness needs a refresh after installation, the page reports the pending state explicitly.

How it works

Bundled marketing catalog
          ↓
SnapMarketing Plugin Market
          ↓  validated plugin id
Harness existing installer
          ↓
Harness Loader and plugin runtime

The catalog lives at packages/plugin-center/registry/plugins.json and ships with @snapmarketing/dsh-plugin-center. The Host validates the Manifest, resolves the selected plugin id to an approved package source, and delegates installation or removal to Harness. Installed clients do not call GitHub at runtime.

Security and boundaries

SnapMarketing intentionally remains a surface layer around Harness. It does not:

  • host plugin packages or run a separate Marketplace backend;
  • create accounts, process payments, or accept arbitrary uploads;
  • inspect, analyze, or sandbox third-party plugin source code;
  • replace Harness's package manager, Loader, UI slots, or plugin lifecycle.

Manifest policy rejects unapproved install sources such as HTTP URLs, local paths, and arbitrary Git sources. The catalog is a curated allowlist, not an endorsement. Install third-party plugins only when you trust their source and permissions.

Development

pnpm install
pnpm dev

pnpm dev builds SnapMarketing, links the local Plugin Center into a web profile, starts Harness Web, and watches the client bundle. The default isolated temporary home is named dsh-snapmarketing-dsh-home; the default address is http://127.0.0.1:3081.

Useful overrides:

DSH_ROOT=/path/to/deepseek-harness-demo pnpm dev
DSH_HOME=/tmp/dsh-snapmarketing-dsh-home pnpm dev
DSH_PORT=4099 pnpm dev
DSH_SKIP_HARNESS_BUILD=1 pnpm dev

For the current project only:

pnpm dsh:add
pnpm dsh:remove

Run the standard checks with:

pnpm test
pnpm typecheck
pnpm build
pnpm check:package

Catalog and documentation

When adding or updating an entry, verify its package name, repository, version, category, and install source. Keep the Thin Layer boundary intact: reuse Harness installation and UI APIs rather than introducing a parallel package or layout system.

License

Apache-2.0