Unifi

This skill appears to implement a legitimate UniFi read-only monitor, but review and accept a few risks before installing: - Credentials: the skill requires a local UniFi admin username/password stored in ~/.clawdbot/credentials/unifi/config.json (or via environment variables). That file contains plaintext credentials — ensure you set restrictive permissions (chmod 600) and consider creating a dedicated low-privilege local admin for the API. - Metadata mismatch: the registry entry lists no required config paths/env, but the skill actually requires the config file or env vars. Treat this as an indicator the package metadata is incomplete; verify the file location and ownership before running. - Disk writes: the scripts write files (dashboard_debug_dump.json and $HOME/clawd/memory/bank/unifi-inventory.md) that contain sensitive network data. If you don’t want that persisted, edit the scripts to disable dumps or change paths to a secure location. - SSL verification: the scripts use curl -k to skip TLS verification (common with self-signed UniFi certs). This is insecure in network environments where the gateway might be spoofed — if possible, use a valid certificate or modify scripts to verify certs. - Review scripts locally: because this is an instruction-based skill with runnable shell scripts, inspect scripts locally before use and consider running them in a controlled environment first. If you’re uncomfortable with plaintext creds or disk persistence, either modify the scripts to use a more secure auth method (token, restricted account) or do not install. If you want, I can list the exact places in the scripts to change to improve security (e.g., remove debug dump, enforce cert verification, set strict file perms).