Menu
Query, configure, and debug the local TP-Link Omada controller using its official OpenAPI and the omada CLI. Use for Omada sites, access points, switches, clients, adoption, connectivity, configuration, or controller health.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | omada |
| description | Query, configure, and debug the local TP-Link Omada controller using its official OpenAPI and the omada CLI. Use for Omada sites, access points, switches, clients, adoption, connectivity, configuration, or controller health. |
Use omada against https://omada.house.flakm.com. It discovers operations from the controller's OpenAPI specification, so do not guess operation names or parameters.
The controller must be initialized and an app must exist under Global View > Settings > Platform Integration > Open API using client mode. Grant the narrowest role and site privileges needed.
Credentials must come from OMADA_CLIENT_ID and OMADA_CLIENT_SECRET. Never put the secret in commands, chat, source files, or output. Use OMADA_BASE_URL=https://omada.house.flakm.com and OMADA_SSL_VERIFY=true.
omada auth to verify access.omada list, optionally with --tag, to find the operation.omada schema <operationId> before invoking it.omada <operationId> with parameters derived from the schema.Prefer read operations. Before create, update, delete, adopt, reboot, upgrade, block, or disconnect operations, explain the impact and obtain user confirmation unless the user explicitly requested that exact mutation.
omada auth
omada list --tag Device
omada schema getGridActiveClients
omada getGridActiveClients
omada getGridKnownClients --page-size 1000 --search-key "printer"
Refresh cached metadata after controller upgrades or site changes:
omada spec refresh
omada sites refresh
Use Chrome DevTools against https://omada.house.flakm.com when OpenAPI does not expose a UI-only operation or when debugging browser/network behavior.
Jira operations via the `jira` CLI (jira-cli-go): list/view/create/edit/transition issues, manage sprints, epics, and boards. Use when: (1) listing or searching Jira issues, (2) viewing issue details, (3) creating or updating issues, (4) transitioning issue status, (5) managing sprints or boards. NOT for: bulk imports, Jira admin, or webhook configuration.
Summarize Maciek's recent work across Jira and GitHub. Use when asked: 'what did I do today/this week', 'standup summary', 'work summary', 'weekly report', 'what have I been working on'. Combines Jira issue activity with GitHub PR/commit history for a unified view.
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).