Unraid

This skill looks like a legitimate Unraid monitoring helper, but the declared metadata is incomplete and the scripts perform filesystem I/O in your home directory and expect environment variables and helper binaries. Before installing or running: 1) Inspect $HOME/.clawdbot/credentials/unraid/config.json (if it exists) to ensure it only contains servers/API keys you intend to expose to this tool. 2) Be aware the scripts save debug and report files (e.g., ${NAME}_debug.json and $HOME/clawd/memory/bank/unraid-inventory.md) — run in an isolated directory or container if you don’t want these persisted. 3) Verify you are willing to provide an Unraid API key (give the Viewer role only) and that keys stored for other services are not stored in the same config. 4) The helper uses curl -k (skips TLS verification) — consider editing scripts to remove -k or ensure you use valid TLS certs or a private network. 5) Ensure jq and curl are available on the host. If these gaps (missing metadata about env vars, binaries, and config paths) are acceptable and you trust the source, the scripts are coherent for their stated monitoring purpose; otherwise ask the publisher to correct metadata or provide a version that documents and limits file access.