What problem does it solve?
The UniFi controller exposes two incompatible API surfaces (V2 controller API and Integration API) with different auth, ID namespaces, and field schemas. Mixing them causes silent failures where IDs from one API are passed to tools backed by the other. This Skill provides the rules for safely adding tools that talk to the UniFi Integration API.
Core Features & Use Cases
- Tool Family Boundaries: Defines how to decide whether a new tool joins an existing ID family or starts a new one, with the current firewall policy CRUD and ordering families as reference.
- ID Scoping Rules: Mandates scoping clauses in MCP tool, GraphQL, and REST descriptions so UUIDs from the Integration API are never confused with V2 Mongo ObjectIDs.
- Auth and Bridging Patterns: Requires X-API-Key auth checks with remediation messages, bans silent ID translation except the grandfathered zone case, and prescribes named bridging tools when cross-namespace lookup is genuinely needed.
- Use Case: When adding a new firewall policy ordering tool backed by the Integration API, follow the steps to scope its UUIDs, wire the API-key check in the manager, and add tests covering the family boundary.
Quick Start
Ask the agent to add a new UniFi Integration API tool following the add-integration-api-tool skill, specifying the endpoint and whether it reads or mutates resources.
