Starling Home Hub (Nest/Google Home)

Controls Nest and Google Home smart home devices via the Starling Home Hub's local REST API. Supports thermostats, cameras, Nest Protects, Nest × Yale locks, temperature sensors, home/away control, and Nest weather service. Use this skill when managing Nest/Google Home devices through Starling Home Hub — reading device status, setting temperatures, getting camera snapshots, locking/unlocking doors, checking smoke/CO alerts, and toggling home/away mode.

This skill appears coherent and implements a local Starling Home Hub client via an included Bash script. Before installing: (1) only provide STARLING_API_KEY and the hub IP — treat that key as sensitive and create a least-privilege/read-only key if possible; (2) avoid passing the key with --key (visible in process lists); use the STARLING_API_KEY env var instead; (3) prefer supplying --cacert to pin the hub certificate rather than accepting -k (curl -k disables TLS verification and is acceptable only on a fully trusted local network); (4) never port-forward the hub ports to the internet; (5) snapshots are written with owner-only permissions by the script but still handle them carefully; (6) inspect scripts you run locally (scripts/starling.sh is included and readable) and ensure you trust the source before giving the agent access to your hub credentials. If you plan to allow autonomous agent actions, be aware the agent could issue commands to your hub while it has access to the API key — consider limiting the skill's use or the key's permissions accordingly.

Type: OpenClaw Skill Name: starling-home-hub Version: 1.0.2 The skill is classified as suspicious primarily due to the default use of `curl -k` (disabling TLS certificate verification) in `scripts/starling.sh` when connecting to the Starling Home Hub via HTTPS. While this is explicitly documented in `SKILL.md` and `starling.sh` as a practical compromise for self-signed certificates on a trusted local network, it introduces a Man-in-the-Middle (MITM) vulnerability. However, the skill also includes positive security practices such as input validation (`validate_id`), explicit warnings against passing API keys via CLI arguments, and setting `chmod 600` on sensitive snapshot files. There is no evidence of intentional malicious behavior like data exfiltration, unauthorized remote execution, or prompt injection attempts against the agent.