DSH Plugin Registry

DeepSeek Harness Plugin Directory

Search and compare installable DeepSeek Harness plugins across the full DSH Plugin Registry. Filter by category, plugin type, verification status, and repository activity.

2477plugins
Page 96 of 104
View plugin dsh-solo-thinking

dsh-solo-thinking

fredalxin/dsh-solo-thinking

23GitHub stars
Manifest Valid

DeepSeek Harness plugin for isolated brainstorm branches, agent-authored Handoffs, and a persistent visual thinking tree.

DSH Profile: webv0.1.19MIT
View plugin
View plugin dsh-teacher

dsh-teacher

Yihong89/dsh-teacher

3GitHub stars
Manifest Valid

A DeepSeek Harness Socratic tutoring plugin that turns Markdown question sets into guided practice, quizzes, gap tracking, and spaced retests.

DSH Profile: webv0.3.0MIT
View plugin

About the DeepSeek Harness Plugin Directory

The DSH Plugin Registry organizes installable community plugins for DeepSeek Harness into a searchable directory. Browse plugins by capability, plugin type, verification status, repository activity, and category while keeping the source repository visible for every entry. Each registry page connects plugin discovery with install information, source-backed capability analysis, security signals, compatibility evidence, and other facts that help users evaluate an extension before installing it.

How Plugins Enter the Registry

DSH Plugin discovers projects from the public DeepSeek Harness plugin ecosystem and community submissions. A repository is not treated as an installable plugin simply because it uses the dsh-plugin topic. Registry classification checks source evidence, package and bundle metadata, install information, and plugin identity before a project is published as a plugin or plugin bundle. This keeps the directory focused on usable DeepSeek Harness extensions instead of mixing plugins with unrelated repositories, tutorials, SDKs, wrappers, or other resources.

How to Choose a DSH Plugin

Start with the capability you need, then check the plugin's target DSH profile, source repository, recent activity, license, install path, and documented limitations. Security Signals surface dependencies, lifecycle scripts, manifests, and other source facts. Compatibility Evidence records version-specific runtime results and clearly distinguishes tested and untested combinations. These signals make comparison easier, but third-party plugin code should still be reviewed before installation.