Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
RTS Dashboard
v1.0.0RTS (Real-Time Strategy) style monitoring dashboard for OpenClaw. Provides a browser-based tactical command center with real-time visualization of agents, sk...
⭐ 0· 104·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (RTS monitoring dashboard) match the behaviour: the server reads OpenClaw config, enumerates agents/skills/sessions, polls system vitals, and can open a Web UI and connect to the Gateway. The use of a Gateway token and filesystem reads under ~/.openclaw and agent skill/workspace directories are coherent with monitoring and chat features.
Instruction Scope
SKILL.md instructs the agent to check port 4320, run `node server.js` (background), and `npm install` if node_modules is missing — all expected to launch the dashboard. The instructions reference only OpenClaw config files, skill/session paths, and the local Gateway. This grants the skill the ability to read local OpenClaw state and to send chat via the Gateway (an explicit feature), but does not instruct unrelated data collection or external transmission.
Install Mechanism
No install spec is provided (instruction-only for the agent), and included package.json/package-lock.json only depend on the standard 'ws' npm package from the public registry. No downloads from untrusted URLs or extract-from-arbitrary-URLs are present.
Credentials
The skill requests no required env vars but will read optional OPENCLAW_GATEWAY_TOKEN or gateway.auth.token from ~/.openclaw/openclaw.json and scans agent/workspace skill directories and session files. That is proportionate for a monitoring/dashboard tool, but it does access potentially sensitive local tokens and session data and will write an unencrypted .device-keys.json (private key) into the skill directory for Gateway device auth — the user should be aware of these sensitive local accesses.
Persistence & Privilege
always is false and the skill does not request persistent platform-wide privileges. It writes its own .device-keys.json and runs as a local process; it does not modify other skills or system-wide agent configurations. The SKILL.md asks the user to add an allowedOrigins entry to Gateway config (manual step) rather than changing it automatically.
Assessment
This dashboard appears to be what it claims: a local Node.js web server that reads your OpenClaw config, sessions, and skill directories and can connect to the local Gateway. Before installing/running: 1) review server.js and public/index.html yourself (or run in an isolated container) because `npm install` and `node server.js` will execute code from this package; 2) note the dashboard will read ~/.openclaw/openclaw.json (may contain the Gateway token) and will save an Ed25519 private key unencrypted at .device-keys.json in the skill folder — consider file permissions or storing it elsewhere if that concerns you; 3) granting the Gateway allowedOrigins entry will permit the dashboard's web UI to connect to the Gateway from localhost — apply that change intentionally; 4) if you don't trust the source, run the server in a sandbox or VM and inspect network connections. Overall the package is internally consistent with its monitoring purpose, but treat the local token/private-key access as sensitive.server.js:25
Shell command execution detected (child_process).
Patterns worth reviewing
These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97ah1vfbx8epxrbn5812s4fsx83kxw6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.