What problem does it solve? Managing SAP BTP services across Cloud Foundry, Kyma, and Kubernetes requires juggling multiple CLIs, REST APIs, authentication methods, and rate limits, with errors like HTTP 429 throttling, failed provisioning, and missing binding credentials being common and hard to diagnose. ## Core Features & Use Cases - Service Lifecycle Management: Create, update, and delete service instances and bindings using SMCTL, BTP CLI, CF CLI, or the Service Manager REST API, with async operation status polling. - Kubernetes Service Operator Setup: Deploy the SAP BTP Service Operator with cert-manager, manage ServiceInstance and ServiceBinding CRDs, and migrate from legacy Service Catalog (svcat). - Authentication & Troubleshooting: Configure OAuth2 client credentials and X.509 certificate authentication, handle three-tier rate limiting, and resolve common provisioning failures. - Use Case: A platform engineer needs to provision an XSUAA instance in a Kubernetes cluster. The skill guides them through creating a service-operator-access instance, deploying the operator via Helm, and applying ServiceInstance and ServiceBinding YAML manifests. ## Quick Start Ask the assistant to provision a service instance on SAP BTP and create a binding for it using SMCTL or the BTP CLI.