aicore-lifecycle-management

aicore-lifecycle-management is a skill for Claude Code from SAP/ai-skills-library. It costs 0 tokens per session (1,612 once invoked), scanned A, original, Apache-2.0.

A management guide for SAP AI Core resources, including scenarios, executables, configurations, and deployments. SAP AI Core is a cloud service for running AI workloads.

In plain words
What is it for?
Use it to list or inspect scenarios and executables, manage configurations, create or control deployments, read deployment logs, and remove duplicate language-model deployments.
Why use it?
It provides defined procedures for inspecting and changing those resources, while requiring confirmation for operations that change or delete state.

Skill for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter.

Part of the aicore-skills plugin — 4 skills shipped together

Good fit Use it to list or inspect scenarios and executables, manage configurations, create or control deployments, read deployment logs, and remove duplicate language-model deployments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sap/ai-skills-library/aicore-lifecycle-management
About the project

SAP/ai-skills-library is a catalogue for discovering, filtering, and installing AI skills that support SAP digital assistants. SAP users and contributors can install listed skills with the skills CLI across compatible coding agents, while skill authors keep their implementations in their own public repositories and register them with the library. The catalogue contains five of the library's skills and its plugin.

SAP/ai-skills-library · 81 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add SAP/ai-skills-library --skill aicore-lifecycle-management
Clone the repo
git clone --depth 1 https://github.com/SAP/ai-skills-library

Made for: Claude Code.

Or install aicore-skills, the plugin that ships this one along with the rest of its 4 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for aicore-lifecycle-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/sap/ai-skills-library/aicore-lifecycle-management/github.svg)](https://agentmods.dev/skills/sap/ai-skills-library/aicore-lifecycle-management)
Your own site
<a href="https://agentmods.dev/skills/sap/ai-skills-library/aicore-lifecycle-management"><img src="https://agentmods.dev/badge/skills/sap/ai-skills-library/aicore-lifecycle-management/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for aicore-lifecycle-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/sap/ai-skills-library/aicore-lifecycle-management"><img src="https://agentmods.dev/badge/skills/sap/ai-skills-library/aicore-lifecycle-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,612 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01612
Opus 5.5 $0.00000 $0.00645
Sonnet 5.5 $0.00000 $0.00322
Haiku 4.5 $0.00000 $0.00161

Measured 10d ago against content hash 54f50b884ba9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

aicore-lifecycle-management scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

The scan reads SKILL.md. This mod also ships 11 executable files (scripts/create_configuration.py, scripts/create_deployment.py, scripts/dedup_deployments.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/aicore-skills/skills/aicore-lifecycle-management/SKILL.md · 187 lines

How it starts

The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Read the full file on GitHub · 187 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago Changed · +1 lines · -108 tokens per session 54f50b884ba9
  2. 17d ago Changed · +1 lines cb440e5cea1d
  3. 24d ago First seen · 185 lines · 108 tokens per session scan A b17979279e28

Subscribe to this mod's changes

aicore-lifecycle-management is a skill published in the GitHub repository SAP/ai-skills-library (81 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,612 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-22.

Related

Other skills, from other repositories

agent-platform-tuning

Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).

google/skills · 64 tokens

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

gke-alert-configuration

Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…

google/skills · 120 tokens

gke-ai-troubleshooting-tpu-partition-overlap

Diagnose and resolve GKE TPU slice creation failures (SliceCreationFailed) caused by partition overlap conflicts where requested TPU partitions or their nodes are already used by another slice or JobSet. Use when diagnosing GKE TPU slice creation failures with SliceCreationFailed partition or node conflicts. Don't use…

google/skills · 108 tokens

application-design-center-design-deploy

Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…

google/skills · 94 tokens

cloud-run-basics

Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).

google/skills · 53 tokens