From kong-konnect
Manage Kong Gateway entities with decK. Use for `deck gateway` state files, validate/diff/sync/dump workflows, OpenAPI-derived Gateway config, or GitOps-style Gateway entity repos. Do not use for Konnect platform resources or HCL/kongctl repos.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kong-konnect:deck-gatewayThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate, inspect, and apply Kong Gateway entity configuration with `decK`
Generate, inspect, and apply Kong Gateway entity configuration with decK
without losing track of live state, scope, or deployment model.
Use this skill for Gateway entities and Gateway-oriented GitOps. Do not use it
as a replacement for Konnect platform workflows that belong in kongctl or
Terraform.
kong-konnect MCP server first for live Konnect inspection
when the target Gateway entities live in Konnect and MCP is available.decK, _format_version,
or deck gateway commands, or when the user explicitly asks for decK.kongctl-query first when the real task is incident
diagnosis, live-state discovery, or Konnect inspection before a repo-owned
decK slice is identified.decK layout, file split, tags, and CI patterns in
the repository.kongctl repository to decK unless the user
explicitly asks for that migration.terraform-kong-gateway, terraform-konnect, or
kongctl-declarative when the user wants HCL or kongctl rather than
decK.Load only the reference file that matches the active branch:
references/command-paths.md
references/openapi-generation.md
references/state-shaping-and-tags.md
references/dump-diff-sync-safety.md
Before editing files or proposing a live sync:
deck is installed and runnable: deck versiondecK path.sync.deck gateway sync only when the user explicitly asked for mutation.sync aligned with the already previewed file, directory, tags, or
include boundary.deck gateway diff and expect no remaining intended
changes.decK as the source-controlled representation of Gateway entities, not
as proof that the live Gateway currently matches it.deck command appears blocked by the agent environment rather
than the live product or CLI itself, request an unsandboxed retry with
approval before assuming auth or command failure.deck gateway validate plus a scoped deck gateway diff as the
required preview surface before sync.decK files. decK is for Gateway
entities, not the full Konnect product surface.decK is the right answer for DB-less runtime loading,
identity or team management, or non-Gateway Konnect resources.decK shapeIdentify:
decK state filesdeck gateway diff, deck gateway sync, or wrapper scriptsMatch the existing conventions before adding new files or commands.
Pin down:
Do not treat platform resources such as teams, portals, or access rules as Gateway entities.
decK's native safety surfacePick the smallest decK path that answers the request:
Load references/command-paths.md when several decK paths could fit and you
need a sharper decision rule.
When editing state:
Load references/state-shaping-and-tags.md when the repo's split, tags, or
include boundaries are the main constraint.
deck gateway sync only when the user explicitly asked for live
mutation.Load references/dump-diff-sync-safety.md when the user needs a safer
inspection-first path or is about to use a broad dump/sync flow.
decKAfter any requested sync:
deck gateway diff and expect no remaining intended
changessync exit status alone as proof that the live Gateway now
matches the intended stateState:
decK is strongest for Gateway entities, not the broader Konnect platform.decK file in Git does not prove the live control plane matches it.sync runs can overwrite adjacent entity changes when file scope or
tag scope is too loose.decK for Gateway-entity workflows, but
the surrounding platform resources may belong in another tool.decK adds
unnecessary translation.Before answering, verify that you can state:
decK is the right tool for this repository or requestdeck preview commands prove the intended change safelyterraform-kong-gateway when the repository already manages
self-managed Gateway config in HCL.terraform-konnect when the repository already manages Konnect-hosted
Gateway entities or surrounding Konnect resources in HCL.kongctl-declarative when the task is really Konnect platform YAML
rather than Gateway-entity decK.kongctl-query or the relevant domain skill when the user first needs
live inspection rather than config authoring.npx claudepluginhub kong/ai-marketplace --plugin kong-konnectCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.