Individual skill
aicore-lifecycle-management
Manage SAP AI Core lifecycle resources: scenarios, executables, configurations, and deployments. WHEN: user wants to list or inspect scenarios or executables, create or list configurations, create or list or stop or delete or patch deployments, get deployment logs, or remove duplicate LLM deployments. DO NOT USE FOR: listing foundation models or getting inference examples — use `genai-hub-foundation-models`; managing resource groups, secrets, or GitOps resources — use `aicore-admin-resources`.
plugins/aicore-skills/skills/aicore-lifecycle-management/SKILL.md
Source commit 82b27a81d972aa4f70dc6154605606cfed0b4772
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 146
- Repository last updated
- Nov 5, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,706 bytesSKILL.mdcore · 6,706 bytesSKILL.mdcore · 6,706 bytesSKILL.mdcore · 6,706 bytesSKILL.mdcore · 6,706 bytesSKILL.mdcore · 6,706 bytesSKILL.mdcore · 6,706 bytesSKILL.mdcore · 6,706 bytesSKILL.mdcore · 6,706 bytesSKILL.mdcore · 6,706 bytesscripts/create_configuration.pyruns · 4,492 bytesscripts/create_deployment.pyruns · 5,614 bytesscripts/dedup_deployments.pyruns · 6,034 bytesscripts/delete_deployment.pyruns · 4,883 bytesscripts/get_configurations.pyruns · 7,773 bytesscripts/get_deployment_logs.pyruns · 5,344 bytesscripts/get_deployments.pyruns · 14,435 bytesscripts/get_executables.pyruns · 7,919 bytesscripts/get_scenarios.pyruns · 6,531 bytesscripts/patch_deployment.pyruns · 2,488 bytesscripts/stop_deployment.pyruns · 3,900 bytes
Read excerpt
## Rules
1. Run all scripts from the skill root directory with `uv run scripts/<name>.py`.
2. Never print or log credential values — the SDK reads them from the environment.
3. Scripts that delete or mutate state require `--confirm`. Always pass it explicitly; never bypass it.
4. When the user does not specify a resource group, omit `--resource-group` so the SDK uses its configured default.
5. For LLM deployments: the scenario ID, executable ID, and model parameter names come from `genai-hub-foundation-models` — invoke it first if those values are unknown.
6. Deployment configuration naming convention: use `{executable_id}--{model_name}` for LLM deployments (e.g. `azure-openai--gpt-4o-mini`). Before creating a configuration, check whether one with that name already exists via `get_configurations.py --scenario-id <id>` and reuse it to avoid duplicates.
---
## List / Inspect Scenarios
```bash