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.
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.
npx skills add SAP/ai-skills-library --skill aicore-lifecycle-managementgit clone --depth 1 https://github.com/SAP/ai-skills-libraryWrote 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.
[](https://agentmods.dev/skills/sap/ai-skills-library/aicore-lifecycle-management)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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.
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
- Run all scripts from the skill root directory with
uv run scripts/<name>.py. - Never print or log credential values — the SDK reads them from the environment.
- Scripts that delete or mutate state require
--confirm. Always pass it explicitly; never bypass it. - When the user does not specify a resource group, omit
--resource-groupso the SDK uses its configured default. - 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. - 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 viaget_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
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/create_configuration.py 4.4 KB runs code
- scripts/create_deployment.py 5.5 KB runs code
- scripts/dedup_deployments.py 5.9 KB runs code
- scripts/delete_deployment.py 4.8 KB runs code
- scripts/get_configurations.py 7.6 KB runs code
- scripts/get_deployment_logs.py 5.2 KB runs code
- scripts/get_deployments.py 14 KB runs code
- scripts/get_executables.py 7.7 KB runs code
- scripts/get_scenarios.py 6.4 KB runs code
- scripts/patch_deployment.py 2.4 KB runs code
- scripts/stop_deployment.py 3.8 KB runs code
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.
- 10d ago Changed · +1 lines · -108 tokens per session 54f50b884ba9
- 17d ago Changed · +1 lines cb440e5cea1d
- 24d ago First seen · 185 lines · 108 tokens per session scan A b17979279e28
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.
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).
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…
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…
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…
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…
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).