Agent skill

clidash CLI Dashboard for NanoClaw

Installs clidash, a dependency-free web dashboard that turns the JSON resource listings of a CLI such as NanoClaw's ncl into read-only tabs and tables.

MITAuto-check passedDevOps & Cloud

Install clidash CLI Dashboard for NanoClaw

skills CLI

$ npx skills add nanocoai/nanoclaw --skill add-clidash -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nanocoai/nanoclaw add-clidash --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/add-clidash .claude/skills/add-clidash && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "add-clidash" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/add-clidash into .claude/skills/add-clidash/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-clidash", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/add-clidash

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nanocoai/nanoclaw --skill add-clidash -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nanocoai/nanoclaw add-clidash --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/add-clidash .agents/skills/add-clidash && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "add-clidash" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/add-clidash into .agents/skills/add-clidash/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-clidash", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nanocoai/nanoclaw --skill add-clidash -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nanocoai/nanoclaw add-clidash --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/add-clidash .cursor/skills/add-clidash && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "add-clidash" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/add-clidash into .cursor/skills/add-clidash/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-clidash", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nanocoai/nanoclaw.git --path .claude/skills/add-clidash

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nanocoai/nanoclaw --skill add-clidash -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nanocoai/nanoclaw add-clidash --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/add-clidash .gemini/skills/add-clidash && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "add-clidash" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/add-clidash into .gemini/skills/add-clidash/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-clidash", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nanocoai/nanoclaw add-clidash

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nanocoai/nanoclaw --skill add-clidash -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/add-clidash .github/skills/add-clidash && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "add-clidash" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/add-clidash into .github/skills/add-clidash/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-clidash", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nanocoai/nanoclaw --skill add-clidash -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nanocoai/nanoclaw add-clidash --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nanocoai/nanoclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/add-clidash .opencode/skills/add-clidash && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "add-clidash" agent skill from https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/add-clidash into .opencode/skills/add-clidash/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-clidash", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: add-clidash
GitHub stars: 31k
Token cost: ~1.6k tokens
SKILL.md length: 716 words
Files: 39
Skills in repo: 59
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Installs clidash, a dependency-free web dashboard that turns the JSON resource listings of a CLI such as NanoClaw's ncl into read-only tabs and tables.

Works in 5 steps: Copy the tool into place → Create the config → Test → …
Getting a quick read-only view of NanoClaw groups, sessions and channels
SKILL.md covers Why it's safe, Steps, Configuration reference and Troubleshooting, plus 1 more section
Runs JavaScript scripts from its folder; calls node, curl and pnpm

What it does

clidash points at a CLI such as `ncl`, `docker` or `kubectl` and creates one tab per resource with a generic table over whatever columns the rows contain, so a new resource or column shows up with no code change. For NanoClaw it adds an agents overview with status cards colored by recent activity, message activity charts read from the session databases, a tail of allowlisted host log files and a read-only viewer for group skills, `CLAUDE.md` and profiles.

It is read-only by design: the server only runs the argv templates in its config, the single `{resource}` substitution is checked against an allowlist, and no shell is involved. There is no authentication and it binds `127.0.0.1` by default, so only a private interface should ever be used. Installing means copying the `clidash` folder into `tools/` and creating a config from the example file. It has no dependencies or build step and differs from `/add-dashboard`.

When your agent uses it

Getting a quick read-only view of NanoClaw groups, sessions and channels
Putting a web dashboard over any CLI that can output resources as JSON
Watching host logs and message activity without changing NanoClaw's source

Example prompts

“Add clidash to NanoClaw so I can see agent groups and sessions in a browser.”
“Point clidash at kubectl and show pods and deployments as tabs.”
“Set up clidash on my tailnet address only, and keep it off the public interface.”

Requirements

A NanoClaw installation with the `ncl` CLI
Node.js to run the dashboard server

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Copy the tool into place
Create the config
Test
Run and verify
(Optional) Run as a service

What it can do on your machine

Read from SKILL.md and the folder at commit af699e7. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (JavaScript, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
- node
- curl
- pnpm
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, pnpm and npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

clidash CLI Dashboard for NanoClaw loads about 1.6k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 716 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~88
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nanocoai/nanoclaw at commit af699e7, republished under its MIT licence (© nanocoai). 716 words, ~1,608 tokens.

Download SKILL.mdSave it as .claude/skills/add-clidash/SKILL.md (or your agent's skills folder). This skill also uses 38 other files; get the full folder from GitHub.

name: add-clidash
description: Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.

/add-clidash — CLI-derived read-only dashboard

clidash is a small, read-only web dashboard. You point it at any CLI that can list resources as JSON (NanoClaw's ncl, docker, kubectl, …) and it builds the dashboard at runtime: one tab per resource, a generic table over whatever columns the rows have. A new ncl resource becomes a new tab and a new column becomes a new table column with zero code changes.

It ships pre-wired for NanoClaw's ncl CLI and adds three NanoClaw-aware panels driven entirely by config:

Agents overview — status cards joining groups + sessions + messaging groups + wirings (green <15m / amber <2h / red older).
Activity — per-session inbound/outbound message totals and a daily series, read directly from the session DBs (ncl has no messages resource).
Logs — last N lines of allowlisted host log files.
Files — a read-only viewer for group skills, CLAUDE.md, and profiles.

Why it's safe

clidash is read-only by construction: the server can only execFile the argv templates in its config. {resource} is the sole substitution and is allowlist-validated against the discovered/static resource set before exec — never a shell, no free-form input reaches argv. There is no auth; the network is the auth boundary — it binds 127.0.0.1 by default. Only ever bind a private interface (e.g. a tailnet IP), never a public one.

It's distinct from /add-dashboard (which pushes JSON snapshots to a separate @nanoco/nanoclaw-dashboard npm package): clidash has zero dependencies, no build step, no push pipeline, and no edits to NanoClaw source — it just reads ncl and the session DBs.

Steps

1. Copy the tool into place

clidash is fully self-contained — copy the whole directory in:

tools/ is not a standard NanoClaw directory and cp -R won't create it, so make it first:

bash

mkdir -p tools
cp -R .claude/skills/add-clidash/add/tools/clidash tools/clidash

That is the only file change this skill makes. Nothing in NanoClaw src/ is touched, no dependency is added.

2. Create the config

The example config is pre-wired for NanoClaw with paths relative to the repo root, so it works as-is when you run clidash from tools/clidash/:

bash

cd tools/clidash
cp clidash.config.example.json clidash.config.json

clidash.config.json is your local config — add it to .gitignore if you don't want to commit install-specific paths:

bash

echo 'tools/clidash/clidash.config.json' >> ../../.gitignore

The example assumes ncl is built at bin/ncl. If bin/ncl doesn't exist, build it first (pnpm run build) or point clis.ncl.bin at the right path.

3. Test

Tests use a stub CLI — no real ncl or docker needed:

bash

npm test

All tests should pass (Node ≥ 22.5, node:test, zero dependencies).

4. Run and verify

bash

node server.js          # serves http://127.0.0.1:4690

In another shell, confirm it's live and that ncl discovery worked:

bash

curl -s http://127.0.0.1:4690/api/clis | head -c 400      # CLIs + discovered resources
curl -s http://127.0.0.1:4690/api/r/ncl/groups | head -c 400   # a real resource table

Then open http://127.0.0.1:4690/ in a browser. You should see the Agents overview plus a tab per ncl resource.

Show full SKILL.md (291 more words)Show less

5. (Optional) Run as a service

clidash binds 127.0.0.1 by default. To reach it from other devices, bind a private (e.g. tailnet) IP via the BIND env var or bind in config — never a public interface.

ini

# ~/.config/systemd/user/clidash.service   (Linux)
[Unit]
Description=clidash read-only CLI dashboard

[Service]
WorkingDirectory=%h/nanoclaw/tools/clidash
ExecStart=/usr/bin/node %h/nanoclaw/tools/clidash/server.js
Environment=BIND=127.0.0.1
Restart=on-failure

[Install]
WantedBy=default.target

bash

systemctl --user enable --now clidash

On macOS, wrap node server.js (with WorkingDirectory = tools/clidash) in a launchd plist the same way the main NanoClaw service is configured.

Configuration reference

clidash.config.json keys (see tools/clidash/README.md and clidash.config.example.json for the full shape):

Key	Purpose
`port`, `bind`, `refreshSeconds`	server bind + UI auto-refresh cadence
`clis.<name>.bin` / `cwd` / `env`	how to invoke the CLI (`bin` is relative to `cwd`)
`clis.<name>.discover` or `resources`	runtime discovery (`ncl help`) vs a static resource list
`clis.<name>.list`	argv template; `{resource}` is the only substitution
`clis.<name>.output`	`json` or `jsonlines` (docker/kubectl style)
`clis.<name>.unwrap`	dot-path into a response envelope (e.g. `data`)
`clis.<name>.enrich`/`badges`/`summary`	table decorations (ID→name joins, status colors, summary cards)
`activity`	`sessionsRoot` + `days` for the message-activity charts
`logs`	`dir`, `tailLines`, and an allowlist of `files` to tail
`docs`	file viewer: `root`, a `deny` glob list, and `collections` of glob patterns

Adding a second CLI is config-only — e.g. docker is included as a jsonlines example. View plugins (views/<cli>-<view>.js) are the only per-CLI code and are optional.

Troubleshooting

ENOENT / config not found — run from tools/clidash/ and make sure you copied clidash.config.example.json to clidash.config.json (step 2), or set CLIDASH_CONFIG=/abs/path.json.
No ncl resources / discovery empty — bin/ncl isn't built or the path is wrong. Build it (pnpm run build) or fix clis.ncl.bin.
docker tab errors — the docker daemon isn't running, or remove the docker CLI from config if you don't need it.
Can't reach it from another device — it binds 127.0.0.1; set BIND=<private-ip> (tailnet), never a public interface.
Empty Activity/Logs/Files — check that activity.sessionsRoot, logs.dir, and docs.root resolve to your NanoClaw root (relative to where you launch node server.js).

Removal

See REMOVE.md.

Files

SKILL.md and 38 other files in .claude/skills/add-clidash of nanocoai/nanoclaw.

SKILL.md
REMOVE.md
add/tools/clidash/README.md
add/tools/clidash/activity.js
add/tools/clidash/clidash.config.example.json
add/tools/clidash/docs.js
add/tools/clidash/logs.js
add/tools/clidash/package.json
add/tools/clidash/parsers.js
add/tools/clidash/public/app.js
add/tools/clidash/public/apple-touch-icon.png
add/tools/clidash/public/favicon.ico
add/tools/clidash/public/favicon.svg
add/tools/clidash/public/icon-192.png
add/tools/clidash/public/icon-512.png
add/tools/clidash/public/index.html
add/tools/clidash/public/md.js
… and 22 more

Open the folder on GitHubat commit af699e7

Compare with similar skills

clidash CLI Dashboard for NanoClaw next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

clidash CLI Dashboard for NanoClaw compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
clidash CLI Dashboard for NanoClaw this skillnanocoai/nanoclaw	31k	—	~1.6k	Automated safety check: Pass	MIT	today
Alloygrafana/skills	282	—	~1.3k	Automated safety check: Pass	Apache-2.0	yesterday
Kratos Developmentaide-family/moon	253	—	~1.5k	Automated safety check: Pass	None	3 mo ago
WizTelemetry Platform Servicekubesphere/kubesphere	17k	—	~1.8k	Automated safety check: Pass	Custom licence	2 mo ago
Logfire Infrastructurepydantic/skills	140	—	~1.8k	Automated safety check: Pass	MIT	8 days ago
Proto Backend Moduleaide-family/moon	253	—	~4.1k	Automated safety check: Pass	None	3 mo ago

Similar skills

Alloy
grafana/skills
Official
Build a unified telemetry pipeline with Grafana Alloy — one OpenTelemetry-compatible binary that collects metrics, logs, traces, and profiles and ships to Grafana Cloud / Prometheus / Loki / Tempo /…
282 GitHub stars~1.3k tokensUpdated yesterday
DevOps & CloudAuto-check passed
Kratos Development
aide-family/moon
Develops Go microservices with Kratos v2 following official design philosophy, DDD/Clean Architecture layout, Protobuf API, error/config/middleware patterns, and observability.
253 GitHub stars~1.5k tokensUpdated 3 mo ago
Backend & APIsAuto-check passed
WizTelemetry Platform Service
kubesphere/kubesphere
Installs and configures the WizTelemetry Platform Service extension for KubeSphere, the shared API server behind its observability extensions.
17k GitHub stars~1.8k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed
Logfire Infrastructure
pydantic/skills
Official
Monitor hosts, Docker containers, Kubernetes clusters, database/queue/cache servers, and cloud-provider metrics with Pydantic Logfire — no application code required.
140 GitHub stars~1.8k tokensUpdated 8 days ago
DevOps & CloudAuto-check passed
Proto Backend Module
aide-family/moon
Implements backend modules from proto definitions for goddess, marksman, and rabbit apps.
253 GitHub stars~4.1k tokensUpdated 3 mo ago
DevOps & CloudAuto-check passed
KubeSphere WizTelemetry Events
kubesphere/kubesphere
Installs and configures the WizTelemetry Events extension for KubeSphere, which exports Kubernetes events for storage, with dependency checks and the event query API.
17k GitHub stars~1.8k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed

Questions about clidash CLI Dashboard for NanoClaw

What does clidash CLI Dashboard for NanoClaw do?

Installs clidash, a dependency-free web dashboard that turns the JSON resource listings of a CLI such as NanoClaw's ncl into read-only tabs and tables. clidash points at a CLI such as `ncl`, `docker` or `kubectl` and creates one tab per resource with a generic table over whatever columns the rows contain, so a new resource or column shows up with no code change.md` and profiles.

When should I use clidash CLI Dashboard for NanoClaw?

clidash CLI Dashboard for NanoClaw fits situations like: getting a quick read-only view of NanoClaw groups, sessions and channels; putting a web dashboard over any CLI that can output resources as JSON; watching host logs and message activity without changing NanoClaw's source.

How do I install clidash CLI Dashboard for NanoClaw in Claude Code?

Run `npx skills add nanocoai/nanoclaw --skill add-clidash -a claude-code`. Or copy the skill folder (.claude/skills/add-clidash in nanocoai/nanoclaw) into .claude/skills/add-clidash in your project. Claude Code loads it when a task matches its description.

How do I install clidash CLI Dashboard for NanoClaw in Codex?

Run `npx skills add nanocoai/nanoclaw --skill add-clidash -a codex`. Or copy the skill folder (.claude/skills/add-clidash in nanocoai/nanoclaw) into .agents/skills/add-clidash in your project. Codex loads it when a task matches its description.

Can I use clidash CLI Dashboard for NanoClaw in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nanocoai/nanoclaw --skill add-clidash -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-clidash, .gemini/skills/add-clidash, .github/skills/add-clidash and .opencode/skills/add-clidash in your project.

What does clidash CLI Dashboard for NanoClaw need to run?

Going by SKILL.md and its folder, clidash CLI Dashboard for NanoClaw needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node, curl, pnpm and npm). Our summary lists: A NanoClaw installation with the `ncl` CLI; Node.js to run the dashboard server.

Does clidash CLI Dashboard for NanoClaw access the network?

SKILL.md contains no URLs. Its commands use curl and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is clidash CLI Dashboard for NanoClaw safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does clidash CLI Dashboard for NanoClaw use?

clidash CLI Dashboard for NanoClaw is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does clidash CLI Dashboard for NanoClaw use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to clidash CLI Dashboard for NanoClaw?

Skills that share tags, products or a category with clidash CLI Dashboard for NanoClaw: Alloy (grafana/skills, 282 stars), Kratos Development (aide-family/moon, 253 stars), WizTelemetry Platform Service (kubesphere/kubesphere, 17k stars) and Logfire Infrastructure (pydantic/skills, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains clidash CLI Dashboard for NanoClaw?

nanocoai (a GitHub organization) maintains it in nanocoai/nanoclaw, which has 30,906 GitHub stars. The repository holds 59 skills in this directory. The repository was last updated on October 9, 2026.

Source: nanocoai/nanoclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install clidash CLI Dashboard for NanoClaw

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/add-clidash — CLI-derived read-only dashboard

Why it's safe

Steps

1. Copy the tool into place

2. Create the config

3. Test

4. Run and verify

5. (Optional) Run as a service

Configuration reference

Troubleshooting

Removal

Files

Compare with similar skills

Similar skills

More from nanocoai/nanoclaw

Related

Questions about clidash CLI Dashboard for NanoClaw