unifi-context-map
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 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).
Profile →npx skills add t3chnaztea/unifi-skills --skill unifi-context-map --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Read this before you write anything down
- Where to keep it
- Skeleton
- Building the inventory
- Reservation vs reality
- The Gotchas list
- Provenance: keeping it honest
- What not to put in it
udm networks --json | python3 -c '
import json,sys
for n in json.load(sys.stdin):
udm devices --json | python3 -c '
for d in json.load(sys.stdin):
udm wlans --json | python3 -c '
for w in json.load(sys.stdin):
udm reservations --json | python3 -c '
for u in r: print(" ", u.get("name") or u.get("hostname"), u.get("fixed_ip"))'
udm zones --json | python3 -c 'What does the unifi-context-map skill do?
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 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).
How do I install it?
Run `npx skills add t3chnaztea/unifi-skills --skill unifi-context-map --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From t3chnaztea/unifi-skills, a repository with 24 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.