konnect-access-scope
Troubleshoot Konnect operator access and visibility. Use when a user cannot authenticate, cannot see or edit a Konnect resource, may be in the wrong region, org, or team, or needs help with scoped roles or IdP-managed access. Not for Dev Portal app auth.
Install
With your agent
Install OMGSkills skill "kong/ai-marketplace:plugins/kong-konnect/skills/konnect-access-scope" 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-access-scope ~/.claude/skills/konnect-access-scopeFrom README
Konnect access and scope troubleshooting Goal Explain why an identity can or cannot reach a Konnect surface, see a resource, or mutate it, then identify the narrowest next step. Default to read-first inspection. Do not propose role or team changes until you have separated resource existence, endpoint selection, authentication, and authorization. Use this skill for operator or automation access to Konnect itself. Do not use it for downstream API consumer auth, Dev Portal application credentials, or Gateway runtime auth flows. Tool Selection Use the shared kong-konnect MCP server first for live inspection when it is available in the session. Use kongctl-query for read-only checks, identity inspection, and resource existence checks from the CLI surface. Preserve the repository's chosen declarative toolchain when access-adjacent resources need to be codified: prefer kongctl-declarative for kongctl YAML and terraform-konnect for HCL-managed Konnect resources.