Unifi
Analysis
The skill appears coherent for UniFi administration, but it gives an agent direct authority to change network settings such as DNS, Wi‑Fi, and radio configuration without documented approval or rollback safeguards.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
python3 {baseDir}/scripts/unifi.py set-wlan ...; python3 {baseDir}/scripts/unifi.py set-network-dns Default --dns1 1.1.1.1 --dns2 1.0.0.1; python3 {baseDir}/scripts/unifi.py set-radio --ap Living --band 5 --channel 36 --width 80 --power highThese documented commands directly modify Wi‑Fi, DNS, and radio settings on UniFi infrastructure. The artifacts do not describe confirmation, dry-run, scoped approval, or rollback safeguards for these high-impact changes.
Python 3.12+; `requests` library (`pip install requests`)
The setup relies on a manually installed external Python package, but there is no install spec or pinned dependency version in the supplied artifacts. This is common for a small CLI skill, but users should install from trusted package sources.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
"api_key": "YOUR_SITE_MANAGER_API_KEY", "gateway_ip": "192.168.0.2", "local_api_key": "YOUR_LOCAL_API_KEY"
The skill requires a UniFi Site Manager API key and can optionally use a local gateway API key. This is expected for the purpose, but those credentials provide sensitive administrative access to network inventory and configuration.
