konnect-platform-router
Route broad or ambiguous Konnect requests to the first owning specialist skill. Use when multiple Konnect surfaces are involved or the right owner is unclear, not when the user already named a specific workflow, toolchain, or non-Konnect task.
Install
With your agent
Install OMGSkills skill "kong/ai-marketplace:plugins/kong-konnect/skills/konnect-platform-router" 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-platform-router ~/.claude/skills/konnect-platform-routerFrom README
Konnect platform router Goal Turn broad Konnect requests into one primary downstream skill with a clear next step and one concrete thing that skill should prove next. Use this skill as a classifier and handoff layer. Do not turn it into a product guide or a second copy of specialist workflows. Shared Operating Defaults Prefer the shared kong-konnect MCP server when the request depends on live Konnect state. If kong-konnect MCP is unavailable, say so early and continue with kongctl-query, repository artifacts, logs, or user-provided state. Preserve the repository's existing declarative toolchain. Do not convert the user between decK, kongctl, and Terraform unless they ask. Prefer current live state and current product docs over stale assumptions when behavior, product coverage, or limits may have changed. When a downstream CLI appears blocked by the agent environment, let the specialist tool skill handle sandbox retry guidance instead of classifying it as a product failure here.