Plugin directory / Developer / dsh-claude-marketplace
dsh-claude-marketplace
Verified · install-tested on dsh ben7am1n
What it does
Claude Code marketplace compatibility for DeepSeek Harness
Works — verified, early-stage project
Claude Code marketplace compatibility for DeepSeek Harness It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
dsh-claude-marketplace
Claude Code compatibility layer for DeepSeek Harness: load Claude Code skills, commands and agents — from a project's .claude directory or from Claude Code marketplaces — as native dsh skills.
This is the ecosystem bridge: install any Claude Code plugin once and its components become callable dsh skills (prefixed cc-), reusing the huge Claude Code plugin/skills ecosystem inside DeepSeek Harness.
Install
dsh plugin --profile <name> add dsh-claude-marketplace
Usage
Ask the model to use the cc_* tools, or drive them directly:
| Tool | Purpose |
|---|---|
cc_scan |
Scan <project>/.claude + installed plugins; register every component as a dsh skill |
cc_marketplace_add |
Register a marketplace (local path, owner/repo[#ref], or git URL) |
cc_marketplace_list |
List registered marketplaces and their plugins |
cc_plugin_install |
Install a plugin and register its skills/commands/agents |
cc_plugin_list |
List installed plugins |
Example flow:
cc_marketplace_add("anthropics/claude-code")
cc_marketplace_list()
cc_plugin_install(plugin="commit-commands", marketplace="claude-code-plugins")
cc_scan()
Imported components are named cc-<plugin>-<component> (kebab-case, matching dsh's skill name contract), so they can never collide with native dsh skills. Original names are preserved in the label field (my-plugin:review).
What is supported (v0.1)
- Skills —
skills/<name>/SKILL.md, plugin-rootSKILL.md - Commands —
commands/*.md(flat, loaded as skills) - Agents —
agents/**/*.md(loaded as skills with a delegation header) - Marketplaces —
.claude-plugin/marketplace.jsonwith sources: relative path,github,url,git-subdir,npm,archive - Local
.claude— project-level skills/commands/agents (project trust)
Not yet (v0.2+)
- Hooks — parsed but not executed (security: hooks are arbitrary code; an opt-in policy is planned)
- MCP / LSP servers — use dsh's native MCP client instead
- Themes / monitors / workflows / output styles
allowed-tools,model,effortfrontmatter semantics (documented, ignored for now)- Auto-refresh of the skill catalog on file changes (run
cc_scanmanually)
Configuration
| Field | Default | Meaning |
|---|---|---|
cacheDir |
~/.dsh/claude-plugins |
Cache root for marketplaces and installed plugins |
skillPrefix |
cc |
Prefix for imported dsh skill names |
Security
Installed plugins are copied into the cache (never referenced in place). Hooks are not executed in v0.1. Path traversal in marketplace relative sources is rejected. Review plugin sources before installing, exactly as you would for Claude Code itself.
License
MIT
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalogThen say "install dsh-claude-marketplace for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
Web profile:
dsh plugin --profile web add dsh-claude-marketplaceHeadless (CLI) profile:
dsh plugin --profile headless add dsh-claude-marketplacePackage
npm: dsh-claude-marketplace · version 0.1.0 · tested on dsh 0.1.0-rc.6
Test report
Verified end-to-end: L1 install + L2 load + L3 runtime Q&A on dsh 0.1.0-rc.6.
When to use it
Extend the agent's coding surface — give it a new tool, workflow, or integration so it handles a dev task it couldn't before.
Who it's for
Developers who want dsh to behave like a teammate on real codebases — editing, running, and verifying changes rather than just answering.
For developers — extending it
The tool/command surface is the seam: expose more of the SDK, add smarter context wiring, or tighten the loop between code changes and verification.
Share this badge
Drop this badge into your README — it links back here and updates automatically when our test status changes:
[](https://dshbase.com/plugins/dsh-claude-marketplace/)<a href="https://dshbase.com/plugins/dsh-claude-marketplace/"><img src="https://dshbase.com/badges/dsh-claude-marketplace.svg" alt="dshbase install-tested"></a>