Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
digital staff
v2.0.0A modern web-based dashboard for managing OpenClaw agents with real-time monitoring, token usage tracking, skill management, and multi-language support. Prov...
⭐ 0· 27·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's code and SKILL.md align with a dashboard for OpenClaw (finding OpenClaw installs, listing/creating agents, managing skills). However the registry metadata declares no required config paths or credentials while the implementation clearly reads and writes ~/.openclaw and creates agent directories in ~/.openclaw/agents. That mismatch (no declared config paths but extensive file access) is an inconsistency the user should be aware of.
Instruction Scope
SKILL.md and the included scripts instruct the user to clone/run install.sh or start dashboard_server.py. The code searches the user's home for OpenClaw installations, reads ~/.openclaw/openclaw.json, and (per README and scripts) can create new agent directories and write model/metadata files into ~/.openclaw/agents. The dashboard exposes REST endpoints for listing/creating/deleting agents and uploading avatars. These operations touch and modify potentially sensitive local configuration (including model provider entries and API keys) and are broader than metadata claims.
Install Mechanism
There is no formal install spec in the registry metadata, but the package includes install.sh and start.sh. install.sh will pip install Flask (via pip --user), create a systemd user service file, enable it, and optionally start it. The install approach is typical but performs filesystem writes (systemd user unit, desktop shortcut) and launches a service — so the user should review the install script before running it.
Credentials
Registry metadata lists no required environment variables, but SKILL.md and scripts reference OPENCLAW_HOME and DASHBOARD_PORT. More importantly, the dashboard reads/writes ~/.openclaw/openclaw.json and agent model files; those files often contain model provider configurations and API keys. Requiring (and manipulating) these local config files is a legitimate need for a management dashboard, but the omission from declared requirements and the potential to copy/store provider API keys inside agent files is a sensitive capability that should be explicitly called out to users.
Persistence & Privilege
always is false. The installer (with interactive prompts) can create and enable a user-level systemd service that will autorun the dashboard. The dashboard defaults to binding to all addresses (config DEFAULT host is '0.0.0.0' and server.log shows 'Running on all addresses (0.0.0.0)'), which can expose the dashboard and any OpenClaw configuration it serves to the local network. This persistence and network exposure are significant and require user attention, but they are not set automatically by the registry metadata — they happen via the provided install script if the user consents.
What to consider before installing
Before installing/running this skill:
- Review the code (especially dashboard_server.py, install.sh and start.sh) to confirm authentication and binding behavior. The shipped config defaults bind the server to 0.0.0.0 (exposed to network).
- Expect the dashboard to read and write ~/.openclaw/openclaw.json and to create/modify files under ~/.openclaw/agents — back up that directory first and inspect openclaw.json for API keys you may not want exposed.
- Do not run install.sh or enable the systemd service without reading it; install.sh will create a user systemd unit and may start the service.
- If you want safer deployment: run the dashboard in a sandbox or container, change host binding to 127.0.0.1, restrict firewall rules, or require explicit authentication on the dashboard before exposing it to any network.
- If you install, verify that REST endpoints require appropriate auth and that uploaded avatars or created agent files are stored where you expect.
Given the missing declarations in the metadata (no config paths or env vars listed) and the dashboard's ability to modify local OpenClaw data and serve it over the network, treat this package as requiring manual review and limited deployment (suspicious until validated).data/config.json:89
Install source points to URL shortener or raw IP.
About static analysis
These patterns were detected by automated regex scanning. They may be normal for skills that integrate with external APIs. Check the VirusTotal and OpenClaw results above for context-aware analysis.Like a lobster shell, security has layers — review code before you run it.
latestvk97531h48g83e6nk9fjzy8rpc98496ba
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📊 Clawdis