UniFi Network Consoles

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Muse Home Link and a compatible physical device are required to USE this skill, not to install it: installing the skill file itself needs no account, no key and no device, and this install does NOT set up Home Link, pair anything or ask for any credential. But the skill is instructions only. To use it I must read and follow ~/docs/devices/home_link.md in my Muse environment, have the compatible physical device named below already set up on my local network, and have an existing local UniFi Network controller/console on my local network with an authorized local controller account/session (read-only access where available), the correct controller API family and trusted TLS identity, and my permission to inspect network inventory, knowing client names, identifiers and activity are private household data that must not be exposed beyond my request. This skill is read-only: it makes no network configuration changes. Installing the file configures none of that. Install "UniFi Network Consoles" for me. It inspects read-only network inventory and status through an existing local UniFi Network controller using Muse Home Link, over an authorized compatible HTTPS API for the intended site; it is not network configuration or client blocking. It is used when the home has an existing local UniFi Network controller/console with a compatible authenticated HTTPS API: console/controller product, UniFi OS and Network application versions are confirmed using the authorized local endpoint, and the requested site is identified before enumerating its devices or clients — a UniFi access point alone is not necessarily the controller. It needs an existing authorized local controller account/session with read-only access where available, the correct controller API family and trusted TLS identity (cloud SSO/account access is not assumed) and my permission to inspect network inventory, because client names, identifiers and activity are private household data. It uses a version-compatible local API client and authentication flow — legacy controllers commonly use /api, UniFi OS commonly proxies Network requests under /proxy/network/api — confirming the deployed version rather than probing arbitrary variants; it authenticates over the local HTTPS service, preserving cookies/tokens and any required CSRF handling without logging them, enumerates authorized sites, then requests documented device/client/status reads for the selected site (community methods include site listing and stat/device or stat/sta reads under that API's site route). It handles pagination and offline/stale records, reports the controller's observation time and distinguishes connected clients from historical inventory, and it checks API-level success/error metadata, authorization scope and returned site identity: a controller record is not proof that a client is currently reachable or that its smart-home control interface works. Limits: this is a read-only skill — no restart, adoption, blocking/unblocking, port, Wi-Fi, firewall or network configuration changes; no assumed cloud SSO, new controller deployment, guessed private endpoints or official-support claim; and raw client inventories are never exposed beyond my request. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-unifi-network-consoles/ folder at the pinned commit: SKILL.md only, 1 file) Pinned version: install the code at commit e6fe5174092702ffddae6f90759a38d55a4ebae1 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/facebookincubator/muse-gadget-sdk into a temporary folder, check out commit e6fe5174092702ffddae6f90759a38d55a4ebae1, and copy the skills/gadget-unifi-network-consoles/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 f28be16642c0092f9023a952c5aa6cca815f8f75bcb624f3be4a103382ecdffc If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (2 571 bytes). There is no script, no code and no configuration in it; the procedure runs at use time through Muse Home Link against my own local device. It has no dependency on any other gadget skill in this lot. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No device is contacted, no pairing is started and no key is asked for during installation. - At use time, exchanges go only to my local UniFi Network controller over its local HTTPS API: local authentication (cookies/tokens preserved, never logged) and documented read-only device/client/status reads for the site I selected. Client names, identifiers and activity are private household data and are never exposed beyond my request. No configuration write of any kind happens at use time. - The skill is read-only: it does no restart, adoption, blocking/unblocking, port, Wi-Fi, firewall or network configuration changes, assumes no cloud SSO, deploys no new controller, guesses no private endpoints and claims no official support. - Do not pair any device, do not ask for or set any credential, do not run any control, print, scan or playback action, and do not use the skill in any way during this install: Home Link setup, pairing and use are my decisions, later, when I actually ask for them. 3. When I say "yes, install", install it as a skill: copy the whole gadget-unifi-network-consoles folder into the agent's skills directory, in a folder named exactly "gadget-unifi-network-consoles", keeping its 1 file (SKILL.md at its root). The exact folder name matters: relative links between sibling gadget skills depend on these exact names. 4. Verify with no network calls: frontmatter valid (name: gadget-unifi-network-consoles), the 1 file in place with matching fingerprint. Do not run anything and do not connect to any device to verify. 5. Report what was installed, where, and what I still need to do myself (for example: read ~/docs/devices/home_link.md in my Muse environment and follow its Home Link rules; have an existing local UniFi Network controller with an authorized local account/session (read-only where available) and give my permission to inspect network inventory, knowing client inventory is private household data; this skill never changes network configuration; using the skill is a separate step that only starts when I ask for it, and the use-time exchanges disclosed above happen only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.