dsh-claude-compat

Name: biedongbin/dsh-claude-compat
Author: biedongbin

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.

111JavaScriptMITSource 开源推广 · .claude/ 目录桥接

Install

Add dsh-claude-compat to DeepSeek Harness

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 8d ago.

Show it in your README

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.
Detected: terminal surface. Read the source before granting these.
A listing here is not a security review. 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

dsh-routing-suite

yjh051108

7.2k

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 sourceJavaScript26d ago

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 sourceTypeScript2d ago

1Details

oh-dsh

hust-open-atom-club

325

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

Installed cleanly when we ran it

GitHub sourceTypeScript18d ago

1Details

pi2dsh

weijiafu14

185

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.

Installed cleanly when we ran it

npm packageTypeScript1mo ago

1Source

dsh-undo-savepoint

lire1131

153

Undo/redo & rollback system for DSH: every config change is auto-snapshotted; undo/redo/restore to any version from the WebUI or the offline CLI/GUI tools (works even when DSH fails to boot).

Installed cleanly when we ran it

npm packageJavaScript20d ago

1Source

dsh-skill-mcp-panel

Fishquito7

146

Manages DSH skills and MCP servers from the web settings: skill cards with hot enable/disable, workspace scopes, groups, batch migration and drag-and-drop import, plus stdio/HTTP MCP CRUD with connection tests, secret redaction and the unified dsh-panel CLI.

Installed cleanly when we ran it

npm packageJavaScript10d ago

1Source