DSH Marketplace

dsh-claude-compat

biedongbin/dsh-claude-compat

Bridge Claude Code's .claude/ directories into DSH with zero migration: project and user-level skills, commands, rules (one system-reminder envelope), agent files, hooks (PreToolUse/PostToolUse/UserPromptSubmit/ SessionStart/SessionEnd) and .mcp.json servers, plus Claude Code plugin marketplaces. Ships /cc-plugin for full plugin/marketplace management (claude CLI first, self-implemented fallback), /cc-resume to list and import Claude Code sessions into DSH as native event-sourced logs, and /cc-export to write DSH skills back as Claude Code skills. Two-way Claude Code <-> DSH bridge, versioned and released as dsh-claude-compat.

Install

Add dsh-claude-compat to DeepSeek Harness

Install into

via npm

Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.

via GitHub · npm package

Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.

What happened when we ran it

Installed cleanly when we ran it

Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 4d agoon DeepSeek Harness 0.2.2-rc.1.

Show it in your README

install verified — dshmarketplace

For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.

Due diligence

Before you install dsh-claude-compat

  • Source of record: biedongbin/dsh-claude-compat — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.

Security

What installing dsh-claude-compat runs

Build scripts

No build script was blocked in our run.

Source: our sandbox install on DeepSeek Harness 0.2.2-rc.1, 4d ago.

Install hooks

package.json declares no preinstall, install or postinstall script.

Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.

README mentions

shell commands (bash, exec, spawn …)

Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.

Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.

The AI take

What it is — Directly integrate Claude Code's .claude/ directory into DeepSeek Harness for zero-migration reuse of skills, commands, and rules.

Who it is for — When developing a project that follows Claude Code conventions in a specific DeepSeek Harness profile containing .claude/skills/, .claude/commands/, and .claude/rules/ directories, the plugin enables direct invocation of those skills and commands. If your workflow relies only on DeepSeek Harness's built-in skills and rules without needing to bridge external directories, you do not need this plugin.

Watch out — Sandbox test passed with successful installation and registration in a new profile. The static check noted execution of shell commands, which is a prompt rather than a defect. No other issues identified.

The verdict — I would install it because it provides a direct channel for integrating Claude Code configurations into DeepSeek Harness, but only if the project follows the .claude/ directory structure; otherwise, DeepSeek Harness's native tools suffice.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

What dsh-claude-compat does

Project and home files split into skill cards and injected rule messages.

dsh-claude-compat is a DeepSeek Harness plugin that makes Claude Code conventions available from a project’s .claude/ directory and the user-level ~/.claude/ directory. It registers skills/**/SKILL.md and commands/*.md through a DSH skill provider: names and descriptions appear in the model-visible catalogue, while bodies load on demand through the skill tool. Markdown command files are also available as slash commands such as /command-name. Files in rules/ use a different path: their contents are concatenated, wrapped in <system-reminder>, and prepended as a user-role message to the message array once per session.

The plugin reads these files; the README does not describe writing or modifying them. Project entries take precedence over DSH-native and ~/.claude/ entries, while DSH-native entries take precedence over user-level copies. Project rules are cached per session working directory, and changes take effect in the next session. enableSkills, enableRules, rulesMaxBytes, userRulesMaxBytes and project-root discovery can be configured.

dsh-claude-compat is intended for projects that already use .claude/skills/, .claude/commands/ or .claude/rules/, and requires DSH with a profile. It is a poor fit when these conventions are not used, or when DSH’s built-in dsh-agent-instructions is sufficient for CLAUDE.md and AGENTS.md, which this plugin deliberately does not touch. Its terminal-surface risk is its access to project and home-directory .claude files: rules are injected verbatim as model instructions, so only trusted content should be placed there.

dsh-claude-compat documentation

How it behaves

dsh-claude-compat discovers a project root using the markers in projectRootMarkers, whose default is [".git"]. It reads .claude/skills/**/SKILL.md, .claude/commands/*.md, and .claude/rules/*.md, plus the corresponding paths under userClaudeDir, defaulting to ~/.claude.

Skills and commands are exposed through the DSH skill provider. A skill’s name and description enter the model-visible catalogue, and its body is fetched when the model uses the skill tool. Command files also appear in the slash menu. Nested skill directories are flattened, such as gitnexus/gitnexus-guide becoming gitnexus-gitnexus-guide; invalid frontmatter names fall back to the directory name. DSH requires kebab-case skill names.

Rules are concatenated and injected verbatim inside a <system-reminder> envelope as a user-role message at the front of the message array once per session. Project and user rules with the same basename are deduplicated in favour of the project file. CLAUDE.md and AGENTS.md are not read by this plugin.

Configuration

Key Default Purpose
enableSkills true Enables the skills and commands provider
enableRules true Enables rule injection
rulesMaxBytes 65536 Caps project rule text
userRulesMaxBytes 65536 Caps ~/.claude/rules text
projectRootMarkers [".git"] Project-root discovery markers
skillRank 50 Rank for project skills
skillSource project-claude Project catalogue source tag
userSkillRank 700 Rank for user skills
userSkillSource user-claude User catalogue source tag
userClaudeDir ~/.claude User-level Claude directory

Project entries use rank 50, DSH bundled skills use 600, and user entries use 700; lower rank wins.

Requirements and session timing

The README requires DSH with a profile, such as web, and a project using Claude Code directory conventions. All three directory types are optional. Skills are reconciled into the catalogue without a restart, while rules are read for each new session and cached per session working directory. Editing a rule during a session therefore affects the next session.

Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub

Same category

Alternatives to dsh-claude-compat

7.0k

One repository, three parts: a runtime injector for DSH plugin packages (inject, hot-reload, unload, promote a dev staging tool to the front, route self-heal, plus a settings-page plugin manager that lists, unloads and drags folders in to internalize), a task-aware reasoning-mode router agent preset (router-standard / router-spec / router-react), and a graded two-level task protocol whose six tools (commit_star, lock_stage, revise_do, edit_plan, mark_task, redteam_verdict) pin task state to disk. The injector implementation ships in-tree, so the install carries its own behaviour rather than a dependency list.

Installs, but needs a build approved first

GitHub sourceJavaScript1mo ago

AI review

dsh-routing-suite

What it is — A DSH suite that ships a runtime injector, task-aware reasoning-mode presets, and a graded two-level protocol whose six tools pin task state to disk.

Who it is for — You are on DSH 0.1 preview with DeepSeek Pro or Flash, running spec-then-execute work that needs the agent to switch reasoning modes by task and to write stage state to disk. Skip it when your DSH is already outside >=0.1.0-rc.6 <0.2.0; the preview still breaks APIs, so the version window is the constraint, not the job type.

Watch out — In our run the install started, then pnpm blocked the build script and DSH never finished registration. Until that build is allowed by hand, the plugin does not actually land.

The verdict — I'll take it only after unlocking the blocked build: the injector ships in-tree, so that allow step is how you accept this runtime's behaviour rather than a dependency list.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Source

mirage

strukto-ai

3.7k

Swaps the filesystem and bash providers for a mirage virtual workspace: file tools and shell commands run over mounted resources (RAM, S3, Redis, Slack, Gmail, Notion, Postgres) instead of the host disk, with per-mount read/write/exec modes, per-command sandbox routing (monty, pyodide, quickjs in process; docker, e2b, daytona remote), and installed CLIs (git, gh, slack, linear, ntn, gws, or one you register) as head words in the virtual terminal.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourceTypeScript24d ago

AI review

mirage

What it is — mirage provides a unified virtual filesystem for AI agents, allowing bash tools to operate across mounted resources.

Who it is for — It is suitable for AI agents that use bash tools and need to access multiple backends such as S3 and Slack at the same time. It is not suitable for agents that only run on local filesystems without remote mounted services.

Watch out — No obvious issues found. There is a static check prompt indicating it will execute shell commands. Sandbox testing was not performed.

The verdict — I would not install it because sandbox testing was not performed.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details

oh-my-agent

first-fluke

1.4k

Runs project OMA checks before and after tool execution and when a turn tries to finish. Installs its OMA CLI dependency and initializes unconfigured projects on first use. Requires Node.js 22+; initial setup needs network access and project write access.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourceTypeScript24d ago

AI review

oh-my-agent

What it is — oh-my-agent runs project OMA checks before and after tool execution and when a turn tries to finish, installing its OMA CLI dependency and initializing unconfigured projects on first use.

Who it is for — It fits users who need to run project checks before and after tool execution and when a turn tries to finish, as well as project initialization on first use. Users who avoid network access and project write permissions during setup can choose not to install it.

Watch out — Initial setup requires network access and project write access. It executes shell commands. Sandbox testing has not been performed, no obvious pitfalls found.

The verdict — I won't install it because it requires network access and project write access during initial setup and has no sandbox testing.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source
386

Manages local DeepSeek Harness skills in Settings and shows shared Agent skills as read-only.

Installed cleanly when we ran it

npm packageJavaScript19d ago

AI review

dsh-skills-manager

What it is — Manages local DeepSeek Harness skills in Settings and displays shared Agent skills as read-only.

Who it is for — Users who need to manage local and project skills across multiple tools in DeepSeek Harness setups would use this plugin. Users who only rely on shared agent skills without local or project management do not need it.

Watch out — Passed sandbox test: installed in a new profile and registered by Harness. No obvious issues found. Compatible with DeepSeek Harness 0.2.x series.

The verdict — I would install it because it supports incremental updates from public GitHub repositories with backup restoration.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Details

oh-dsh

hust-open-atom-club

323

Community distribution: TUI, desktop, and Web UI as one bundle with layered installation.

GitHub sourceTypeScript2mo ago

pi2dsh

weijiafu14

212

Pi Host ABI compatibility engine: after one install, unmodified Pi extensions from npm mount as native DSH plugins with `dsh plugin add <pi-package>`. Verified end to end on stock DSH with pi-mcp-adapter (full MCP manager: OAuth, resources, prompts, MCP Apps, elicitation, sampling), @tintinweb/pi-subagents, pi-code, pi-hermes-memory and pi-background-tasks; `pi2dsh inspect` reports a package's compatibility before installing.

DeepSeek Harness 0.2.2-rc.1 refuses the latest release

npm packageTypeScript21d ago

AI review

pi2dsh

What it is — pi2dsh is a Pi host ABI compatibility engine that mounts unmodified Pi npm packages as native DSH plugins on DeepSeek Harness.

Who it is for — Pi plugin developers who want to run their npm packages unmodified on DeepSeek Harness should install it. Developers who are not involved in Pi plugin development do not need to install it.

Watch out — It was tested successfully in a new profile and registered into the profile. A restart of DeepSeek Harness is required. Installation may require manually approving build scripts if pnpm blocks them.

The verdict — I would install it if I need Pi ecosystem plugins on DeepSeek Harness because it provides unmodified compatibility.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source