← ClaudeAtlas

unifi-context-maplisted

Use when an agent keeps guessing wrong about a UniFi network, when starting recurring agent work against a gateway, or when asked to "map my network", "document my UniFi setup", "build a network inventory", "what's on my network", "why does the agent keep using the wrong AP", or "audit my reservations against reality". Covers writing and maintaining the site map file: networks, devices, SSIDs, reservations, zones, an append-only Gotchas list, provenance checks that keep it honest, and the security rules for a file that is a burglary aid if it leaks. Assumes unifi-connect. Not for making changes to any of it (unifi-firewall, unifi-wifi, unifi-clients).
t3chnaztea/unifi-skills · ★ 39 · Data & Documents · score 81
Install: claude install-skill t3chnaztea/unifi-skills
# UniFi Context Map This repo deliberately ships no network inventory, because the useful one is yours. This skill is how the agent builds it. An agent working a UniFi network without a map guesses: which AP is the one in the back bedroom, whether `10.x.x.50` is the NAS or a decommissioned print server, whether that camera reservation reflects where the camera actually is. UniFi answers with MAC addresses and machine names, and it is confidently wrong in a specific way: **the config is not the operational reality.** A reservation exists whether or not the device honors it. A port override is stored whether or not the hardware enforces it. One markdown file, one human pass, fixes this. ## Read this before you write anything down **A complete UniFi map is a burglary aid.** Not being dramatic: assembled in one file it contains camera names and their physical placements, which cameras are on which segment, your WAN address, the MAC address of every device in the building, your alarm panel's IP, and which SSID is the trusted one. That is a casing document with a network diagram attached. So, before the first line: - **Never commit it to a public repo.** Not "scrub it later". Git history is forever and the scrub is always harder than you think. - **`.gitignore` it by name** in whatever repo you do network work from. A suggested pattern is in this repo's `.gitignore`. - **Never paste it into a shared or third-party context** you do not control. - **The API key never goes