<!-- the config said isolated. the network said otherwise. -->

<p align="center"> <img src="./media/hero.png" alt="unifi-skills: agent skills for administering a real UniFi network" width="840"> </p>

<p align="center"> <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-00e5ff" alt="MIT license"></a> <a href="https://github.com/t3chnaztea/unifi-skills/releases"><img src="https://img.shields.io/github/v/release/t3chnaztea/unifi-skills?color=ff2e97" alt="Latest release"></a> <img src="https://img.shields.io/badge/skills-5-ffcc00" alt="5 skills"> <img src="https://img.shields.io/badge/deps-none-8a2be2" alt="No dependencies"> <img src="https://img.shields.io/badge/Claude%20Code-plugin-d97706" alt="Claude Code plugin"> </p>

<p align="center"> <b>Point a coding agent at a real multi-VLAN UniFi network without finding every trap yourself, at midnight, from the wrong side of a firewall rule.</b> </p>

> UniFi has a complete local API and almost no public documentation for it. It also has three overlapping API surfaces with different auth rules, endpoints that move between point releases without deprecation notices, and a habit of accepting configuration it does not actually apply. Point a coding agent at it without doctrine and you get changes that read back clean and did nothing, or a firewall zone that silently cuts your house off from its own DNS. This repo packages the doctrine as [Agent Skills](https://agentskills.io): focused, model-readable guides your coding agent loads on demand when you ask it to work on your network.

``` /plugin marketplace add t3chnaztea/unifi-skills /plugin install unifi@t3chnaztea-unifi ```

## The five skills

**Start with `unifi-connect`.** The others assume its auth lanes, its endpoint map, and its read-before-write doctrine.

<table> <tr> <td align="center" width="50%" valign="top"> <a href="skills/unifi-connect/SKILL.md"><b>🔌 unifi-connect</b></a><br /> <sub>Start here. Minting an API