Skip to main content

dsh-skin-market

55Stars6Forks2Issues0Watchers

A skin marketplace embedded in the settings page for DSH Web, enabling one-click browsing, installing, activating, updating, and uninstalling of community skins.

Evidence5/5methodologySourceInstallMaintenanceDSH versionSecurity scan
Machine-auditedInstall commandRepo verifieddsh-plugin topicLicenseREADMEAI wiki
Language
TypeScript
License
MIT
Branch
main
deepseek-harnessdsh-pluginplugin-marketskin-marketthemes

Install

cmdweb profile
$ dsh plugin --profile web add dsh-skin-market

Run the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial

Install via your agent

Install the DeepSeek Harness plugin kingOfSoySauce/dsh-skin-market for me: review the repository at https://github.com/kingOfSoySauce/dsh-skin-market first, then run the install command and verify the plugin loads successfully.

Paste this instruction to the DSH Web GUI assistant — it will install and verify for you.

One-Line Description

dsh-skin-market is a "Skin Market" embedded in the DSH Web settings page, allowing you to browse, install, activate, deactivate, pin, update, and uninstall community skin plugins like an app store. The installation source is pinned to a specific commit, and failures automatically rollback the profile file, minimizing the risks associated with appearance changes.

Core Capabilities

  • Browse the community skin catalog with search/sort by name, tag, light/dark mode
  • One-click install, activate, deactivate, pin, update, and uninstall skins within the DSH settings page
  • Silently fetch the latest catalog from GitHub Pages every 5 minutes, falling back to cache or built-in catalog when offline
  • Display download progress, speed, and real-time stages during skin installation/update, with cancelable operations
  • Provide in-page updates for the skin market itself (no DSH restart required to detect new versions)
  • Auto-restore snapshots of profile's package.json, cordis.patch.yml, workspace, and lockfile when install/activate fails

Technical Implementation

  • Language: TypeScript (with client-side React 18)
  • Key Dependencies: @deepseek-ai/cordis (peerDependencies, DSH host framework), @deepseek-ai/dsh-client-ui-primitives (client UI primitives), yaml (read/write cordis.patch.yml), ajv (catalog schema validation)
  • Architecture Pattern: Injects webServer/loader/agents services via Cordis, registers a set of HTTP routes (/dsh-skin-market/...); client injects into settings page's settings.section slot via slots; actual pnpm install/uninstall via child_process calling dsh plugin subcommand
  • Entry Points: src/index.ts (Host side), src/client/index.ts (Client side, injects settings slot)

Use Cases

For users who want to change the DSH Web appearance but don't want to manually copy repositories, edit cordis.patch.yml, or run pnpm commands. Also for users who have installed multiple third-party skins and want unified management, or want to trial several skins before deciding which to keep. If you only install one skin and won't adjust it later, you can directly install a single skin plugin without using this market.

Prerequisites & Compatibility

DependencyMinimum VersionDescription
DSH Web0.1.0-rc.6Both README and catalog's compatibility field point to this version; DSH uses pnpm to manage profile dependencies
Node.js22 or higherStated in README "Local Development" section; source uses ESM and built-in modules like node:crypto/node:fs
PlatformmacOS / Windows / LinuxSubcommand calls via dsh plugin --profile <name>, no OS/CPU restrictions declared; on Windows, pnpm.cmd needs to be in PATH alongside pnpm
Native ModulesNoneAll dependencies are JS/YAML processing, no native bindings

Installation

dsh plugin --profile web add github:kingOfSoySauce/dsh-skin-market

Configuration Options

ConfigTypeDescriptionDefault
profilestringWhich DSH profile to operate on (reads from --profile CLI arg if not passed, falls back to web)web
DSH_SKIN_MARKET_LOCAL_CATALOGenv varWhen set to 1, only uses plugin's built-in data/catalog.json, skips remote fetch; for local entry debuggingunset
DSH_HOMEenv varOverrides DSH user directory location; profile path resolution joins it with profiles/<name>~/.dsh

Note: Each skin in the catalog may declare its own compatibility.dsh and install.allowBuild, but these are catalog entry-level attributes, not plugin runtime configuration.

FAQ

Q: What preparation is needed before installing dsh-skin-market?

A: It's recommended to close other skin-related plugins first to avoid conflicts. DSH uses pnpm to manage profile dependencies, so ensure pnpm is in PATH. Local development requires Node.js 22 or higher.

Q: Can skin market installation, update, or uninstallation fail?

A: It won't modify your real profile. Before each operation, it snapshots package.json, cordis.patch.yml, pnpm-workspace.yaml, and pnpm-lock.yaml; on error, it atomically restores and cleans up half-installed states; when encountering pnpm allowBuilds approval, it only writes necessary keys to the corresponding fields.

Q: How are skins in the list obtained? Does the plugin need manual updates each time?

A: No, the market silently validates the remote catalog JSON from GitHub Pages every 5 minutes or when the window regains focus. After validation passes, it writes to the profile's IndexedDB cache; offline or timeout falls back to cache, then to the plugin's built-in catalog.

Q: Why pin to a full commit instead of a branch?

A: Each skin target in the catalog is in the form github:<owner>/<repo>#<40-char commit>, optionally with a &path: subdirectory. Pinning to commit avoids subsequent main branch commits from accidentally overwriting already-captured versions, and the skin detail page can precisely display the source.

Q: What operations does the skin market support? What's the workflow?

A: It supports seven lifecycle operations: install / activate / deactivate / pin (stay active) / unpin / update / uninstall. Each skin can be installed, used, and pinned; before uninstall, if still in use, it automatically deactivates and restores the default appearance, then deletes the package.

Q: Does the skin market actively create GitHub PRs or read private files?

A: No. The browser can only submit skinId from the catalog, cannot submit arbitrary commands or installation addresses; the catalog submission process only goes through PRs in the maintainer's local fork, and explicitly states it doesn't read .env, credentials, chat records, or private files outside the workspace.

Q: No interface change after install or activate. What to do?

A: Most skins require DSH Web restart to take effect. Settings → Skin Market → Select skin → Click "Use" → "Restart DSH". If agents are still running during restart, they will be waited for until idle before safe restart.

Q: How to recover when the page is unresponsive due to skin conflicts?

A: First stop the DSH process, execute ~/.dsh/profiles/web/node_modules/.bin/dsh-skin-market-reset --profile web, which will turn off all skins managed by the market while preserving package files; then restart DSH. The command uses atomic writes and rolls back on failure.

Difficulty Level

Beginner — Users only need to click buttons in the settings page, no manual profile editing required; one-click restore command is also provided for conflicts, no need to understand Cordis or pnpm internals.

Known Issues & Limitations

  • Hard timeout for single pnpm subcommand is 10 minutes; large GitHub package downloads may trigger "plugin download timeout" prompt (src/commands.ts:30, src/commands.ts:132-139)
  • Catalog requires remote generatedAt to be strictly >= locally accepted version; if remote catalog is rolled back to older timestamp, it's treated as invalid and old catalog is retained (src/catalog.ts:140-143)
  • Skin market extends pnpm download timeout via .npmrc's fetch-timeout=600000; this is to work around pnpm 11 treating --config.fetchTimeout as string causing errors (src/lifecycle.ts:117-118)
  • Only verified on DSH Web 0.1.0-rc.6; README explicitly states this combination passed 132 catalog validations, 70 automated tests, and 5-minute silent update test, but doesn't imply all third-party skins in the catalog have undergone the same level of review (README.md:182-190)
  • Lifecycle operations like install, activate, deactivate can only run one at a time; concurrent requests are rejected (src/lifecycle.ts:241)

Read the usage guide →

Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.

Listing badge

Listed on deepseek-plugin.org
[![Listed on deepseek-plugin.org](https://img.shields.io/badge/listed_on-deepseek--plugin.org-007EC6)](https://deepseek-plugin.org/plugins/kingOfSoySauce/dsh-skin-market)

Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.

← Back to plugin directory