abap-cds-model-check
Optional intended usage such as analytical, transactional, reuse, value-help, or extraction
Deployment target: cf (Cloud Foundry), kyma, or local
$ npx -y skills add secondsky/sap-skills --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/cap-deployment-checklistContext preview
What this command does when you run it.
Deployment target: cf (Cloud Foundry), kyma, or local
name: cap-deployment-checklist
description: Pre-deployment validation checklist for CAP applications to Cloud Foundry, Kyma, or local environments
allowed-tools:
- Read
- Grep
- Glob
- Bash
argument-hint: "[cf|kyma|local]"
arguments:
- name: target
description: "Deployment target: cf (Cloud Foundry), kyma, or local"
required: falseReturn a deployment readiness checklist, blockers, environment assumptions, safe validation commands, and pending tenant/system checks. Default to read-only guidance and do not deploy or modify services.
Comprehensive pre-deployment validation checklist for SAP Cloud Application Programming Model applications.
**Validate**:
mbt validate mta.yaml
**Verify**:
cf services
**Build**:
mbt build -t ./mta_archives
**Deploy**:
cf deploy mta_archives/my-app_1.0.0.mtar
**Check**: 1. Logs: `cf logs <app> --recent` 2. Environment: `cf env <app>` 3. Services: `cf services`
**Check**: 1. HDI container deployed 2. Service binding correct 3. Database service running
# Login cf login -a <api-endpoint> # Build MTA mbt build -t ./mta_archives # Deploy cf deploy mta_archives/my-app_1.0.0.mtar # Check status cf apps
# Deploy database cds deploy --to sqlite:db/data.db # Start server cds watch
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
Optional intended usage such as analytical, transactional, reuse, value-help, or extraction
Optional target ABAP platform or SAP BTP ABAP Environment release
Optional runtime or scenario name, such as orchestration, serving, training, or batch
Optional scenario lens such as extension, integration, analytics, or AI