Kyma CLI
Manage an open-source Kyma module through its full lifecycle with the Kyma CLI (v3) - discover, enable, configure, verify, change managed state, and remove. Use when the user wants to enable, install, add, configure, or remove a Kyma module (e.g. Serverless, Istio, API Gateway), pick a module channel, or manage/unmanage a module.
Build and deploy an application to an open-source Kyma cluster with kyma app push (v3) - from local source, a Dockerfile, or a pre-built image, with exposure via APIRule, Istio injection, and env/secret/config injection. Use when the user wants to push, deploy, or expose an app on Kyma.
Diagnose a misbehaving open-source Kyma cluster or module using the Kyma CLI (v3) and kubectl. Use when a module is stuck or not ready, an app is failing, Istio or networking is broken, or the user wants to troubleshoot, diagnose, or inspect a Kyma cluster. Also use when kyma module add/delete itself is failing with an error. Do NOT use for pure module lifecycle tasks (add/enable/remove) where no problem is reported — e.g. "add the Istio module" with no error context → use kyma-module-lifecycle instead; "add the Istio module because sidecar injection is broken" → this skill applies for the diagnosis step.
Clean up a deployed SAP appFront (Application Frontend) application. Undeploys from Cloud Foundry (optionally deleting service instances and keys) and removes the local output folder if applicable. Every destructive step requires explicit user confirmation. Use when the user asks to clean up, remove, or tear down an appFront app.