add-clidash

Run the add-clidash skill, which copies the self-contained clidash tool into tools/clidash and creates a config pre-wired for the ncl CLI. Start it with node server.js and open http://127.0.0.1:4690 to see agent status cards, resource tables, activity charts, logs, and files.

clidash runs the CLI's help output through a discovery parser to find resources, then executes a configured argv template like ncl <resource> list --json for each one. Each discovered resource becomes a tab and each JSON column becomes a table column with no code changes.

Yes, any CLI that lists resources as JSON works by adding a config entry with its binary path, resource list or discovery command, and output format. The example config includes docker using jsonlines output, and kubectl-style CLIs work the same way.

clidash is read-only by construction: it can only execFile configured argv templates with allowlist-validated resource names, never a shell. It has no authentication, so it binds 127.0.0.1 by default and should only ever be bound to a private interface such as a tailnet IP.

Empty discovery means the ncl binary is missing or the configured path is wrong. Build it with pnpm run build so bin/ncl exists, or fix the clis.ncl.bin path in clidash.config.json relative to the configured cwd.

clidash has zero npm dependencies and no build step, using only Node built-ins. It requires Node 22.5 or later for the node:sqlite module used to read session message databases.