dsh-skills-mcp-manager: Manage Skills and MCP Servers in the DeepSeek Harness Settings Panel

What Does It Do?

It is a DSH plugin for DeepSeek Harness that brings skill and MCP server management into a single settings panel called Skills & MCP. It solves the problem of scattered skill files and hand-edited MCP configuration by letting you list, search, preview, create, rename, delete, and import from one page. The page is organized as two tabs times two levels, with MCP and skills each split into global and project scope, and changes take effect immediately. It is maintained by j62268781-alt under the MIT license.

Core Features

• Skill management: list, search, preview full text, create, rename, and delete, writing //SKILL.md to disk; deletion backs up to a sibling .smp-backup-- directory first so you can restore by renaming it back.
• MCP management: global entries are the real Loader rows in the profile cordis.patch.yml, with add, edit, disable, and delete written back to the config file; project-level entries attach only to agents running in that project.
• MCP import: one-click scanning of user-level or project-level configs from 26 sources including Claude Code, Cursor, VS Code, Gemini, and Codex, with a preview of which files exist, how many were recognized, and which shapes are unsupported before you confirm.
• Two-level separation: switch between global and project in the same page, with a project selector that autocompletes from the workspace registry and also accepts a manually typed absolute path; each level collapses independently and has its own add button.
• Configuration safety: the plugin never throws exceptions outward, and backs up, locks, atomically writes, and re-validates before touching cordis.patch.yml, so DSH does not isolate the whole profile config.
• Zero runtime dependencies: react and yaml are reused from the host, so the plugin ships no third-party runtime dependencies.

How to Use This Plugin?

After enabling it in DSH, open the Skills & MCP page from settings; it shares the same settings slot as the built-in plugins page. Search matches names only, not addresses, arguments, or environment variables, and the project selector decides which project the project-level layer shows.

For MCP, global entries come from config file rows, marked by the "config file" tag on the card; these rows can be edited, disabled, or deleted, and disabling only sets the row's enabled flag to false without removing your configuration. Expanding a card reveals transport, address or command, arguments, environment variables with masked values, scope, and running state. Project-level entries are stored in the plugin's own settings field and mounted by project path when an agent is created.

For skills, the list comes from disk scanning across $DSH_HOME/skills, ~/.agents/skills, and each project's .agents/skills and .dsh/skills, with dsh and agents tags on cards showing which root they came from. When adding a skill, pick global or project scope, and the name doubles as the directory name. Previews read file bodies on demand with a 4KB cap, so bodies never enter the settings document, and renaming moves the directory and rewrites the name in the frontmatter. In-flight operations show progress such as saving, deleting, or switching on the card, other buttons on that card are disabled meanwhile, and failures are reported in place.