mrkeyoor.comAsk

VDERR/echocat-skill-panel-3.0tested 05 Oct 2026commit 1f98da6

dsh-echocat-skill-panel review

dsh-echocat-skill-panel is worth a controlled trial for existing DSH Desktop Beta users who need skill visibility and management.

  • Build 6 s
  • Tests failed
5 sto install
  • 0 packages
Dev Toolsevaluationupdated 01 Nov 2026
+0stars / 7d

Consider dsh-echocat-skill-panel if you already use DSH Desktop Beta and want skill tracking and management inside the application. The README describes dsh-echocat-skill-panel 5.1.3 as a DSH Desktop Beta plugin for tracking per-turn skill use and installing, removing, and updating skills. Our run on October 5, 2026 tested commit 1f98da6 in our sandbox; it did not verify the plugin inside a running DSH Desktop application.

Verdict

dsh-echocat-skill-panel is worth a controlled trial for existing DSH Desktop Beta users who need skill visibility and management. Our October 5, 2026 sandbox run at commit 1f98da6 recorded a successful installation and build, followed by a failed test command. Before adopting it across a team, verify loading in your actual host, review one skill's source, and exercise disabling, updating, and restoration in a disposable profile. The supplied evidence does not establish those workflows as tested.

We ran it

Lab card: what happened when we ran dsh-echocat-skill-panel
Lab card from our sandbox run
Screenshot of dsh-echocat-skill-panel (github.com/VDERR/dsh-echocat-skill-panel)
github.com/VDERR/dsh-echocat-skill-panel
Install✓ · 5s0 packages · 9 MB
Build✓ · 6s
Tests✗ · 4sran, no count parsed
Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
Repo97 files~34,266 lines of source · 5.4 MB · 0 CI workflows · tests dir

Answers from our run

Does dsh-echocat-skill-panel build from source?

Dependencies installed in 5 seconds (0 packages), and the build succeeded in 6 seconds. We cloned commit 1f98da6 into a clean Debian container with 3 CPUs and no project-specific setup.

Do dsh-echocat-skill-panel's tests pass?

No. The project's own test command exited unsuccessfully after 4 seconds, and its output did not expose an individual test count.

Does dsh-echocat-skill-panel have known vulnerabilities in its dependencies?

npm audit found none in the dependency tree at the time of our run.

Who should not use dsh-echocat-skill-panel?

Readers seeking a standalone skill manager for other agent applications.

What are the alternatives to dsh-echocat-skill-panel?

Awesome DeepSeek Harness, Awesome DSH Plugins. dsh-echocat-skill-panel is worth a controlled trial for existing DSH Desktop Beta users who need skill visibility and management.

Setup3/5Under the visible rubric, successful sandbox installation and build support a middle rating; host wiring, restart, and live desktop loading remain unverified.
Docs4/5For Chinese-reading users, the supplied README explains installation, restart boundaries, backup behavior, provenance, and development checks. English documentation was not independently established.
Community3/5A limited rating for public ecosystem discoverability through the supplied directories. Maintainer responsiveness, active-user adoption, and support quality were not measured.
Maturity3/5Version 5.1.3 has release documentation and described recovery mechanisms, but our sandbox test command exited 1 and live DSH workflows were not verified.

Who it’s for

DSH Desktop Beta users comfortable following Chinese documentation.
Users who want to inspect per-turn skill use alongside controls for installation, updates, and disabling.
Developers willing to check host integration separately from the repository build.

Who it’s NOT for

Readers seeking a standalone skill manager for other agent applications.
Teams that require a successful sandbox test command before adoption: ours exited 1.
Users who need appearance settings to sync across devices; the README explicitly limits them to the current client.
Readers who need this review to establish live DSH compatibility or skill-installation safety; neither was tested.

Setup reality

Our sandbox recorded installation success in 5 seconds, build success in 6 seconds, and test-command failure in 4 seconds at commit 1f98da6 on October 5, 2026. These are the attached harness values, not a new execution.

The installation tail includes an npm ci EUSAGE error about the required lockfile, followed by successful npm output. The enclosing installation step records exit 0. That establishes the recorded step outcome, not a successful npm ci invocation. The record lists 0 dependency packages and a 9 MB footprint.

The test tail identifies the missing package as @deepseek-ai/cordis, imported by test/smoke.mjs. DSH Desktop itself was not launched. The README says the host supplies optional peers and requires an application restart after installation or host-side changes.

Should you try it?

Try it in a disposable DSH Desktop Beta profile if per-turn skill visibility is the problem you need to solve. The documented management controls are relevant to that workflow, but our sandbox build does not establish that the panel works in your desktop installation.

The README describes dsh-echocat-skill-panel 5.1.3 as a DSH Desktop Beta plugin for tracking per-turn skill use and installing, removing, and updating skills. It says the plugin derives skill use from conversation events, including automatic loads and manual slash invocations. Those are documented capabilities, rather than observations from our desktop testing.

What our sandbox established

Our run on October 5, 2026 tested commit 1f98da6 in our sandbox; it did not verify the plugin inside a running DSH Desktop application.

Installation recorded exit 0 in 5 seconds, the build recorded exit 0 in 6 seconds, and the test command recorded exit 1 in 4 seconds. Our harness stores each step's outcome, exit code, duration, timeout flag, and a log tail. Reading those fields together matters here: the installation tail contains an earlier npm ci lockfile error even though the enclosing step succeeded.

The build tail confirms that the build script wrote lib/client.js. This verifies bundle generation in that run. It does not verify desktop loading, a conversation workload, skill installation, update recovery, or interface behavior.

The stored sandbox description names the lab-node:22 image, while the test tail reports Node.js v20.20.2 and runtime detection records Node major 20. The image label alone does not establish which Node executable ran the command.

The MrKeyoor testing methodology explains how command outcomes and measurement limits are reported. Its supplied October 31 snapshot provides provenance context; it does not establish that the October 5 run used that later procedure unchanged.

Why the test command failed

The raw failure names @deepseek-ai/cordis as the package that test/smoke.mjs could not import. The tail also contains a successful tracker/store footer before the missing-package error. A successful subset footer and a failed overall command can coexist; this evidence does not establish an internally inconsistent release gate.

We do not report that footer as an aggregate passing-test count. The attached aggregate tests field is null, and exhaustive unique coverage was not verified. There was no new execution or complete-log reconciliation. The supported conclusion is narrower: the test command could not complete successfully in our sandbox because the smoke test encountered a missing package. Whether a properly configured DSH host resolves that import remains untested here.

The stored npm audit result contains 0 advisories. Scanned-package coverage is unknown because the record has no scannedPackages field. This is an advisory result, not a security assessment of the plugin or the skills it installs.

What the management controls change

According to the README, installation accepts repository and subdirectory addresses, SKILL.md links, ZIP links, uploaded Markdown or ZIP files, and pasted skill content. Same-named skills are backed up before replacement, and deletion moves files into backup rather than permanently removing them.

The README says source information is stored in .echocat.json beside an installed skill, including its address, branch, subdirectory, installation commit, and content fingerprint. Update checks use git ls-remote. Updates move the old copy to backup, while the confirmation warns when local edits will be overwritten.

Disabling a skill moves its directory out of the location DSH watches. That gives users a concrete filesystem operation to inspect. We did not exercise these operations, verify restoration, or review installed skill content for safety.

Discovery tools complement the panel

Awesome DeepSeek Harness is a curated directory of plugins, skills, MCP servers, patch/profile layers, orchestrators, and interfaces for DeepSeek Harness. Use it to find projects to inspect; its supplied description establishes a discovery role rather than the panel's per-turn reporting role.

Awesome DSH Plugins publishes a machine-readable registry whose source of truth is data/plugins.json. Choose it when you need registry data or discovery integration. Both directories can complement a panel installation; neither supplied extract establishes a replacement for this plugin's conversation-event reporting.

How to read the scores

These editorial ratings use a five-point rubric: 1 means substantial documented obstacles, 2 means significant limitations, 3 means useful evidence with material gaps, 4 means strong evidence for the stated audience, and 5 requires broad verification with few unresolved limits. They are not benchmark results or adoption measurements.

Setup receives 3 because the recorded install and build succeeded, but desktop wiring and restart remain outside our verification. Documentation receives 4 for the Chinese-reading audience because the supplied README explains installation, restart boundaries, source tracking, backup behavior, and development checks. Community receives 3 as a limited assessment of public ecosystem discoverability, not support responsiveness or adoption. Maturity receives 3 because the release and operational documentation provide useful evidence, while our test command failed and live host behavior remains unverified.

Alternatives

ProjectWhat it isPick it when
Awesome DeepSeek HarnessA curated directory of DeepSeek Harness extensions and related tools.Use it for discovery before choosing what to install. It complements the panel; the supplied source does not establish equivalent per-turn reporting.
Awesome DSH PluginsAn open-data registry with data/plugins.json as its source of truth.Choose it for machine-readable discovery data or registry integration. Treat it as a complement to an in-app manager.

What people are saying

  1. [velocity-scout] VDERR/echocat-skill-panel-3.0

Sources

  1. dsh-echocat-skill-panel repository
  2. dsh-echocat-skill-panel README
  3. v5.1.3 release
  4. Chinese installation guide

More dev tools reviews