Comprehensive SAP Business Technology Platform (BTP) reference for cloud development, deployment, and operations. Use when setting up BTP accounts, working with Cloud Foundry environment, deploying to Kyma (Kubernetes, serverless), developing in ABAP environment (RAP, CDS), managing entitlements and quotas, configuring identity providers (XSUAA), using btp CLI or CF CLI, deploying multi-target applications (MTA), setting up connectivity (destinations, Cloud Connector), implementing CI/CD pipelines, extending SAP solutions, or troubleshooting BTP services. Covers all three runtime environments.
npx skills add https://github.com/secondsky/sap-skills --skill sap-btp-cloud-platform
Use this skill when setting up or operating SAP BTP accounts, directories, subaccounts, Cloud Foundry, Kyma, ABAP Environment, entitlements, quotas, role collections, CLI tooling, MTA deployments, connectivity, CI/CD, extensions, or platform troubleshooting.
btp and cf CLI examples in Tools for repeatable setup.sap-cap-capire, sap-fiori-tools, sap-btp-connectivity, or sap-btp-service-manager.Comprehensive reference for SAP Business Technology Platform covering all runtime environments, account management, security, and operations.
Documentation Source: https://github.com/SAP-docs/sap-btp-cloud-platform
SAP Help Portal: https://help.sap.com/docs/btp
SAP Discovery Center: https://discovery-center.cloud.sap/
SAP BTP integrates five technology portfolios: Application Development, Process Automation, Integration, Data & Analytics, and AI. Provides suite qualities: SAP Fiori UX, Cloud Identity Services, Master Data Integration, embedded analytics, SAP Task Center, and SAP Cloud ALM.
Global Account → Directory (optional) → Subaccount (region-specific)
↓ CF: Org → Spaces
↓ Kyma: Cluster → Namespaces
↓ ABAP: System instance
SAP BTP offers four runtime environments at the subaccount level:
Open PaaS with polyglot support. Features: multiple buildpacks (Java, Node.js, Python, Go, PHP), spaces for separation, auto-scaling, SAP HANA integration.
cf login -a https://api.cf.<region>.hana.ondemand.com
cf push my-app
cf bind-service my-app my-service-instance
Structure: Subaccount → Org (1:1) → Spaces
Managed Kubernetes runtime based on open-source Kyma.
Structure: Subaccount → Cluster (1:1) → Namespaces
Cloud ABAP development with RAP, CDS, SAP Fiori integration, ADT, 1:1 SAP HANA database per system.
Use Cases: Extend S/4HANA Cloud, build new cloud applications, transform ABAP custom code
Status: Sunsetting December 31, 2028. Recommendation: Migrate to CF/Kyma.
Access all eligible services with flexible usage. Flavors: SAP BTPEA, CPEA, Pay-As-You-Go. Benefits: Switch services on/off, access current and future services.
Fixed cost for selected services, pay irrespective of consumption. Additional services require contract modification.
Best Practice: Use consumption-based for pilots, subscription for stable workloads.
Global Account → Directory (reserves) → Subaccount (consumes) → CF Space (optional)
| Provider | Examples |
|----------|----------|
| SAP | eu10, us10, ap10 |
| AWS | eu10, us10, ap10, ap11, ap12 |
| Azure | eu20, us20, ap20, jp20 |
| Google Cloud | us30, in30 |
| Alibaba Cloud | cn40 |
Multi-AZ deployment for high availability:
| Type | Description | Example |
|------|-------------|---------|
| Platform Users | Manage BTP infrastructure | Developers, administrators |
| Business Users | Use deployed applications | End users, customers |
| Provider | Use Case |
|----------|----------|
| SAP ID Service | Default, SAP community users |
| SAP Cloud Identity Services | Recommended for production |
| Corporate IdP | Via Identity Authentication proxy |
Identity Provider
↓
SAP BTP (Shadow Users)
↓
Role Collections
↓
Application/Service Access
# btp CLI
btp login --url https://cpcli.cf.<region>.hana.ondemand.com
btp list accounts/subaccount
btp create accounts/subaccount --display-name "Dev"
btp assign security/role-collection "Subaccount Administrator" --to-user [email protected]
# CF CLI
cf login -a https://api.cf.<region>.hana.ondemand.com
cf target -o my-org -s my-space
cf push my-app
cf bind-service my-app my-service
# kubectl
kubectl get pods -n my-namespace
kubectl apply -f deployment.yaml
kubectl logs -f deployment/my-app
Recommended: Corporate IdP → SAP Cloud Identity Services → SAP BTP
XSUAA provides OAuth 2.0 authorization, role-based access control, and application security descriptors (xs-security.json).
Connect to remote systems without hardcoding URLs. Key authentication methods:
NoAuthentication (public APIs)OAuth2ClientCredentials (service-to-service)OAuth2SAMLBearerAssertion (user propagation)PrincipalPropagation (on-premise with Cloud Connector)Secure tunnel for on-premise connectivity with no inbound firewall ports, fine-grained access control, RFC/HTTP support, and principal propagation.
Package multiple modules for deployment. Core structure includes modules (app types: nodejs, html5) and resources (services like hana).
Single entry point providing static content serving, user authentication, URL rewriting, and request forwarding to microservices.
Managed service supporting Cloud Foundry apps (Fiori, CAP), SAP Fiori for ABAP Platform, and SAP Integration Suite artifacts.
Build loosely coupled extensions: SAP Solution → APIs & Events → SAP BTP Extension → Custom Business Logic
For detailed guidance, see the 13 reference files:
references/glossary.md - Complete terminology (40+ terms)references/cloud-foundry.md - CF development and administrationreferences/kyma.md - Kyma runtime and Kubernetes patternsreferences/abap.md - ABAP environment, RAP, CDSreferences/security.md - Authentication, authorization, identityreferences/connectivity.md - Destinations, Cloud Connectorreferences/development.md - Development patterns, MTA, Application Routerreferences/administration.md - Account management, btp CLIreferences/operations.md - Monitoring, alerting, loggingreferences/extensions.md - SAP solution extensions, formationsreferences/tools.md - CLI references, development toolsreferences/troubleshooting.md - Common issues and solutionsreferences/regions-endpoints.md - Region-specific API endpointsLast Verified: 2025-11-27
Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.
Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.
Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).
This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.
Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.
Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.
Take secondsky/sap-btp-cloud-platform from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.