dsh-experts (DSH Expert Marketplace)

An out-of-tree DSH bundle that brings the Awesome DSH Experts catalog (community experts and expert groups) into the DeepSeek Harness Web UI — without any changes to deepseek-harness itself.

> DSH ("everything is a plugin") ships with no first-class "Expert / Expert Group" concept. This bundle fills that gap: a Settings → section tab (the same settings.section slot the reference dshmarket client uses) to browse and copy experts, plus an optional compose-box entry to inject an installed expert group into the chat.

Overview

• Settings → section tab — browse the catalog by category/kind, search, view details, and copy a ready-to-paste @expert <id> invocation block. Registered into the verified settings.section slot.
• Composer entry (chat input) — an optional button that opens a picker and copies an expert/group invocation block into the chat input. Note: deepseek-harness 0.1.0-rc.6 does not expose a composer input slot, so this entry is expected to silently degrade in that version; the Settings-tab clipboard flow is the working path. The slot is configurable (DSH_EXPERT_MARKETPLACE_COMPOSER_SLOT).
• Same-origin HTTP API — POST /api/expert-marketplace with methods bootstrap, list, detail, groups, refresh, packs, packDetail.
• Agent tools — registers expert_list / expert_detail tools (best-effort, only when @deepseek-ai/dsh-tools is available).

Compatibility

The client bundle registers via the native __ModuleLoader__.load contract and only consumes the slots, locale, theme client services, so it degrades gracefully (never crashes the Web UI) on versions where those differ.

Install / Uninstall

Install (from git):

dsh plugin --profile web add https://github.com/fuchao2pku/dsh-experts.git

Install (local dev, symlinked):

dsh plugin --profile web add /path/to/dsh-experts

Then (re)start the Web profile:

dsh --profile web web

Uninstall:

dsh plugin --profile web remove dsh-experts
dsh --profile web web   # restart to apply

Quick start

1. Install the plugin and restart the Web profile (above). 2. Open Settings → Expert Marketplace. 3. Search or filter by category/kind; open an expert or expert group. 4. Click Add to chat to copy its @expert <id> invocation block to your clipboard, then paste it into the chat input.

Example: paste @software-team followed by a feature request to invoke the multi-role software team (product-manager → architect → engineer → QA).

Configuration

All options default sensibly and can be overridden via cordis.patch.yml or environment variables:

Permissions & data

• Network: the plugin's host (Node) process fetches a single pre-built catalog.json from catalogUrl (default: the companion awesome-dsh-experts repo's raw catalog.json). The browser never contacts GitHub — it only calls the same-origin POST /api/expert-marketplace.
• Storage: catalog data is cached in-memory, best-effort in the system temp dir (<tmpdir>/dsh-experts/catalog.json), and a bundled catalog-seed.json is the offline fallback. No personal files are read or written.
• No secrets: the plugin ships no credentials and never transmits user data off-host except the catalog fetch above (same as any web page loading a static JSON).
• Untrusted catalog: the remote catalog is treated as untrusted input — every entry is schema-validated and never executed as code; only its human-readable text + a copyable @expert <id> hint are surfaced in the UI.

Safety design (why it won't crash your DSH install)

This bundle was written to the explicit contract: installing it must never crash the host or the Web UI. Mechanisms:

• Zero build step — pure ESM JS, no tsdown/TypeScript compile, so there is no build failure surface and every file is directly loadable + testable in plain Node.
• Defensive perimeters — every external input (catalog JSON, HTTP params, agent-tool args, UI entries) is validated and never throws; failures become safe empty structures.
• Lazy optional dependencies — all @deepseek-ai/* packages and react are optional peer dependencies, imported lazily inside try/catch. Missing them degrades a feature, never the plugin.
• Per-feature try/catch in apply() — web server route, agent tools, system-prompt section, and UI tabs are each independently guarded; one failing feature never prevents the others (or the plugin mount).
• Bundled seed catalog — if the remote fetch fails, the last-good/seed catalog is served, so the Settings tab always renders.
• Double-guarded composer slot — Cordis throws when registering into an undeclared slot; both the slots.inject and slots.register calls are wrapped, so a wrong slot name for a given DSH version silently degrades the composer entry while the Settings tab keeps working.
• Same-origin API guard — cross-origin requests are rejected with a structured 403 instead of throwing.

Data source, updates & storage (experts / expert groups)

Short answer to "does dsh web load straight from the GitHub repo?" — No. The browser never touches GitHub. The host (Node) process fetches a pre-built catalog.json; the browser only calls the same-origin API /api/expert-marketplace. This mirrors how dshmarket sources its catalog.

1. Source of truth: experts/*.md (per-expert Markdown + YAML frontmatter) in the companion catalog repo awesome-dsh-experts. 2. Build: scripts/scan.mjs (in that repo) aggregates them into catalog.json (machine-readable, consumed by this plugin) and CATALOG.md (human-readable). 3. Update: that repo's .github/workflows/scan.yml regenerates the catalog on every push and on a daily cron (UTC 02:00). It runs scan.mjs --local --remote (local experts are always included, plus discovery of community repos tagged dsh-expert / dsh-expert-pack) and commits the refreshed catalog.json back. 4. Runtime load: src/host.js CatalogSource seeds from the bundled catalog-seed.json, then refreshes from cfg.catalogUrl on startup / Settings-tab open / manual refresh. Fetches are conditional (ETag / Last-Modified + 304) so re-fetching is cheap, exactly like dshmarket's registry fetch. 5. Storage / caching (3 layers): in-memory entries; best-effort on-disk cache in the system temp dir; bundled catalog-seed.json offline fallback.

All fetch/cache failures are swallowed; the seed (or last good) wins and the UI shows a "catalog may be stale" hint.

Troubleshooting

Development

# run the test suite (node --test, no external deps)
npm test
npm run test:verbose

# link into a local DSH web profile for manual testing
dsh plugin --profile web add /path/to/dsh-experts
dsh --profile web web

The bundle is plain ESM (no build). src/client.js is the browser half (ModuleLoader contract); src/host.js is the Node half (HTTP API + catalog source); src/catalog.js is the shared, dependency-free catalog model.

License & security

• License: MIT.
• Security model: the catalog is untrusted input — entries are schema-validated and never executed as code; only display text + a copyable @expert <id> hint reach the UI. No network egress beyond the single catalog.json fetch, no filesystem writes outside the temp-dir cache, no secrets.

Tests

npm test          # runs all suites (node --test, no external deps)
npm run test:verbose

27 tests cover: catalog model (parsing/validation/query/grouping), host route handler (every error path returns structured JSON, never throws), lifecycle (apply() survives a down network / missing services), client half (apply() never throws, degrades gracefully when slots/locale/composer are absent, never imports react in Node), and the client buildInvocationBlock.