Individual skill
genai-hub-tabular-orchestration
Manage the SAP AI Core Context Registry — data destinations (HDL connections), tabular artifacts (CSV/Parquet/Delta files as queryable tables), and scenario configurations (named artifact bundles). Also interactively build and send tabular prediction requests using the SAP AI Core Tabular Prediction service (sap-rpt-1-small / sap-rpt-1-large). Use this skill whenever the user mentions context registry, data destinations, tabular artifacts, scenario configurations, TCR, HDL connections, or wants to register/list/delete structured data sources in SAP AI Core. Always use this skill for any tabular-orchestration / tcr API work, even if the user just asks "show me my data destinations" or "register this CSV as a tabular artifact". Also use for: SAP AI Core tabular prediction, sap-rpt prediction, "predict a column with sap-rpt", TCR row classification. NOT FOR general orchestration, generic ML prediction, or LLM pipelines — use `genai-hub-orchestration` for those. NOT FOR general classification/prediction requests unrelated to SAP AI Core TCR (e.g. "predict sales next quarter", "classify this text").
plugins/aicore-skills/skills/genai-hub-tabular-orchestration/SKILL.md
Source commit 82b27a81d972aa4f70dc6154605606cfed0b4772
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 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)
- 146
- 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 · 20,719 bytesSKILL.mdcore · 20,719 bytesSKILL.mdcore · 20,719 bytesSKILL.mdcore · 20,719 bytesSKILL.mdcore · 20,719 bytesSKILL.mdcore · 20,719 bytesSKILL.mdcore · 20,719 bytesSKILL.mdcore · 20,719 bytesSKILL.mdcore · 20,719 bytesSKILL.mdcore · 20,719 bytesSKILL.mdcore · 20,719 bytesSKILL.mdcore · 20,719 bytesreferences/API.mddoc · 10,192 bytesreferences/PREDICT.mddoc · 6,036 bytesreferences/SETUP.mddoc · 1,101 bytesscripts/create_data_destination.pyruns · 9,556 bytesscripts/create_scenario_config.pyruns · 4,805 bytesscripts/create_tabular_artifact.pyruns · 8,327 bytesscripts/delete_data_destination.pyruns · 2,244 bytesscripts/delete_scenario_config.pyruns · 1,876 bytesscripts/delete_tabular_artifact.pyruns · 2,151 bytesscripts/get_data_destination.pyruns · 2,479 bytesscripts/get_scenario_config.pyruns · 2,645 bytesscripts/get_tabular_artifact.pyruns · 2,451 bytesscripts/get_tabular_artifact_data.pyruns · 2,644 bytesscripts/list_data_destinations.pyruns · 2,588 bytesscripts/list_scenario_configs.pyruns · 2,522 bytesscripts/list_tabular_artifacts.pyruns · 2,787 bytesscripts/patch_data_destination.pyruns · 4,823 bytesscripts/patch_scenario_config.pyruns · 5,198 bytesscripts/predict.pyruns · 4,892 bytesscripts/search_data_destinations.pyruns · 3,459 bytesscripts/search_scenario_configs.pyruns · 3,393 bytesscripts/validate_data_destination.pyruns · 5,429 bytesscripts/validate_data_destination_by_name.pyruns · 2,323 bytes
Read excerpt
## Rules
1. Run all scripts from the skill root with `uv run scripts/<name>.py`.
2. Never print or log credential values — the SDK reads from the environment.
3. Always verify TCR prerequisites (data destination → tabular artifact → scenario configuration) are in place before sending a prediction request.
4. `rows` and `columns` are mutually exclusive in a prediction request — never include both.
5. For credential or auth errors, invoke `aicore-admin-resources` first.
6. Mutating scripts require `--confirm`; always pass it explicitly for delete operations.
7. Omit `--resource-group` when the user doesn't specify one; the SDK default is used.
8. Before issuing any `btp update services/instance` command: (a) run `btp get services/instance --id <id>` to fetch the full current `parameters` block, (b) show the user the complete current parameters and the exact diff — what is being added, changed, or removed — along with the full resulting payload that will be sent, and (c) require the user to explicitly confirm the shown parameters and the proposed change before proceeding. Do not issue `btp update services/instance` under any circumstance until the user has confirmed in that same turn.
---
## Concepts