omada-skill

TRIGGER when an internal support operator wants a tier-1 ticket draft for an Omada site issue, with evidence (site overview, device detail, recent alerts, audit trail) attached automatically. TRIGGER for "draft a ticket for the outage on `site-042`" / "put together an incident summary for oc-abc between 2 PM and 4 PM" / "who changed config on `site-hq` this morning, and what broke?". TRIGGER when the request asks for a compile-it-for-me artefact, not an interactive diagnosis. SKIP for live root-cause investigation — use `omada-wifi-troubleshoot` or `omada-alert-triage` first. SKIP when the operator wants to *act* (reboot / upgrade / rebind) — the matching write skill. SKIP for multi-site MSP KPI reports — use `omada_exec_report` directly.

TRIGGER when an MSP or SI operator wants to grind through a batch of Insight / Service alerts on an Omada site — group them, prioritise them, and draft ticket-ready summaries backed by device detail and topology. TRIGGER for "what's wrong at site X right now?" / "triage the last 24h of alerts on oc-abc:site-042" / "which AP is responsible for the red bar on the dashboard?". TRIGGER when alerts mention `Device`, `Client`, or `System` modules and the operator needs a signal-grouped view, not a raw log dump. SKIP for single-alert investigations where the operator already knows the device — use `omada_device_detail` directly. SKIP for config audit trails (who changed what, when) — use `omada-support-assist`. SKIP for pure capacity / Wi-Fi health questions — use `omada-wifi-troubleshoot`.

TRIGGER when the operator wants to stand up multiple Omada customer sites from a shared site-template — consistent SSIDs, VLANs, and device-template bindings — in one workflow. TRIGGER when an MSP is onboarding a new batch of stores, branches, or tenants and asks to "roll out", "provision", "clone", or "replicate" a site configuration across N locations. TRIGGER when a request mentions `batchSiteImport`, `bindSiteTemplate`, a backup file server (FTP/SFTP/TFTP/SCP), or a list of sites that should end up identical. SKIP for single-site changes — use the site UI or a targeted tool. SKIP for read-only queries like "list my sites" — use `omada_list_sites` directly. SKIP for firmware-only rollouts — use `omada-support-assist` + `omada_firmware_rollout`.

TRIGGER when an SI operator wants to stand up a branded Omada captive portal (guest Wi-Fi splash page) end-to-end — collect requirements, assemble the PortalSetting payload, and run the two-phase handshake to create it via `addPortal`. TRIGGER for "spin up a guest Wi-Fi portal on site X with our corporate logo and terms" / "add a voucher-auth portal to the lounge SSID" / "roll out the same portal across these sites". TRIGGER when the request mentions `authType`, `portalSetting`, `voucher`, `landing page`, or references a brand book. SKIP for changes to an existing portal — edit via the controller UI or a future update-portal tool. SKIP for SSID-level changes that don't involve a portal — use `omada_apply_site_template` directly. SKIP for MSP-wide rollouts of new sites — use `omada-bulk-site-onboard`, then run this skill per site.

TRIGGER when a prosumer / SI operator asks "why is my Wi-Fi slow?" on an Omada site and wants a fixed diagnostic playbook — site-wide health signals, per-client journey, per-AP detail — without chasing individual API calls. TRIGGER for "Wi-Fi is unstable at `site-home`" / "client X keeps roaming" / "AP Living-Room looks overloaded". TRIGGER when the operator mentions `retryRate`, `airtime`, `roaming`, `poor signal`, or asks for an AP/client health snapshot. SKIP when the question is purely about alerts in the last N hours — use `omada-alert-triage`. SKIP for writes (reboot, firmware, portal) — hand off to the matching write skill once root-cause is clear. SKIP for multi-site MSP reports — use `omada_exec_report` directly.