yanglaofish/dsh-skill-manager

dsh-skill-manager is a native plugin for DeepSeek Harness (DSH) that provides a unified management plane for agent skills, which are Markdown files with YAML frontmatter packaged as directories containing a SKILL.md. It organizes skills into a strict three-layer model: a library at ~/.dsh/skill-manager/library/ that only stores skills and is never scanned by the engine, a workspace layer at <project-root>/.dsh/skills/ whose directory entries (symlinks or copies) are the sole enable switch and the only source the engine actually reads, and a session layer stored in JSON that defaults to the workspace whitelist but allows free selection from the entire library. Installation is performed through dsh plugin --profile web add @yanglaofish/dsh-skill-manager (npm) or dsh plugin --profile web add github:yanglaofish/dsh-skill-manager (GitHub), after which running dsh web exposes the management UI; the package itself is a DSH bundle shipped through a bundle-manifest and a cordis.patch.yml, confirming DSH-native packaging rather than cross-agent compatibility.

Typical workflow: the operator launches dsh web, opens Settings → Skill Manager, and uses the "Global Skills" tab to view, edit, or import skills (zip ≤50MB, extracted ≤100MB, folder batches supported) while the "Workspace Skills" tab toggles per-project enablement from a dropdown that auto-locates the current session's workspace; the session panel offers a third override layer with a "return to follow" reset. From the conversation side, the user can ask the agent things like "list my skills" or "enable markdown-formatter in this workspace" and the agent invokes any of 13 skill_manager_* tools registered by the plugin. Since v4.2, the /view endpoint calls the native ctx.skills.list({ cwd }) to validate what the engine actually loaded, flagging workspace-enabled skills as missing (red corner) or shadowed when another source overrides them; other Cordis plugins can inject: ['skillManager'] to call 17 host-side service-facade methods without going through HTTP.

The host side is plain native ESM and the client bundle is hand-written react.createElement, requiring no JSX, TypeScript, or bundler; the README explicitly confirms cross-platform deployment on Windows, Linux, and macOS since v4.0, with Windows cross-drive symlinks automatically degrading to full fs.cp directory copies. Safety gates include an isValidIdentifier whitelist for skill names and session IDs, an assertRegisteredWorkspace check that restricts writes to registered workspaces, 2MB HTTP body and 50MB/100MB zip limits, UTF-8 BOM stripping in parseSkillDoc, and a v4.3 browser-trust fence (loopback-only host binding plus sec-fetch-site: cross-site rejection and same-origin Origin enforcement mirroring dsh-client-connection's isTrustedApiRequest). Development uses node --check for syntax plus 165 isolated unit tests under a temporary DSH_HOME; license is MIT.