Wdio Testing
ansible/vscode-ansible
Write, run, and debug WebDriverIO (WDIO) UI tests for the Ansible VS Code extension.
Acquire approved SAP media into the SDAF library after SAP-system infrastructure exists.
Install Sdaf Media Acquisition
$ npx skills add Azure/sap-automation --skill sdaf-media-acquisition -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/sap-automation sdaf-media-acquisition --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-media-acquisition .claude/skills/sdaf-media-acquisition && 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-media-acquisition" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-acquisition into .claude/skills/sdaf-media-acquisition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-acquisition", 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-media-acquisitionType 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-media-acquisition -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/sap-automation sdaf-media-acquisition --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-media-acquisition .agents/skills/sdaf-media-acquisition && 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-media-acquisition" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-acquisition into .agents/skills/sdaf-media-acquisition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-acquisition", 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-media-acquisition -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/sap-automation sdaf-media-acquisition --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-media-acquisition .cursor/skills/sdaf-media-acquisition && 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-media-acquisition" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-acquisition into .cursor/skills/sdaf-media-acquisition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-acquisition", 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-media-acquisition--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-media-acquisition -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/sap-automation sdaf-media-acquisition --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-media-acquisition .gemini/skills/sdaf-media-acquisition && 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-media-acquisition" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-acquisition into .gemini/skills/sdaf-media-acquisition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-acquisition", 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-media-acquisitionInstalls 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-media-acquisition -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-media-acquisition .github/skills/sdaf-media-acquisition && 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-media-acquisition" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-acquisition into .github/skills/sdaf-media-acquisition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-acquisition", 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-media-acquisition -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-media-acquisition --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-media-acquisition .opencode/skills/sdaf-media-acquisition && 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-media-acquisition" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-acquisition into .opencode/skills/sdaf-media-acquisition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-acquisition", 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-media-acquisition- GitHub stars
- 146
- Token cost
- ~1.4k tokens
- SKILL.md length
- 490 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Acquire approved SAP media into the SDAF library after SAP-system infrastructure exists.
- Works in 3 steps: Confirm the catalog root and component… → Run the documented local acquisition flow → Validate before installation
- Download SAP media
- SKILL.md covers When to invoke, Preconditions, Decision: which download input… and Recipe, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sdaf Media Acquisition is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Acquire approved SAP media into the SDAF library after SAP-system infrastructure exists. Drives local deploy/ansible/downloadmenu.sh per docs/local/06-00-software-and-installation.md § Download software, enforces the documented BOMCATALOG root and the four required sap-parameters.yaml BOM keys (applicationbomname, databasebomname, sapkernelbomname, savebomas), and explains the documented download and validation flow. Use for "download SAP media", "run downloadmenu.sh", "acquire software into the library", "BOM…
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Infrastructure as code. It works with Ansible. 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
- Download SAP media
- Run downloadmenu.sh
- Acquire software into the library
- Assemble application/database/kernel BOMs for download
Example prompts
- “download SAP media”
- “run downloadmenu.sh”
- “acquire software into the library”
- “/sdaf-media-acquisition”
Requirements
- Pre-approved tools (allowed-tools): shell
Workflow steps
3 steps, taken from the step headings in SKILL.md.
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 bash and 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 Media Acquisition loads about 1.4k tokens when it runs. Until then it costs about 187 tokens; SKILL.md has 490 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). 490 words, ~1,441 tokens.
Download SKILL.mdSave it as
.claude/skills/sdaf-media-acquisition/SKILL.md (or your agent's skills folder).- name
- sdaf-media-acquisition
- description
- Acquire approved SAP media into the SDAF library after SAP-system infrastructure exists. Drives local `deploy/ansible/download_menu.sh` per `docs/local/06-00-software-and-installation.md § Download software`, enforces the documented `BOM_CATALOG` root and the four required `sap-parameters.yaml` BOM keys (`application_bom_name`, `database_bom_name`, `sap_kernel_bom_name`, `save_bom_as`), and explains the documented download and validation flow. Use for "download SAP media", "run download_menu.sh", "acquire software into the library", "BOM Downloader", "BOM_CATALOG", or "assemble application/database/kernel BOMs for download". Do NOT use to choose a BOM, troubleshoot a failed download, or run installation playbooks.
- allowed-tools
- shell
- license
- MIT
SDAF Media Acquisition
Action-loop skill. Acquires approved SAP media into the library after
SAP-system infrastructure exists. The local operator path is documented in
docs/local/06-00-software-and-installation.md; shared downloader behavior
is described in the same operator guide.
When to invoke
Trigger on: "download SAP media", "acquire software into the library",
"download_menu.sh", "BOM Downloader", "BOM_CATALOG", or
"assemble application/database/kernel BOMs for download".
Do NOT trigger on: choosing a BOM (sdaf-bom-selection), troubleshooting a
failed or mismatched download (sdaf-media-diagnostics), or install playbooks.
Preconditions
- SAP-system infrastructure already completed;
sap-parameters.yamland<SID>_hosts.yamlexist in the system directory (docs/local/06-00-software-and-installation.md § Before you begin;docs/local/05-00-sap-system.md § Validate). - SSH connectivity to the inventory hosts, Key Vault-generated credentials, SAP
download credentials, and library capacity are confirmed
(
docs/local/06-00-software-and-installation.md § Before you begin). - The BOM choice is already reviewed; this skill does not decide product versus
component BOMs (
sdaf-bom-selection;sap-automation-samples/docs/02-00-bom-samples.md § Select and run a BOM).
Decision: which download input shape applies?
docs/local/06-00-software-and-installation.md § Inputs and BOM ownership is
explicit:
BOM_CATALOGmust point at the samples checkout root that contains siblingSAP/andBOM/directories.- Local
download_menu.shdoes not keep the Terraform-generatedbom_base_name. It reads these four keys fromsap-parameters.yamland constructs the effective BOM name itself:
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>Keep these values in the exact format documented by
§ Inputs and BOM ownership. The automation validates the application,
database, kernel, and output-name combination before download. Require
bom_base_name to equal save_bom_as; installation reloads
bom_base_name and must find the combined BOM written by the downloader.
Recipe
Step 1 — Confirm the catalog root and component names
From the SAP-system directory, confirm the catalog root exactly as the local doc requires:
cd "$CONFIG_REPO_PATH/WORKSPACES/SYSTEM/<SAP_SYSTEM>"
test -d "$BOM_CATALOG/SAP"
test -d "$BOM_CATALOG/BOM"Then re-read sap-parameters.yaml once. For the local menu path, all five BOM
keys above must be present, component names must match actual samples
directories/files, and bom_base_name must equal save_bom_as.
Show full SKILL.md (207 more words)Show less
Step 2 — Run the documented local acquisition flow
Start the local wrapper exactly per
docs/local/06-00-software-and-installation.md § Download software:
"$SAP_AUTOMATION_REPO_PATH/deploy/ansible/download_menu.sh"Then select BOM Downloader. The documented path requires
sap-parameters.yaml in the current directory and BOM_CATALOG in the
environment.
Step 3 — Validate before installation
Do not continue into configuration_menu.sh until both doc-level checks pass
(docs/local/06-00-software-and-installation.md § Validate):
- the downloader reports success for every required archive; and
- the SAP library contains the expected software.
Also keep the samples commit and selected BOM names with the run record
(
sap-automation-samples/docs/02-00-bom-samples.md § Validate).
If the run stops or rejects the input
sap-parameters.yamlmissing,BOM_CATALOGunset, orBOM_CATALOGnot a directory: fix the local wrapper precondition and rerun (deploy/ansible/download_menu.sh;docs/local/troubleshooting.md § BOM files are not found).- Incompatible application/database/kernel combination: go back to
sdaf-bom-selectionand review the documented compatibility fields. - Archive, checksum, or download-service failures belong to
sdaf-media-diagnostics, not this skill.
Hard rules
- Documented behaviour only (D19). Do not invent alternate download
commands, proxy/offline procedures, or compatibility matrices (
docs/PLUGINS.md § Ground rules and exclusions). - Do not point
BOM_CATALOGat a single BOM directory. - Do not bypass checksum or compatibility failures
(
sap-automation-samples/docs/02-00-bom-samples.md § If it fails). - Do not start installation until the downloader reports success for the required archives.
See also
sdaf-bom-selection,sdaf-sap-system,sdaf-media-diagnostics.docs/local/06-00-software-and-installation.md,docs/local/troubleshooting.md § BOM files are not found,sap-automation-samples/docs/02-00-bom-samples.md,.github/copilot-instructions.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
Just SKILL.md in skills/sdaf-media-acquisition of Azure/sap-automation.
Open the folder on GitHubat commit 78835f0
Compare with similar skills
Sdaf Media Acquisition 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 Media Acquisition this skillAzure/sap-automation | 146 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Wdio Testingansible/vscode-ansible | 488 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Spa Create Configsplunk/splunk-platform-automator | 138 | — | ~3.5k | Automated safety check: Pass | Proprietary | |
| Spa Add Test Scenariosplunk/splunk-platform-automator | 138 | — | ~2.2k | Automated safety check: Pass | Proprietary | |
| Frontend Overlayansible/ansible-ui | 113 | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Run Testsansible-collections/ansible.mysql | 134 | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
Spa Create Config
splunk/splunk-platform-automator
A skill your agent uses when creating or updating splunkconfig.yml, designing Splunk Enterprise lab topology, multisite IDXC, SHC layout, architecture plan before config, or AWS Terraform block for…
Spa Add Test Scenario
splunk/splunk-platform-automator
A skill your agent uses when adding app scope/routing test coverage (deployer, CM, DS, direct).
Frontend Overlay
ansible/ansible-ui
Product-specific frontend wrappers, API clients, and paths for ansible-ui.
Run Tests
ansible-collections/ansible.mysql
Runs and writes tests (sanity, unit, integration) for the ansible.mysql Ansible collection using ansible-test.
Ansible Module Doc Review
ansible-collections/vmware.vmware_rest
Review and enrich Ansible module documentation to ensure completeness and quality.
More from Azure/sap-automation
All 19 skills in this repo- Official
Sdaf Bom Selection
Azure/sap-automation
Pick the right SDAF BOM for a target SAP product / release / DB platform / version / kernel / topology.
- 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.
Related
Works with
Categories
Questions about Sdaf Media Acquisition
What does Sdaf Media Acquisition do?
Acquire approved SAP media into the SDAF library after SAP-system infrastructure exists. Sdaf Media Acquisition is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Acquire approved SAP media into the SDAF library after SAP-system infrastructure exists.
When should I use Sdaf Media Acquisition?
Sdaf Media Acquisition fits situations like: download SAP media; run downloadmenu.sh; acquire software into the library; assemble application/database/kernel BOMs for download.
How do I install Sdaf Media Acquisition in Claude Code?
Run `npx skills add Azure/sap-automation --skill sdaf-media-acquisition -a claude-code`. Or copy the skill folder (skills/sdaf-media-acquisition in Azure/sap-automation) into .claude/skills/sdaf-media-acquisition in your project. Claude Code loads it when a task matches its description.
How do I install Sdaf Media Acquisition in Codex?
Run `npx skills add Azure/sap-automation --skill sdaf-media-acquisition -a codex`. Or copy the skill folder (skills/sdaf-media-acquisition in Azure/sap-automation) into .agents/skills/sdaf-media-acquisition in your project. Codex loads it when a task matches its description.
Can I use Sdaf Media Acquisition 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-media-acquisition -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-media-acquisition, .gemini/skills/sdaf-media-acquisition, .github/skills/sdaf-media-acquisition and .opencode/skills/sdaf-media-acquisition in your project.
What does Sdaf Media Acquisition need to run?
SKILL.md names no scripts, command-line tools or credentials: Sdaf Media Acquisition is instructions for the agent only. Its frontmatter pre-approves these tools: shell.
Does Sdaf Media Acquisition 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 Media Acquisition 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 Media Acquisition use?
Sdaf Media Acquisition 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 Media Acquisition use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sdaf Media Acquisition?
Skills that share tags, products or a category with Sdaf Media Acquisition: Wdio Testing (ansible/vscode-ansible, 488 stars), Spa Create Config (splunk/splunk-platform-automator, 138 stars), Spa Add Test Scenario (splunk/splunk-platform-automator, 138 stars) and Frontend Overlay (ansible/ansible-ui, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sdaf Media Acquisition?
Azure (a GitHub organization, an official publisher) maintains it in Azure/sap-automation, which has 146 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 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.