konnect-api-publish
Operate Konnect API publication from managed API through Catalog and Dev Portal. Use when an API should be visible but the missing link is Catalog readiness, portal publication, or audience scoping. Not for Catalog modeling or post-publication app auth.
Install
With your agent
Install OMGSkills skill "kong/ai-marketplace:plugins/kong-konnect/skills/konnect-api-publish" 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-publish ~/.claude/skills/konnect-api-publishFrom README
Konnect API publish workflow Goal Help an operator trace why an API is not reaching the intended developer audience, from managed API presence through catalog readiness and portal publication. Use workflow language: inspect, trace, publish, validate, and approve. Do not turn this into generic Portal documentation. This skill owns publication-chain diagnosis, not generic Catalog authoring or developer application auth design. Tool Selection Use the shared kong-konnect MCP server first for live inspection of managed API, catalog, and portal state. Use kongctl-query for read-only checks on API, portal, and adjacent resources. Preserve the repository's chosen declarative toolchain when publication resources need to change: prefer kongctl-declarative for kongctl YAML, terraform-konnect for HCL-managed Konnect resources, and deck-gateway only when the missing link is in Gateway-entity config within the target control plane.