Individual skill
genai-hub-orchestration
Configure and use the SAP AI Core Orchestration service: build prompt templates, add content filtering, set up document grounding (RAG) pipelines, and call models via the Harmonized API. WHEN: user asks about the orchestration service, Harmonized API, prompt templating with variables, content filtering, grounding, RAG pipeline, document grounding, or building a pipeline that wraps an LLM. DO NOT USE FOR: creating an orchestration deployment — use `aicore-lifecycle-management` for that; credential setup — use `aicore-admin-resources`; browsing or deploying foundation models directly without a pipeline — use `genai-hub-foundation-models`; direct LLM inference without a pipeline — use `aicore-sdk-java` or `aicore-sdk-js`
plugins/aicore-skills/skills/genai-hub-orchestration/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)
- 144
- 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 · 7,714 bytesSKILL.mdcore · 7,714 bytesSKILL.mdcore · 7,714 bytesSKILL.mdcore · 7,714 bytesSKILL.mdcore · 7,714 bytesassets/orchestration_basic.pyruns · 1,981 bytesassets/orchestration_filtering.pyruns · 2,813 bytesassets/rag_grounding.pyruns · 2,941 bytesevals/evals.jsonasset · 2,094 bytesreferences/GROUNDING.mddoc · 3,405 bytesreferences/ORCHESTRATION.mddoc · 7,042 bytes
Read excerpt
## Rules
1. Orchestration always requires a **running orchestration deployment** as a prerequisite — invoke `aicore-lifecycle-management` first if one does not exist.
2. The orchestration endpoint is `POST {DEPLOYMENT_URL}/v2/completion` — not `/v1/chat/completions`.
3. Orchestration `scenario_id` and `executable_id` are always `"orchestration"` — these are fixed.
4. The Harmonized API normalizes all models to OpenAI message format — the same client code works for GPT, Gemini, and Bedrock.
5. If credentials are not configured, invoke `aicore-admin-resources` first.
6. `generative-ai-hub-sdk` is deprecated — always use `sap-ai-sdk-gen`. Import namespace `gen_ai_hub` is shared by both.
7. **If the user's request does not explicitly specify an approach, use `AskUserQuestion` to ask whether they prefer the REST API (curl) or the Python SDK before writing or running any code.**
---
## Deployment Prerequisite