konnect-observability-triage
Diagnose missing, partial, delayed, or mis-scoped Konnect observability data across analytics, Explorer, and Debugger. Use when the question is dataset, scope, or telemetry visibility, not pure gateway health or operator-access troubleshooting.
Install
With your agent
Install OMGSkills skill "kong/ai-marketplace:plugins/kong-konnect/skills/konnect-observability-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-observability-triage ~/.claude/skills/konnect-observability-triageFrom README
Konnect observability triage Goal Explain why Konnect observability data is missing, partial, delayed, or scoped unexpectedly, and direct the operator to the right dataset and next action. Default to proving traffic and scope before concluding that observability is broken. This skill owns observability diagnosis, not generic gateway connectivity, portal publication, or operator-access troubleshooting. Tool Selection Use the shared kong-konnect MCP server for live inspection of the relevant Konnect surface when available. Use kongctl-query for read-only checks on organizations, control planes, APIs, and adjacent resources that determine where telemetry should appear. Preserve the repository's chosen declarative toolchain if the investigation turns into a configuration change rather than an observability diagnosis. Use konnect-access-scope when the problem is primarily who can see the data. Use konnect-gateway-triage when the real issue is no traffic or unhealthy gateway connectivity.