AI Agent Hub
Back to plugins
🧩

dsh-skill-stats

admin-security Updated 2026.08.20

Run the following command in DeepSeek Harness:

dsh plugin install omdsh-dev/dsh-skill-stats

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install omdsh-dev/dsh-skill-stats in the DeepSeek Harness terminal to install the read-only skill call statistics plugin from https://github.com/omdsh-dev/dsh-skill-stats.

About this plugin

As your skill catalogue grows, a deceptively simple question becomes hard to answer: which skills are actually being invoked, and which have quietly become dead weight? dsh-skill-stats exists to fill that gap. It attaches read-only to the host environment, modifying neither session logs nor skill files, yet it replays historical tool/call events on startup and keeps subscribing to live invocations in real time, surfacing each skill's cumulative call count, active session count, and first and last invocation timestamps.

The dashboard offers two complementary views. The session view lets you expand a single conversation to see every skill it touched, each row carrying a mini trend chart that opens into a full timeline. The global view consolidates all skills including those with zero usage into a sortable table with SVG trend charts and 1/3/7/30-day range filters, with per-invocation details one click away. Under the hood, a file-level incremental cache ensures restarts only replay changed logs, while deleted skills are auto-flagged so a transient empty snapshot is never mistaken for never used.

If you manage multiple workspaces, have outgrown your skill directory into a list that needs periodic pruning, and want a purely read-only audit tool to make keep-or-ditch decisions, dsh-skill-stats is a drop-in panel that requires zero configuration beyond a standard plugin install.

Use Cases

  • Prune skills that have never been invoked to stop catalogue bloat
  • Review a skill's 7 or 30-day invocation trend to decide whether to keep it
  • Audit which skills a particular session triggered and on what dates

Best For

  • Admins managing multi-workspace skill catalogues who need periodic keep-or-ditch reviews
  • Developers who want purely read-only usage auditing without modifying any logs
  • Ops staff maintaining multiple global skill roots who need cross-workspace statistics