MCPInstall

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.

Installs
88
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/sap/ai-skills-library --skill aicore-lifecycle-management
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads aicore-lifecycle-management automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

# List all scenarios
uv run scripts/get_scenarios.py

# Inspect a specific scenario and its versions
uv run scripts/get_scenarios.py --scenario-id <id>
uv run scripts/get_scenarios.py --scenario-id <id> --response-format detailed

# JSON output for piping
uv run scripts/get_scenarios.py --json

List Executables

# List executables for a scenario
uv run scripts/get_executables.py --scenario-id <id>

# Inspect a specific executable (includes parameters and input artifacts)
uv run scripts/get_executables.py --scenario-id <id> --executable-id <id>
uv run scripts/get_executables.py --scenario-id <id> --executable-id <id> --response-format detailed

# JSON output
uv run scripts/get_executables.py --scenario-id <id> --json

Parameters are only returned when inspecting a single executable (--executable-id). The list view returns id, name, and description only.


Configurations

# List configurations
uv run scripts/get_configurations.py
uv run scripts/get_configurations.py --scenario-id <id>
uv run scripts/get_configurations.py --response-format detailed
uv run scripts/get_configurations.py --json

# Inspect a specific configuration
uv run scripts/get_configurations.py --configuration-id <id>

# Create a configuration (binds parameters to an executable)
uv run scripts/create_configuration.py \
  --name my-config \
  --scenario-id <id> \
  --executable-id <id> \
  --param modelName=gpt-4o \
  --param temperature=0.7

If a deployment fails or stays PENDING after several minutes, verify parameter names and values against the executable's declared parameters:

uv run scripts/get_executables.py --scenario-id <id> --executable-id <id> --response-format detailed

Deployments

Deployments serve inference endpoints. The standard flow is: create (or reuse) a configuration, then create a deployment from it.

Configuration naming convention

Always check whether a matching configuration already exists before creating one, to avoid duplicates:

# Check existing configurations before creating
uv run scripts/get_configurations.py --scenario-id <scenario-id> --json | jq '.[] | select(.name == "<expected-name>")'

Naming convention:

  • LLM: {executable_id}--{model_name} — e.g. azure-openai--gpt-4o-mini
  • Orchestration: orchestration
  • Custom: choose a descriptive name

LLM deployment (from genai-hub-foundation-models handoff)

# 1. Create configuration (skip if one with this name already exists):
uv run scripts/create_configuration.py \
  --name azure-openai--gpt-4o-mini \
  --scenario-id foundation-models \
  --executable-id azure-openai \
  --param modelName=gpt-4o-mini \
  --param modelVersion=latest

# 2. Deploy:
uv run scripts/create_deployment.py --configuration-id <config-id> --wait

Orchestration deployment

# 1. Create configuration (skip if "orchestration" config already exists):
uv run scripts/create_configuration.py \
  --name orchestration \
  --scenario-id orchestration \
  --executable-id orchestration

# 2. Deploy:
uv run scripts/create_deployment.py --configuration-id <config-id> --wait --timeout 600

List and inspect deployments

# List all deployments
uv run scripts/get_deployments.py

# Filter by status or scenario or executable
uv run scripts/get_deployments.py --status RUNNING
uv run scripts/get_deployments.py --scenario orchestration
uv run scripts/get_deployments.py --executable-id azure-openai --status RUNNING
uv run scripts/get_deployments.py --executable-id azure-openai --status RUNNING --json

# Inspect one deployment
uv run scripts/get_deployments.py --deployment-id <id>
uv run scripts/get_deployments.py --deployment-id <id> --response-format detailed
uv run scripts/get_deployments.py --deployment-id <id> --json

Stop, patch, delete, logs

# Stop a deployment
uv run scripts/stop_deployment.py --deployment-id <id> --confirm
uv run scripts/stop_deployment.py --deployment-id <id> --confirm --wait

# Patch (swap configuration on a running deployment)
uv run scripts/patch_deployment.py --deployment-id <id> --configuration-id <new-config-id>

# Delete (must be STOPPED or DEAD first)
uv run scripts/delete_deployment.py --deployment-id <id> --confirm
# Stop and delete in one step:
uv run scripts/delete_deployment.py --deployment-id <id> --confirm --auto-stop

# Deployment logs
uv run scripts/get_deployment_logs.py --deployment-id <id>
uv run scripts/get_deployment_logs.py --deployment-id <id> --tail 50
uv run scripts/get_deployment_logs.py --deployment-id <id> --order asc
uv run scripts/get_deployment_logs.py --deployment-id <id> --json

# Remove duplicate LLM deployments (only affects LLM deployments with a model name)
uv run scripts/dedup_deployments.py --dry-run
uv run scripts/dedup_deployments.py

Handoffs

  • Need a Bearer token or credential setup? → invoke aicore-admin-resources
  • Need executable ID, model name, or model capabilities? → invoke genai-hub-foundation-models
  • Want to list available models or providers? → invoke genai-hub-foundation-models

FAQ

What does the aicore-lifecycle-management skill do?

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.

How do I install aicore-lifecycle-management?

Run npx skills add https://github.com/sap/ai-skills-library --skill aicore-lifecycle-management in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/aicore-lifecycle-management/ (personal) or .claude/skills/aicore-lifecycle-management/ (project).

Which AI agents can use aicore-lifecycle-management?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is aicore-lifecycle-management safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains aicore-lifecycle-management?

It is published by sap in sap/ai-skills-library. It has 88 recorded installs.

More from sap/ai-skills-library

View all →

sap-fiori-guidelines

sap/ai-skills-library

SAP Fiori design guidelines for building enterprise applications. Use this skill when designing, building, or reviewing SAP Fiori applications, implementing SAPUI5 or UI5 Web Components, working with SAP enterprise UX patterns, or needing guidance on buttons, forms, tables, object pages, list reports, navigation, messaging, colors, typography, accessibility, AI/Joule integration, or any SAP Fiori UI element. Triggers on mentions of Fiori, SAPUI5, UI5, SAP UX, SAP design system, or enterprise application design following SAP standards.

Frontend & Design1.2K installs

aicore-admin-resources

sap/ai-skills-library

Verify and configure SAP AI Core credentials, retrieve auth tokens, and manage resource groups. WHEN: user wants to check if AI Core is set up, configure credentials, get a Bearer token, fix authentication errors, run a setup health check, or list, create, update, or delete resource groups. DO NOT USE FOR: managing deployments — use aicore-lifecycle-management; listing foundation models — use genai-hub-foundation-models.

Backend & APIs88 installs

genai-hub-tabular-orchestration

sap/ai-skills-library

Open the skill to read its SKILL.md instructions.

87 installs

genai-hub-foundation-models

sap/ai-skills-library

Open the skill to read its SKILL.md instructions.

83 installs

Popular ai & agents skills

View category →

google-agents-cli-publish

google/agents-cli

This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).

AI & Agents513.9K installs

google-agents-cli-eval

google/agents-cli

This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).

AI & Agents513.5K installs

skill-creator

anthropics/skills

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

OfficialAI & Agents416.4K installs

codex-pet

prime-skills/runcomfy-agent-skills

Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.

AI & Agents402.1K installs

full-output-enforcement

leonxlnx/taste-skill

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

AI & Agents401K installs

executing-plans

obra/superpowers

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

AI & Agents245.7K installs