` | One row per conversation in the session table `~/.dsh/S-M-C/contexts.json` |
| Scope | **Global**: every conversation, every workspace, sub-agents included | **This conversation only** |
| Maintained by | The "enable / disable" button on the skills tab | The session default, the sidebar panel, and the model's own `skill_select` |
| Seen by | dsh's own filesystem scan | This plugin's conversation injection |
**How a conversation stores its choice**: the file keeps the **difference from the default** (`overrides: { on, off }`), and the effective set is `default โช on \ off`. Editing the default therefore reaches every conversation that never configured itself, while a skill you turned off in one conversation stays off.
## ๐ค Two tools for the agent
| Tool | What it does |
|---|---|
| `skill_select` | Enable or disable one skill for **this conversation**; writes the conversation's own difference and applies immediately. Accepts every linked row โ container directories too (their DESCRIPTION.md is the loadable body). |
| `skill_query` | **Read-only** view of the skills visible in this workspace (name / description / group / linked? / injected in this conversation?), computed at call time, with keyword and group filters. |
The skill catalog itself is also served by this plugin (**shadow catalog**): the catalog the AI sees is generated here and carries one extra line, `smc-skill-index` โ an **index skill** whose body is the complete list of this workspace's skills in the catalog's own shape. Skills that are not injected cannot be loaded ("not enabled in this conversation"); the `/skill-name` gesture is unaffected.
The guide tab can also switch on **announce to agent**, which describes the plugin and the current state of all three tool families in every agent's system prompt โ
Announce to agent: expanded, it declares the plugin's capabilities; the setting persists in the dsh-s-m-c-center namespace and applies immediately.
## ๐งฑ Architecture
**Mounting and the dual-face structure** โ the plugin is one npm package plus one profile bundle patch; dsh source is untouched:
The host half registers routes, announces to agents and connects MCP for real; the client half only provides the settings page. They talk over /api/dsh-s-m-c-center/*.
**Store layout** โ every artefact lives under `~/.dsh/S-M-C`, while the two directories dsh scans deliberately stay outside it (the plugin only injects and removes junctions there):
A skill's canonical copy always lives in the store; the entry under ~/.dsh/skills is only a junction pointing at it.
**What the three switches really do on disk** โ not a config field, but files and connections that actually move:
Skills: create/remove a junction. MCP activate/archive: the definition moves between mcp.json and mcp-archive.json. CLI: visibility only.
## ๐ Install
> **Requirements**: DeepSeek Harness **`>= 0.1.2-alpha.2`** (all `@deepseek-ai/*` packages release together); Node `^22.19.0 || >=24`.
> Status: **fully tested on `0.1.6-alpha.1`, `0.1.6-alpha.2` and `0.1.5-rc.2`**; every API used has been checked for existence and signature since `0.1.2-alpha.2`.
> **Install it as a normal package โ never as a junction.** A junction breaks resolution of dependencies (`schemastery` / `react` and friends) and makes the package name disagree with `cordis.patch.yml`; either one stops DSH from starting.
```sh
# From npm
dsh plugin --profile web add dsh-s-m-c-center
# or: npm install dsh-s-m-c-center
# From source (this repository / after cloning)
dsh plugin --profile web add
# Or from a packed tarball
dsh plugin --profile web add /dsh-s-m-c-center-0.2.0.tgz
# Or the one-shot scripts
bash scripts/install.sh # macOS / Linux / Git Bash
powershell -ExecutionPolicy Bypass -File scripts/install.ps1 # Windows
```
After the first install, **restart DSH and hard-refresh the browser** (Cmd/Ctrl+Shift+R), then open "Settings โ Web UI plugins โ **Tool manager**".
> **Upgrading**: for UI-only changes, overwrite the files and hard-refresh. Changes on the host side (routes / engines / tools) need one DSH process restart.
## โ๏ธ Configuration
```yaml
# The plugin's own settings namespace (dsh settings)
dsh-s-m-c-center:
enabled: true # master switch (routes, MCP connections, CLI probing)
announceToAgent: true # describe the plugin in every agent's system prompt
```
Runtime state:
- **Unified external store**: `~/.dsh/S-M-C/` (**S**kills / **M**CP / **C**LI) โ `skills/` (canonical copies plus `index.json` manifest), `skills-links.json` (junction ledger), `skills-registry.json` (registered external skills), `mcp.json`, `mcp-archive.json`, `cli.json`. The old locations are migrated in on first start; the whole store can move elsewhere with `DSH_STORE_ROOT` (the plugin rebuilds the junctions).
- **Conversation selections**: one table for the whole machine at `~/.dsh/S-M-C/contexts.json` โ `default` is the session default and `sessions.` holds that conversation's difference from it (`on` / `off`). **No workspace is involved**: the key is the session id, so the settings page and the sidebar read the same document. An older version kept one file per workspace; those are folded in once, on the first mount with the table missing.
- MCP: active definitions in `S-M-C/mcp.json`, archived ones in `S-M-C/mcp-archive.json` (credentials and headers are stored in plain text โ keep both files `0600`).
- CLI registry: `S-M-C/cli.json`.
## ๐ Permissions and dependency disclosure
The plugin runs with the DSH process's privileges and uses four kinds of capability โ files, network, commands and credentials:
| Capability | What it does | Scope and limits |
|---|---|---|
| **Files** | Reads and writes the store `~/.dsh/S-M-C/**`; creates / removes directory junctions in the skill roots; reads and writes the session table `~/.dsh/S-M-C/contexts.json` (plus any legacy `/.dsh/S-M-C/contexts/*.json`, read once by the import); reads `SKILL.md` and skill-embedded scripts | Only the store and the four skill roots dsh scans; in-place skills only get their frontmatter rewritten; no other paths are read or written |
| **Network** | Connects to the MCP servers the user configured (stdio through a subprocess, streamable-http over HTTP) | Only the addresses typed into the manager page; the plugin has **no** built-in external service, **no** telemetry, and reports nothing anywhere |
| **Commands** | Probes local CLI tools: runs their `--help` / `--version` or the command declared in `cli-state` | Only commands inside the registry and visible on the manager page; nothing the user did not register is executed |
| **Credentials** | Stores MCP env / headers / API keys, reads CLI `cli-state` | Plain text under `~/.dsh/S-M-C/*.json`, local only, never sent out; keep those files at `0600` |
**External dependencies**: the only runtime dependency is `schemastery` (settings validation); `@deepseek-ai/*` and `react` are peer dependencies provided by DSH; no native modules, and **no** postinstall / prepare lifecycle scripts.
**Failure boundaries**: a failed scan or route degrades to an empty list and a placeholder; a failed migration is recorded in `failures` and ignored, never blocking DSH startup; a failed MCP connection only changes the status line and touches no files; a failed conversation injection never vetoes the conversation and only explains itself in the log. None of them can stop DSH from starting.
**Known risks**: skill deletion is physical and irreversible (and **only the store's copy is ever deleted**: a `native` skill must be migrated into the store first, a `registered` one is unregistered, and "delete junction" only unlinks and never touches its target); MCP credentials are stored in plain text; enabling / disabling a skill works through a directory junction, so moving the store by hand breaks the junctions (use `DSH_STORE_ROOT` instead and the plugin rebuilds them).
๐๏ธ Expand repository layout
```text
dsh-s-m-c-center/
โโโ src/
โ โโโ index.ts # host composition root (mount, settings, announcement, tools)
โ โโโ routes.ts # route assembly (one entry per feature)
โ โโโ setup.ts # identity constants + the agent-facing guidance text
โ โโโ shared/ # cross-cutting primitives: paths / fs-utils / frontmatter / http / protocol
โ โโโ features/ # vertical slices, each owning manager + routes + index barrel
โ โ โโโ skills/ # roots / scanner / linking / links / registry /
โ โ โ # adopt / delete / migration / store-index / catalog
โ โ โโโ mcp/ # document / manager / routes
โ โ โโโ cli/ # probe / registry / manager / routes
โ โ โโโ context/ # engine / apply / tools / routes
โ โ โโโ announce/ # system-prompt announcement
โ โ โโโ settings/ # the plugin's settings namespace
โ โโโ client/ # browser half
โ โโโ shell/ # settings-card shell, sidebar "conversation skills" panel
โ โโโ shared/ # api / ui / locales (zh+en) / format / css module
โ โโโ features/ # one panel + hook per tab
โโโ lib/ # build output (host index.js; client client.js; types/*)
โโโ tests/ # vitest (13 files)
โโโ cordis.patch.yml # DSH bundle patch (package name must match package.json)
โโโ dsh.plugin.json # DSH plugin manifest (id / version / main / client.main)
โโโ package.json # npm package (dsh.bundle.patch + dsh.client + compatibility)
โโโ LICENSE # MIT
โโโ README.md / README.zh.md
โโโ docs/
โ โโโ ๅ่ฝไป็ป.md / ๆถๆ.md / development.md
โ โโโ arch-*.svg # architecture diagrams (referenced above)
โ โโโ social-preview.png # repository social preview
โ โโโ shots/ # UI screenshots (referenced above)
โโโ scripts/install.* # one-shot installers into a DSH profile
```
## ๐งฐ Development
See [`docs/development.md`](./docs/development.md): dual-half builds (`tsdown` rebuilds `lib/index.js` + `lib/client.js`), type checking (`tsc --noEmit`) and the test suite (`vitest`, 13 files / 193 cases).
## ๐ License
[MIT](./LICENSE).
---
*ไธญๆ๏ผ[`README.zh.md`](./README.zh.md).*
| 
|
| **CLI tools** ๏ฝ discover / probe / register local CLIs | **Guide** ๏ฝ how the three kinds work + uninstall escape hatch |
| 
| 
|
