Terminal
Terminal/Skill
Guides writing kongctl YAML for Konnect and running plan, diff, apply, adopt and CI/CD workflows.
By Kong
Works with
npx skills add kong/ai-marketplace --skill kongctl-declarativeAuthor, update, review, and execute kongctl declarative configuration for
Konnect without drifting into read-only query work or a different declarative
toolchain.
kongctl YAML, _defaults.kongctl, or kongctl plan/apply workflows, or
when the user explicitly asks for kongctl.kong-konnect MCP server first when the task depends on live
Konnect state and MCP is available.kongctl-query for read-only inspection, exact get syntax, output
shaping, or CLI-shaped proof that should not mutate state.decK or Terraform repositories to kongctl unless the user explicitly asks.Load only the branch that matches the task:
references/commands.md
references/resources.md
_defaults, parent versus child metadata,
!file, !ref, and schema discovery.references/apiops-openapi.md
apis resources from OpenAPI.references/cicd-github-actions.md
references/troubleshooting.md
This skill must stay portable across repositories. Do not assume the upstream
kongctl repo layout or a local docs/ tree.
Before editing manifests or proposing execution:
kongctl rather than decK or Terraform.kongctl get organization -o json.!file usage will
require --base-dir.Use the smallest preview surface that matches intent:
diff or inline --dry-run!ref
values, and !file boundary issues before mutationapply, sync, or delete only after a plan, diff, or --dry-run
preview and the user confirms that previewed change in the conversation.adopt, preview through read-only inspection of the target and its
labels, state the exact label change, and wait for conversation confirmation.
Using --overwrite-namespace needs its own confirmation.After a requested mutation:
kongctl-based inspection as the fallback.sync and delete as destructive. Follow the Preview and Execute
gates for every live mutation.adopt only for existing unmanaged parent resources. adopt labels the
resource for namespace ownership; it does not rewrite the resource fields.!file
extraction and !ref links over copied literals or hard-coded UUIDs.!file paths and --base-dir within the repository that owns
the declarative config. Never use absolute paths that leave the repository
or symlinks that escape it, or reference credential, key, or env files.--recursive declarative tree. If a
directory mixes resource YAML with specs or docs, target specific files
instead of the whole tree.kongctl command appears blocked by the agent sandbox rather
than by Konnect or the CLI, ask the user to run it or approve a retry outside
the sandbox before diagnosing the command itself as broken._defaults.kongctl,
apis, portals, control_planes, or related kongctl resource keys
instead of assuming konnect/resources/.references/resources.mdreferences/apiops-openapi.mdreferences/commands.mdreferences/cicd-github-actions.mdBefore answering, verify that you can state:
kongctl is the correct implementation owner for this requestkongctl-query should provide read-only follow-up proofkongctl-query when the real task is read-only inspection, auth
checking, exact get syntax, or output formatting.deck-gateway, terraform-konnect, or
terraform-kong-gateway when the repository already uses those tools for the
target resources.konnect-platform-router when the workflow owner is unclear, if the user
first needs diagnosis or classification rather than declarative
implementation.