ℹ
Purpose & Capability
The scripts and documentation align with the stated purpose: they use the UniFi OS local gateway API to GET monitoring endpoints (devices, clients, health, DPI, alerts). Required binaries (curl, jq) are appropriate. However, the skill expects a credentials file at ~/.clawdbot/credentials/unifi/config.json (or environment variables) even though the registry metadata declared no required config paths or env — that metadata omission is an incoherence.
⚠
Instruction Scope
SKILL.md and the scripts instruct the agent to read a local credentials file (containing username/password) and to perform login (POST /api/auth/login) then multiple GETs. The scripts also write data to disk (dashboard_debug_dump.json and $HOME/clawd/memory/bank/unifi-inventory.md). The README and scripts intentionally skip SSL verification (curl -k). While the operations are limited to the local UniFi gateway and are GET-only for configuration endpoints, the skill stores and reads plaintext credentials and persists potentially sensitive network data to files — these behaviors extend beyond simple transient monitoring and increase risk if not managed.
✓
Install Mechanism
Instruction-only skill with bundled shell scripts (no external downloads or package installs). No install spec means nothing arbitrary is fetched during install — low install risk. The included scripts will be executed at runtime, so their contents matter (and were reviewed).
⚠
Credentials
Requesting UniFi local admin credentials is expected for the stated purpose, but the skill did not declare the required config path or environment variables in the registry metadata. Storing a local admin password in plaintext at ~/.clawdbot/credentials/unifi/config.json (or via env vars) is necessary for this implementation but is sensitive — the skill doesn't provide guidance on secure file permissions beyond the README. Using UNIFI_CONFIG_FILE override is supported but again not declared in metadata.
ℹ
Persistence & Privilege
always:false and autonomous invocation not disabled (normal). The scripts create and write files under the user's home (OUTPUT_FILE=$HOME/clawd/memory/bank/unifi-inventory.md and dashboard_debug_dump.json). They also create temporary cookie files for sessions (deleted in most flows). Writing persistent dumps of network inventory/clients to disk is legitimate for some workflows but is a persistence/privacy concern that the user should explicitly accept.