agentleFS
SAPSAP/custom-agentic-cookbook/skills/sap-ai-core/SKILL.md

sap-ai-core

Skill9 starsChanged 22 days agoApache-2.0View on GitHub

Use this skill when provisioning or calling SAP AI Core — creating service instances, resource groups, deployment configurations, deployments, and OAuth2 client-credentials tokens. Includes per-region model-catalog gotchas so the agent never hardcodes a model that doesn't exist in the customer's region.

  • Sends data out

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When in doubt, run scripts/region-preflight/region-preflight.sh <region> and check the live catalog before picking.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SAP AI Core — bootstrap and call

AI Core is SAP's model-hosting surface on BTP. Models are accessed through deployments, which sit inside resource groups, which sit inside an AI Core service instance.

Bootstrap sequence

# 1. Service instance + binding (gives you OAuth2 creds)
btp create services/instance --offering-name aicore --plan-name extended \
  --name aicore-coe-pilot --subaccount $SUBACCOUNT
btp create services/binding --binding-name aicore-coe-pilot-key \
  --instance-name aicore-coe-pilot --subaccount $SUBACCOUNT
btp get services/binding aicore-coe-pilot-key --subaccount $SUBACCOUNT --output json > ai-core-key.json

# 2. Extract envs
export AICORE_BASE_URL=$(jq -r .serviceurls.AI_API_URL ai-core-key.json)
export AICORE_AUTH_URL=$(jq -r .url ai-core-key.json)/oauth/token
export AICORE_CLIENT_ID=$(jq -r .clientid ai-core-key.json)
export AICORE_CLIENT_SECRET=$(jq -r .clientsecret ai-core-key.json)

# 3. Token
export TOKEN=$(curl -s -X POST $AICORE_AUTH_URL \
  -d "grant_type=client_credentials" \
  -u "$AICORE_CLIENT_ID:$AICORE_CLIENT_SECRET" | jq -r .access_token)

# 4. Resource group
curl -s -X POST "$AICORE_BASE_URL/v2/admin/resourceGroups" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"resourceGroupId":"coe-pilot"}'

# 5. Find the right model for the region
curl -s "$AICORE_BASE_URL/v2/lm/scenarios/foundation-models/configurations" \
  -H "Authorization: Bearer $TOKEN" -H "AI-Resource-Group: coe-pilot" | jq '.resources[].name'

Region gotchas

RegionDO NOT useUse instead
chinaanthropic--*, gpt-*mistralai--mistral-large-2407, local OSS, Qwen via partner
ksaanthropic--*, gpt-*mistralai--mistral-large-2407, Falcon, local OSS
ns2hardcoded modelalways pull live catalog; restricted by authorization tier
commercialn/afull catalog

When in doubt, run scripts/region-preflight/region-preflight.sh <region> and check the live catalog before picking.

Calling a deployment

from gen_ai_hub.proxy.langchain.init_models import init_llm
llm = init_llm(
    "anthropic--claude-sonnet-4-5",
    deployment_id=os.environ["AICORE_MODEL_DEPLOYMENT_ID"],
    temperature=0.0,
)
llm.invoke("hello")

The generative-ai-hub-sdk reads AICORE_* env vars and handles token refresh.

Pitfalls

  • Forgetting the AI-Resource-Group header → 403.
  • Calling a deployment before it's RUNNING → 503; poll status first.
  • Using commercial endpoints from a sovereign region → cross-region call, blocked.
  • Burning entitlement: don't leave dev deployments running 24/7 in sovereign regions where capacity is scarce.

Verify

curl -s "$AICORE_BASE_URL/v2/lm/deployments/$AICORE_MODEL_DEPLOYMENT_ID" \
  -H "Authorization: Bearer $TOKEN" -H "AI-Resource-Group: $AICORE_RESOURCE_GROUP" \
  | jq -r .status
# expect: RUNNING

Cross-references

  • Bootstrap walkthrough: recipes/00-develop/00-region-preflight/ for AI Core availability + entitlement check; recipes/optional/sovereign-model-gateway/ for the openai-compatible fallback when AI Core is not in-region.
  • sap-sovereign-regions and its btp-regional-availability.md reference — source-backed per-region service and model guardrails.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.