echocat-skill-panel-3.0: A Skill Audit and Install Panel for DeepSeek Harness

What Does It Do?

Echocat Skill Panel 3.0 is a DSH plugin for DeepSeek Harness that audits which skills each conversation turn actually used and lets you install or remove them inside the app. Instead of trusting the model to report itself, it derives the used skills from the session event stream, so automatic calls, manual /name calls, and turns with no skill at all are all reported accurately. Maintained by VDERR under the MIT license, it ships three interfaces that share one data source.

Core Features

• Skill call auditing: derives the skills used in each turn from session events, so a silent model still gets reported.
• In-app install and removal: manage skills from the panel, with same-name installs backed up before replacement and deletions moved to a backup directory rather than hard-deleted.
• One-click reference: the bar above the input box is the only place that can reference a skill, appending /name to your draft so Enter triggers a manual call.
• Flexible install sources: accepts repository pages, folder links, SKILL.md links, zip URLs, owner/repo, and SSH addresses, plus uploaded files or a pasted SKILL.md.
• Chinese display and auto-translation: a skill's own meta.yaml carries its Chinese name, and skills without one are translated and cached automatically.
• Read-only fallback and notifications: the panel turns read-only with an explanation when the host forbids writes, and a native notification fires after each turn.

How to Use This Plugin?

After enabling it in DSH Desktop Beta, a persistent bar appears above the input box; open it to see the current turn's skill report and the skill catalog. To add a skill, paste the whole address into the install entry and the host decides whether to clone or download, parsing branch and subdirectory from the address itself. The success prompt after installing carries the same reference button, so the skill is usable immediately. Edit a card any time to set or clear its Chinese name. Because the host half is snapshotted into memory at boot, restart the app after host-side changes, while client-only changes just need a page refresh.

How to Troubleshoot This Plugin?

If the app fails to start, it is usually tied to the hard constraints of the install script, so check them one by one against the official install notes. If the panel shows as read-only, the host is refusing writes and the plugin states the reason alongside it. If the build artifact and the package disagree, the install verification gate fails, and the client bundle must be rebuilt in the same commit as required by the README.