konnect-api-catalog
Diagnose and shape Konnect API Catalog APIs, versions, specs, implementations, and API packages before publication. Use when Catalog readiness is the question, not when the real owner is Dev Portal publication, app auth, or gateway delivery.
Install
With your agent
Install OMGSkills skill "kong/ai-marketplace:plugins/kong-konnect/skills/konnect-api-catalog" 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-api-catalog ~/.claude/skills/konnect-api-catalogFrom README
Konnect API catalog workflow Goal Help an operator create, shape, and troubleshoot Catalog APIs and API packages before they become a Dev Portal publishing or consumer-access problem. Own Catalog readiness diagnosis and object modeling for APIs, versions, specs, documentation, implementations, and packages. Do not absorb Dev Portal publication, app auth, or declarative delivery workflows beyond clear handoffs. Tool Selection Use the shared kong-konnect MCP server first for live inspection of APIs, versions, specs, documents, implementations, packages, and portal publications. Prefer Catalog-oriented MCP reads before changing config. Useful live surfaces include API, version, implementation, package, and publication listings. Preserve the repository's chosen declarative toolchain when catalog objects need to change: use terraform-konnect for HCL-managed Catalog resources and kongctl-declarative only when the repo already manages the surrounding Konnect workflow that way.