konnect-gateway-triage
Use when triaging Konnect Gateway control-plane and data-plane failures such as disconnected planes, missing rollout, or wrong environment slices; separate attachment, network, live-state drift, and traffic-path failures before handing off fixes.
Install
With your agent
Install OMGSkills skill "kong/ai-marketplace:plugins/kong-konnect/skills/konnect-gateway-triage" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Kong/ai-marketplace /tmp/ai-marketplace && ln -s /tmp/ai-marketplace/plugins/kong-konnect/skills/konnect-gateway-triage ~/.claude/skills/konnect-gateway-triageFrom README
Konnect gateway triage Goal Reduce ambiguous "gateway is broken" reports into a concrete failing layer: control plane state, data plane registration, network path, config drift, or traffic behavior. Default to live inspection first. Use repo config only as intended state, not as proof of deployed behavior. Tool Selection Use the shared kong-konnect MCP server first for current control plane and data plane state. Use kongctl-query for concise, read-only checks when CLI output is easier to summarize or filter. Preserve the repository's chosen declarative toolchain for fixes and hand off once the failing layer is proven: deck-gateway for Gateway-entity decK repos, terraform-konnect for HCL-managed Konnect Gateway resources, terraform-kong-gateway for self-managed Gateway HCL, and kongctl-declarative for kongctl YAML. If live Konnect state matters and kong-konnect MCP is not connected, say so early and continue with CLI or user-provided artifacts.