konnect-event-gateway
Use when diagnosing Konnect Event Gateway request flow across listeners, hostname mapping, virtual/backend clusters, auth, and policy evaluation. Exclude generic gateway health, org access control, and declarative implementation after the failing hop is known.
Install
With your agent
Install OMGSkills skill "kong/ai-marketplace:plugins/kong-konnect/skills/konnect-event-gateway" 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-event-gateway ~/.claude/skills/konnect-event-gatewayFrom README
Event Gateway operator workflow Goal Troubleshoot Event Gateway using its own entity model instead of forcing it into standard gateway assumptions. Default to following the request path end to end: client -> listener -> virtual cluster -> backend cluster -> policy and auth Own the diagnosis of the failing Event Gateway hop. Hand off implementation or non-Event-Gateway platform problems once that hop is clear. Tool Selection Use the shared kong-konnect MCP server first for live Event Gateway inspection. Use kongctl-query for read-only resource checks and concise summaries where the CLI surface is available. Preserve the repository's chosen declarative toolchain when Event Gateway resources need to change. Prefer kongctl-declarative for kongctl YAML and terraform-konnect when the required Event Gateway resources are already managed in HCL.