Obliteratus
RedWoodOG/Hermes-Desktop
Remove refusal behaviors from open-weight LLMs using OBLITERATUS — mechanistic interpretability techniques (diff-in-means, SVD, whitened SVD, LEACE, SAE decomposition, etc.) to excise guardrails…
Pick the right SDAF BOM for a target SAP product / release / DB platform / version / kernel / topology.
Install Sdaf Bom Selection
$ npx skills add Azure/sap-automation --skill sdaf-bom-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/sap-automation sdaf-bom-selection --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sdaf-bom-selection .claude/skills/sdaf-bom-selection && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sdaf-bom-selection" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-bom-selection into .claude/skills/sdaf-bom-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-bom-selection", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Azure/sap-automation/tree/main/skills/sdaf-bom-selectionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Azure/sap-automation --skill sdaf-bom-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/sap-automation sdaf-bom-selection --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sdaf-bom-selection .agents/skills/sdaf-bom-selection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sdaf-bom-selection" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-bom-selection into .agents/skills/sdaf-bom-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-bom-selection", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/sap-automation --skill sdaf-bom-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/sap-automation sdaf-bom-selection --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sdaf-bom-selection .cursor/skills/sdaf-bom-selection && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sdaf-bom-selection" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-bom-selection into .cursor/skills/sdaf-bom-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-bom-selection", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Azure/sap-automation.git --path skills/sdaf-bom-selection--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Azure/sap-automation --skill sdaf-bom-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/sap-automation sdaf-bom-selection --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sdaf-bom-selection .gemini/skills/sdaf-bom-selection && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sdaf-bom-selection" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-bom-selection into .gemini/skills/sdaf-bom-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-bom-selection", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Azure/sap-automation sdaf-bom-selectionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Azure/sap-automation --skill sdaf-bom-selection -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sdaf-bom-selection .github/skills/sdaf-bom-selection && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sdaf-bom-selection" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-bom-selection into .github/skills/sdaf-bom-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-bom-selection", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Azure/sap-automation --skill sdaf-bom-selection -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Azure/sap-automation sdaf-bom-selection --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sdaf-bom-selection .opencode/skills/sdaf-bom-selection && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sdaf-bom-selection" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-bom-selection into .opencode/skills/sdaf-bom-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-bom-selection", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sdaf-bom-selection- GitHub stars
- 145
- Token cost
- ~1.6k tokens
- SKILL.md length
- 605 words
- Files
- 2 (incl. references)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Pick the right SDAF BOM for a target SAP product / release / DB platform / version / kernel / topology.
- A user says which BOM do I use
- SKILL.md covers When to invoke, Where BOMs live, BOM_CATALOG must point at the… and The four BOM keys (download…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Product BOM vs component BOM
What it does
Sdaf Bom Selection is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Pick the right SDAF BOM for a target SAP product / release / DB platform / version / kernel / topology. Explains where BOMs live in the samples repo (SAP/ for whole products, BOM/ for components), decodes the ms, v, and latest suffix conventions, points at the compatibility guardrails (supportedPlatforms, supportedDBVersions, supportedKernels), and reminds the operator that the download flow needs four explicit BOM keys in sap-parameters.yaml. Use when a user says "which BOM do I use", "product BOM vs component…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/bom-selection.md`).
It sits in AI & LLM Engineering, covering LLM guardrails. The repository describes itself as: This is the repository supporting the SAP deployment automation framework on Azure. The licence is MIT.
When your agent uses it
- A user says which BOM do I use
- Product BOM vs component BOM
- SAP samples BOM catalog
- How do I pick a BOM for HANA/Oracle/DB2/ASE
Example prompts
- “which BOM do I use”
- “product BOM vs component BOM”
- “SAP samples BOM catalog”
- “/sdaf-bom-selection”
Requirements
- Pre-approved tools (allowed-tools): shell
What it can do on your machine
Read from SKILL.md and the folder at commit 78835f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
shell
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sdaf Bom Selection loads about 1.6k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 206 tokens; SKILL.md has 605 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Azure/sap-automation at commit 78835f0, republished under its MIT licence (© Azure). 605 words, ~1,599 tokens.
Download SKILL.mdSave it as
.claude/skills/sdaf-bom-selection/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- sdaf-bom-selection
- description
- Pick the right SDAF BOM for a target SAP product / release / DB platform / version / kernel / topology. Explains where BOMs live in the samples repo (`SAP/` for whole products, `BOM/` for components), decodes the `ms`, `v####`, and `latest` suffix conventions, points at the compatibility guardrails (`supportedPlatforms`, `supportedDBVersions`, `supportedKernels`), and reminds the operator that the download flow needs four explicit BOM keys in `sap-parameters.yaml`. Use when a user says "which BOM do I use", "product BOM vs component BOM", "SAP samples BOM catalog", "BOM_CATALOG", "S4/2023 BOM", "HANA BOM", or "how do I pick a BOM for HANA/Oracle/DB2/ASE". Do NOT use to author a new BOM, to acquire media (`sdaf-media-acquisition`), or to troubleshoot a checksum / 404 (`sdaf-media-diagnostics`).
- allowed-tools
- shell
- license
- MIT
SDAF BOM Selection
Context-primer. Helps a user choose an existing BOM from the samples
catalog. Grounded in docs/local/06-00-software-and-installation.md § Inputs and BOM ownership and the samples-repo BOM docs
(sap-automation-samples/docs/02-00-bom-samples.md).
For an ordered 5-step end-to-end walkthrough (identify target → product vs
component BOM → compatibility fields → prefer pinned name → pin samples
commit), see references/bom-selection.md;
this body carries the topic-by-topic facts.
When to invoke
Trigger on: "pick a BOM", "which BOM", "product BOM vs component BOM", "BOM_CATALOG", "SAP samples", "S4 2023 BOM", "HANA BOM", "Oracle BOM", "DB2 BOM", "compatibility guardrails".
Do NOT trigger on: authoring a new BOM, running download_menu.sh, media
404 / checksum troubleshooting, or install-time BOM failures.
Where BOMs live
Docs
(sap-automation-samples/docs/02-00-bom-samples.md § Understand SAP and BOM;
docs/local/06-00-software-and-installation.md § Inputs and BOM ownership):
sap-automation-samples/SAP/<name>/<name>.yaml— product BOM (whole product); pick this when the documented flow accepts a single complete definition.sap-automation-samples/BOM/<name>/<name>.yaml— component BOM (app / db / kernel); pick these when the flow supports dynamic assembly driven by the foursap-parameters.yamlkeys documented below. Anchor:sap-automation-samples/docs/02-00-bom-samples.md § Understand SAP and BOM.sap-automation-samples/SAP/archives/— legacy only; do not use without explicit release guidance.
Filename rule (docs; samples): the directory name and the YAML basename must match exactly, case-sensitive. A rename that breaks the pair breaks selection.
BOM_CATALOG must point at the samples root
docs/local/06-00-software-and-installation.md § Inputs and BOM ownership:
- Set
BOM_CATALOGto the root of a reviewed samples checkout that contains bothSAP/andBOM/. - Do not set
BOM_CATALOGto an individual BOM directory. download_menu.shpasses this value to Ansible asBOM_directory.
The four BOM keys (download flow)
docs/local/06-00-software-and-installation.md § Inputs and BOM ownership
is explicit: the SAP-system-generated sap-parameters.yaml contains
bom_base_name, but the wrapper overrides it and requires four keys:
application_bom_name: <APPLICATION_BOM>
database_bom_name: <DATABASE_BOM>
sap_kernel_bom_name: <KERNEL_BOM>
save_bom_as: <COMBINED_BOM_NAME>
bom_base_name: <COMBINED_BOM_NAME>Without the four downloader keys, the wrapper substitutes an empty value and
the download fails. Also require bom_base_name to equal save_bom_as;
installation reloads bom_base_name and must find the combined BOM written by
the downloader. Surface both constraints whenever the operator picks component
BOMs.
Compatibility guardrails
BOM YAML fields to check before picking (documented in
sap-automation-samples/docs/02-00-bom-samples.md § Select and run a BOM /
§ Review before execution; the same fields are present in every shipped
BOM at sap-automation-samples/{SAP,BOM}/<name>/<name>.yaml — open the
current candidate rather than a versioned example):
supportedPlatformssupportedDBVersionssupportedKernelsproduct_ids(role-to-SAP-product-ID map)materials.dependencies(prerequisite BOMs)
For the current allowed values on any of these keys, read the target BOM YAML itself and the samples-repo doc anchor above — those own the strings. Do not select a BOM whose guardrails do not match the target topology.
Show full SKILL.md (208 more words)Show less
Suffix decoding
sap-automation-samples/SAP/readme.md § BOM Name / BOM File and
§ 02-00-bom-samples.md § Select and run a BOM:
mssuffix — Microsoft-supplied BOM.v####suffix — serial version number.latestin a name — moving target; the docs warn that names containinglatestcan change later. Prefer a pinnedv####name, and pin the samples-repo checkout commit, so a BOM selected today matches the media downloaded tomorrow (sap-automation-samples/docs/02-00-bom-samples.md § Select and run a BOM).
Hand-off
- To validate a BOM:
check_bom.sh(runsyamllint,ansible-lint, andcheck_bom.yml). Referenced insap-automation-samples/docs/02-00-bom-samples.md § Validate. BOM authoring is outside the shipped 18-skill hub. - To acquire media once a BOM is selected: route to
sdaf-media-acquisition. - To diagnose archive / checksum / extractor failures after selection:
route to
sdaf-media-diagnostics. - To route BOM failures during a run:
docs/local/troubleshooting.md § BOM files are not found→ confirmBOM_CATALOGroot, names, and files.
Hard rules
- Documented behaviour only (D19). If asked about air-gapped / offline
media, an undocumented compatibility mapping, or the meaning of
XBOM, say docs are silent and stop. - Do not add credentials or downloaded media to the samples repo
(
sap-automation-samples/docs/02-00-bom-samples.md § Before you begin). - Do not point
BOM_CATALOGat a single BOM directory.
See also
sdaf-sap-system(its generatedsap-parameters.yamlis where the four BOM keys are set).sdaf-workspace-and-tfvars(where the samples checkout is separate from the SDAF checkout).sap-automation-samples/docs/02-00-bom-samples.md,docs/local/06-00-software-and-installation.md.
© Azure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/sdaf-bom-selection of Azure/sap-automation.
- SKILL.md
- references/bom-selection.md
Open the folder on GitHubat commit 78835f0
Compare with similar skills
Sdaf Bom Selection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sdaf Bom Selection this skillAzure/sap-automation | 145 | — | ~1.6k | Automated safety check: Pass | MIT | |
| ObliteratusRedWoodOG/Hermes-Desktop | 177 | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Lemonade Router Builderamd/skills | 398 | — | ~4k | Automated safety check: Pass | MIT | |
| Wp Project Triagegambitph/Stackable | 350 | 4 repos | ~371 | Automated safety check: Pass | GPL-3.0 | |
| Aisafetyhotwuyoscar/AISafetyHot-Hub | 224 | — | ~774 | Automated safety check: Pass | Custom licence | |
| Persona Designkangarooking/system-prompt-skills | 205 | 1 repos | ~956 | Automated safety check: Pass | MIT |
Similar skills
Lemonade Router Builder
amd/skills
Turns a natural-language description of routing intent into a valid Lemonade collection.router policy JSON.
Wp Project Triage
gambitph/Stackable
A skill your agent uses when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a…
Aisafetyhot
wuyoscar/AISafetyHot-Hub
Read AI Safety HOT daily digests, search recent AI safety research and incidents, and follow current hot topics.
Persona Design
kangarooking/system-prompt-skills
当需要为 AI 产品定义核心身份、角色声明和能力边界时调用此 skill。典型场景包括：设计新 AI 产品的 system prompt 首段、为不同场景创建差异化角色（如教学助手 vs 编程代理）、重新定义 AI 与用户的关系框架。
Execution Guardrails
mrtooher/fable-mode
Always-on operational guardrails, model-independent. An agent skill from mrtooher/fable-mode.
More from Azure/sap-automation
All 19 skills in this repo- Official
Sdaf Orientation And Surface
Azure/sap-automation
Orient a newcomer to the SAP Deployment Automation Framework (SDAF): explain the spine (control plane → workload zone → SAP system → software → install → operate/remove), summarise the three…
- Official
Sdaf Quality Assurance
Azure/sap-automation
Validate a deployed SDAF SAP system through the SDAF-owned QA entry points: the local quality-assurance menu and the documented Azure DevOps pipeline 13 path.
- Official
Sdaf Sap Installation
Azure/sap-automation
Guide SDAF operating-system, database, and SAP installation after the SAP-system workspace and reviewed media are ready.
- Official
Sdaf Sovereign Cloud
Azure/sap-automation
Explain the current SDAF sovereign-cloud deltas without inventing a generic "all sovereigns" runbook.
- Official
Sdaf State Management
Azure/sap-automation
Inspect and repair SDAF Terraform state safely before any reviewed import/remove.
- Official
Sdaf Workspace And Tfvars
Azure/sap-automation
Explain and validate the SDAF WORKSPACES layout (DEPLOYER / LIBRARY / LANDSCAPE / SYSTEM), the region-code naming convention, and how the four tfvars files hang off it.
Related
Categories
Questions about Sdaf Bom Selection
What does Sdaf Bom Selection do?
Pick the right SDAF BOM for a target SAP product / release / DB platform / version / kernel / topology. Sdaf Bom Selection is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Pick the right SDAF BOM for a target SAP product / release / DB platform / version / kernel / topology.
When should I use Sdaf Bom Selection?
Sdaf Bom Selection fits situations like: A user says which BOM do I use; product BOM vs component BOM; SAP samples BOM catalog; how do I pick a BOM for HANA/Oracle/DB2/ASE.
How do I install Sdaf Bom Selection in Claude Code?
Run `npx skills add Azure/sap-automation --skill sdaf-bom-selection -a claude-code`. Or copy the skill folder (skills/sdaf-bom-selection in Azure/sap-automation) into .claude/skills/sdaf-bom-selection in your project. Claude Code loads it when a task matches its description.
How do I install Sdaf Bom Selection in Codex?
Run `npx skills add Azure/sap-automation --skill sdaf-bom-selection -a codex`. Or copy the skill folder (skills/sdaf-bom-selection in Azure/sap-automation) into .agents/skills/sdaf-bom-selection in your project. Codex loads it when a task matches its description.
Can I use Sdaf Bom Selection in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Azure/sap-automation --skill sdaf-bom-selection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sdaf-bom-selection, .gemini/skills/sdaf-bom-selection, .github/skills/sdaf-bom-selection and .opencode/skills/sdaf-bom-selection in your project.
What does Sdaf Bom Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Sdaf Bom Selection is instructions for the agent only. Its frontmatter pre-approves these tools: shell.
Does Sdaf Bom Selection access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sdaf Bom Selection safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sdaf Bom Selection use?
Sdaf Bom Selection is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sdaf Bom Selection use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 449 tokens, read only when the agent opens those files.
What are the alternatives to Sdaf Bom Selection?
Skills that share tags, products or a category with Sdaf Bom Selection: Obliteratus (RedWoodOG/Hermes-Desktop, 177 stars), Lemonade Router Builder (amd/skills, 398 stars), Wp Project Triage (gambitph/Stackable, 350 stars) and Aisafetyhot (wuyoscar/AISafetyHot-Hub, 224 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sdaf Bom Selection?
Azure (a GitHub organization, an official publisher) maintains it in Azure/sap-automation, which has 145 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.
Source: Azure/sap-automation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.