Terminal
Terminal/Skill
Traces why a Konnect API is not reaching its intended Dev Portal audience, from managed API through Catalog to publication.
By Kong
Works with
npx skills add kong/ai-marketplace --skill konnect-api-publishHelp 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.
kong-konnect MCP server first for live inspection of
managed API, catalog, and portal state.kongctl-query for read-only checks on API, portal, and adjacent
resources.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.konnect-api-catalog when the real problem is API object
modeling, versioning, specification quality, or package readiness rather
than publication.konnect-app-auth once publication is proven and the remaining
issue is developer registration, approval, credential issuance, or auth
strategy selection.kong-konnect MCP is not connected, say
so early and continue with CLI or user-provided artifacts.Default to read-first inspection. Only move to mutation when the missing link in the publication chain is understood.
Load only the reference file that matches the active branch:
references/publication-chain.md
references/portal-visibility-vs-access.md
references/downstream-auth-handoffs.md
Clarify what "not published" means:
Do not use one answer path for all of these. Capture which portal, audience, or viewer is expected to see or use the API before you inspect publication state.
If the operator uses "publish" loosely, load references/publication-chain.md
and classify the missing stage before proposing any fix.
Start with the operator source objects:
If the API object or version does not exist, do not continue to portal debugging yet.
Verify:
Separate "API is published somewhere" from "API is published to the portal and audience the operator means."
Use references/publication-chain.md when the managed-API-to-catalog boundary
is still unclear.
Do not collapse these into one failure:
Load references/portal-visibility-vs-access.md when the main question is
whether the intended audience should actually see or discover the API.
This is where many "publish" issues become access or onboarding issues.
Load references/downstream-auth-handoffs.md when registration, approvals,
credentials, or auth strategy become the real blocker.
Diagnose one primary break:
Before answering, verify that you can state:
konnect-api-catalogkonnect-api-catalog when the missing step is API creation, versioning,
spec quality, implementation/package modeling, or other upstream Catalog
readiness work.konnect-app-auth when publication is present but developer
registration, approvals, credentials, or auth strategy still block use.kongctl-declarative or terraform-konnect when the user wants to
create or update APIs, portals, or related publication resources as code.deck-gateway when the publication issue is downstream of missing or
stale Gateway-entity config inside the control plane.konnect-access-scope when the API likely exists but the caller cannot
see or administer it.kongctl-query for exact read-only command syntax during investigation.