/btp-destination-diagnose
Optional runtime context such as Cloud Foundry, Kyma, BAS, or local development
$ npx -y skills add secondsky/sap-skills --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/btp-destination-diagnose
Context preview
What this command does when you run it.
Optional runtime context such as Cloud Foundry, Kyma, BAS, or local development
Command definition
btp-destination-diagnose.mdname: btp-destination-diagnose
description: Diagnose SAP BTP destination and Cloud Connector issues using configuration checks and safe troubleshooting steps
allowed-tools:
- Read
- Grep
- Glob
- Bash
argument-hint: "<destination-name-or-error> [cf|kyma|bas|local]"
arguments:
- name: destination
description: Destination name, error text, or scenario to diagnose
required: true
- name: runtime
description: Optional runtime context such as Cloud Foundry, Kyma, BAS, or local development
required: falseBTP Destination Diagnose
Diagnose a destination or Cloud Connector connectivity problem. Do not modify tenant configuration by default.
Workflow
1. Identify destination type, authentication mode, proxy type, runtime, subaccount, and target host. 2. Inspect local application destination usage, environment bindings, and destination service configuration snippets. 3. Check common failure classes: DNS, trust, principal propagation, OAuth, HTML5 app routing, Cloud Connector mapping, and timeout. 4. Suggest safe read-only CLI or curl checks when credentials are already configured. 5. Mark tenant-only verification as pending when live access is not available.
Output Contract
Return:
- Probable root cause ranked by evidence.
- Configuration fields to inspect.
- Read-only diagnostics to run.
- Fix plan with tenant owner actions separated from code changes.
- Verification checklist.
Read more
name: btp-destination-diagnose
description: Diagnose SAP BTP destination and Cloud Connector issues using configuration checks and safe troubleshooting steps
allowed-tools:
- Read
- Grep
- Glob
- Bash
argument-hint: "<destination-name-or-error> [cf|kyma|bas|local]"
arguments:
- name: destination
description: Destination name, error text, or scenario to diagnose
required: true
- name: runtime
description: Optional runtime context such as Cloud Foundry, Kyma, BAS, or local development
required: falseBTP Destination Diagnose
Diagnose a destination or Cloud Connector connectivity problem. Do not modify tenant configuration by default.
Workflow
1. Identify destination type, authentication mode, proxy type, runtime, subaccount, and target host. 2. Inspect local application destination usage, environment bindings, and destination service configuration snippets. 3. Check common failure classes: DNS, trust, principal propagation, OAuth, HTML5 app routing, Cloud Connector mapping, and timeout. 4. Suggest safe read-only CLI or curl checks when credentials are already configured. 5. Mark tenant-only verification as pending when live access is not available.
Output Contract
Return:
- Probable root cause ranked by evidence.
- Configuration fields to inspect.
- Read-only diagnostics to run.
- Fix plan with tenant owner actions separated from code changes.
- Verification checklist.
40 SAP development plugins with evidence-tracked verification SAP development plugins for AI coding assistants, with public-source or package-registry verification tracked where available.
Repo: secondsky/sap-skills
Other commands on sap-skills.
- /abap-cds-model-check
Optional intended usage such as analytical, transactional, reuse, value-help, or extraction
Open command - /abap-cloud-review
Optional target ABAP platform or SAP BTP ABAP Environment release
Open command - /ai-core-deployment-check
Optional runtime or scenario name, such as orchestration, serving, training, or batch
Open command - /api-style-review
Optional API style lens such as REST, OData, OpenAPI, or SDK
Open command - /btp-architecture-review
Optional scenario lens such as extension, integration, analytics, or AI
Open command - /work-zone-content-check
Optional Work Zone edition or content type
Open command

