How to manage UniFi Protect cameras and NVR — view cameras, smart detections, recordings, snapshots, lights, sensors, Known Faces, and the Alarm Manager. Use this skill when the user mentions UniFi cameras, security cameras, NVR, recordings, motion detection, person detection, face recognition, Known Faces, snapshots, RTSP streams, floodlights, sensors, chimes, arming/disarming the alarm, or any UniFi Protect task.
Use this skill when reviewing or merging any community PR in unifi-mcp — even if the user just says "take a look at this PR" or "can we merge this." Covers the complete quality gate checklist (f-string logger ban, Ruff lint enforcement, validator registry registration, doc site update ordering), the fork-edit model for trusted contributors, org-fork push limitations, the dual-subagent review pattern, PR body standards, technical API validation (live smoke tests, mutating cycles), DISPATCH_ARG_TRANSLATORS registration for action tools, the unresponsive-first-time-contributor fork-edit exception for trivial fixes, and the close-and-redirect pattern for unsalvageable PRs. Apply this skill before approving any externally-authored PR, before running the merge command, and when auditing recently merged PRs for compliance.
Apply this skill when managing external community engagement in unifi-mcp: setting up GitHub health files and issue routing infrastructure, designing or updating bug report templates, triaging incoming bug reports with an evidence-first protocol, scoping follow-up comments in open issues, and unblocking contributor PRs stalled on trivial CI failures. Activates for any task touching .github/ISSUE_TEMPLATE/, .github/config.yml, CONTRIBUTING.md, or SUPPORT.md, or when reviewing external contributor PRs — even if the user doesn't explicitly ask for community workflow guidance.
Apply this skill whenever modifying, debugging, or extending UniFi client data retrieval in the unifi-mcp monorepo — even if the user doesn't explicitly ask about correctness or fallback behavior. Covers five permanent architectural fixtures of clients.py: (1) choosing the right endpoint (/stat/sta for live clients, /rest/user for offline or historical only); (2) preserving name and hostname as independent fields rather than collapsing with "or"; (3) deriving online status via the _is_online() uptime-field fallback when is_online is absent from the payload; (4) building a resilient fallback chain that never re-raises transient endpoint errors; (5) merging dual-source raw payloads with live data winning on overlapping keys. Verified against a live UDM SE controller (UniFi OS 5.1.12 / Network App 10.3.58): 0/180 active clients carry is_online; 121/445 clients have name and hostname set to different values.
How to manage UniFi network infrastructure — devices, clients, firewall, VPN, routing, WLANs, and statistics. Use this skill when the user mentions UniFi, Ubiquiti, network management, WiFi configuration, firewall rules, port forwarding, VPN, QoS, bandwidth, connected clients, network devices, or any UniFi networking task.
Use this skill when adding any tool that talks to the UniFi public Integration API (X-API-Key auth, /proxy/network/integration/...). The integration API uses a different ID namespace and field schema from the V2 controller API, so these tools form their own "families" with scoped IDs. Covers when to start a new family vs join an existing one, how to scope IDs in tool descriptions, the narrow conditions under which silent ID translation is allowed (rare), how to wire auth, and how to bridge between ID spaces (explicit named bridging tools only). Applies whether you are adding a read tool, a mutation tool, or a paired family of both.
Manage UniFi firewall policies using natural language — create, modify, and review firewall rules, content filters, and traffic policies. Use when asked to block traffic, create firewall rules, manage content filtering, set up time-based access controls, or review firewall configuration.
Activate this skill whenever you need to extend, maintain, or debug the two-tier tool discovery system — even if the user doesn't explicitly ask about "tool discovery." This covers: adding or modifying parameters on the tool discovery layer in `tool_index.py` (including the critical FastMCP named-param wrapper pattern vs. the silent `args: dict` trap), implementing or adjusting the compact-vs-full schema tiers (`include_schemas` flag, token-count rationale), keeping the Worker cloud path in parity with local `tool_index` changes, updating `plugins/*/skills/*/SKILL.md` runtime manifests after any parameter or behavior change, and preserving the one-unified-server architecture. Also applies to future MCP spec issue #2211 (`max_response_bytes`) alignment.