Node Red Manager

Manage Node-RED instances via Admin API or CLI. Automate flow deployment, install nodes, and troubleshoot issues. Use when user wants to "build automation", "connect devices", or "fix node-red".

This skill appears to implement a legitimate Node-RED admin client, but there are multiple incoherences you should resolve before installing or giving it credentials: - Do not provide admin credentials until you review the code and are comfortable. The Python client expects NODE_RED_USERNAME / NODE_RED_PASSWORD and NODE_RED_URL but the registry metadata does not declare them. Use a least-privilege admin account and rotate credentials afterwards. - Verify the CLI wrapper: SKILL.md commands reference scripts/nr but the repo contains scripts/nr_api.py only. Confirm how the CLI is invoked and whether any wrapper will be installed or created automatically. - Review the included flow (assets/flows/watchdog.json). It contains an exec node that will run shell commands on the Node-RED host (currently configured to run 'uptime -p' every 5s). Because the skill can deploy flows via the Admin API, deploying unreviewed flows can execute arbitrary commands on the host. Only deploy flows you trust and review them for exec/http-request/function nodes that could be abused. - The SKILL.md references Docker compose operations and a specific service name and URL — ensure those are relevant to your environment and that Docker/docker-compose are present before running those commands. - Check for missing files the instructions mention (e.g., .env.example). If the skill claims to 'auto-handle dependencies', inspect whether it will run pip installs automatically or require manual setup. If you want to proceed: run the client in an isolated/test environment first, inspect and sanitize any flows before deployment, provide a least-privilege account, and consider network/firewall restrictions around your Node-RED instance. If you can get the maintainers to fix the manifest (declare required env vars, provide a proper CLI wrapper, remove or explain the hard-coded infra hints), the coherence and safety posture will improve.

Type: OpenClaw Skill Name: node-red-manager Version: 1.0.0 The skill is designed for legitimate Node-RED management, but the `scripts/nr_api.py` script contains path traversal vulnerabilities in its file handling functions (`backup_flows`, `restore_flows`, `deploy`, `update_flow`). These flaws allow an attacker to specify arbitrary file paths (e.g., `../../../etc/passwd` or `../../../tmp/malicious_flow.json`) when using the CLI commands. This could lead to arbitrary file reads (LFI) or, more critically, Remote Code Execution (RCE) by deploying malicious Node-RED flows containing `exec` nodes (a capability explicitly noted as an RCE risk in `references/admin-api.md`) from an attacker-controlled file path. There is no evidence of intentional malicious behavior, but the severe vulnerabilities warrant a 'suspicious' classification.