DSH Plugin Registry
中文EN
Submit plugin
Plugins/dsh-claude-compat

dsh-claude-compat

Automated evidence available

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.

Author: biedongbin · Development & Runtime · Catalog snapshot: 2026-09-19

Canonical semantic path

Plugin Management & RuntimeCross-Tool Asset Migration

One primary path; alternate capabilities remain separate.
hooks.tool-lifecyclemcp.server-bridgingplugin.marketplace-managementrules.message-injectionsessions.hot-reloadsessions.importskills.export

What it may solve

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.

Imported third-party catalog description; not a Registry verification conclusion.

Sources and public signals

biedongbin/dsh-claude-compat

13 stars · — downloads

Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19

What can currently be confirmed

Active analysis coverage 4/5. Historical chains are retained but do not count toward current coverage.

Analysis complete

Source structure

Conclusion: The source structure check completed without finding a structural issue.

Analysis complete

Repository health

Conclusion: The GitHub repository is reachable and not archived. Public data: 13 stars, 63 commits, 1 forks, and 1 watches; latest commit 2026-09-17.

Analysis complete

npm release

Conclusion: This plugin has no npm package source, so this item does not apply.

Analysis complete

DSH compatibility

Conclusion: Compatibility verification did not pass: the bounded compatibility check did not pass. Test environment: DSH 0.1.6-alpha.2, web profile.

Analysis complete

Dependency audit

Conclusion: The dependency audit did not produce a complete report.

Not analyzed

Functional verification

The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.

Analysis complete

Static risk scan

Conclusion: The bounded static scan found none of its predefined risk signals. This is not proof of safety.

Analysis complete

Package integrity

Conclusion: Package structure or integrity validation did not pass.

Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.

Continue with the latest plugin manager

Describe your task in a DSH conversation and mention dsh-claude-compat. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.

Install or update the plugin manager (latest)