Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Diagnose SDAF software-download and BOM-processing failures after a BOM is already selected.
Install Sdaf Media Diagnostics
$ npx skills add Azure/sap-automation --skill sdaf-media-diagnostics -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/sap-automation sdaf-media-diagnostics --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-diagnostics .claude/skills/sdaf-media-diagnostics && 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-diagnostics" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-diagnostics into .claude/skills/sdaf-media-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-diagnostics", 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-diagnosticsType 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-diagnostics -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/sap-automation sdaf-media-diagnostics --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-diagnostics .agents/skills/sdaf-media-diagnostics && 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-diagnostics" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-diagnostics into .agents/skills/sdaf-media-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-diagnostics", 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-diagnostics -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/sap-automation sdaf-media-diagnostics --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-diagnostics .cursor/skills/sdaf-media-diagnostics && 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-diagnostics" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-diagnostics into .cursor/skills/sdaf-media-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-diagnostics", 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-diagnostics--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-diagnostics -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/sap-automation sdaf-media-diagnostics --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-diagnostics .gemini/skills/sdaf-media-diagnostics && 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-diagnostics" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-diagnostics into .gemini/skills/sdaf-media-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-diagnostics", 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-diagnosticsInstalls 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-diagnostics -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-diagnostics .github/skills/sdaf-media-diagnostics && 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-diagnostics" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-diagnostics into .github/skills/sdaf-media-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-diagnostics", 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-diagnostics -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-diagnostics --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-diagnostics .opencode/skills/sdaf-media-diagnostics && 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-diagnostics" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-media-diagnostics into .opencode/skills/sdaf-media-diagnostics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-media-diagnostics", 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-diagnostics- GitHub stars
- 145
- Token cost
- ~1.3k tokens
- SKILL.md length
- 551 words
- Files
- 2 (incl. references)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnose SDAF software-download and BOM-processing failures after a BOM is already selected.
- Works in 4 steps: Classify the failing lane → Walk the symptom map → Re-read the current BOM and documented… → …
- A user says downloadmenu failed
- SKILL.md covers When to invoke, Preconditions, Recipe and Special boundary: SPS-level…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sdaf Media Diagnostics is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Diagnose SDAF software-download and BOM-processing failures after a BOM is already selected. Covers the documented local media path, SAP download, storage-account upload/download, checksum validation, and SAPCAR / .EXE extraction. Use when a user says "downloadmenu failed", "BOM downloader 404", "missing archive", "checksum mismatch", "SAPCAR failed", "bom-processing-done missing", or "my SPS07 media run can't find a file". Do NOT use to choose a BOM (see sdaf-bom-selection), to run a clean first-time media…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/media-symptom-map.md`).
It sits in DevOps & Cloud. 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 downloadmenu failed
- BOM downloader 404
- Missing archive
- Checksum mismatch
Example prompts
- “downloadmenu failed”
- “BOM downloader 404”
- “missing archive”
- “/sdaf-media-diagnostics”
Requirements
- Pre-approved tools (allowed-tools): shell
Workflow steps
4 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.
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 Diagnostics loads about 1.3k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 155 tokens; SKILL.md has 551 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). 551 words, ~1,340 tokens.
Download SKILL.mdSave it as
.claude/skills/sdaf-media-diagnostics/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- sdaf-media-diagnostics
- description
- Diagnose SDAF software-download and BOM-processing failures after a BOM is already selected. Covers the documented local media path, SAP download, storage-account upload/download, checksum validation, and `SAPCAR` / `.EXE` extraction. Use when a user says "download_menu failed", "BOM downloader 404", "missing archive", "checksum mismatch", "SAPCAR failed", "bom-processing-done missing", or "my SPS07 media run can't find a file". Do NOT use to choose a BOM (see `sdaf-bom-selection`), to run a clean first-time media download with no failure, or to diagnose a later non-media install failure.
- allowed-tools
- shell
- license
- MIT
SDAF Media Diagnostics
Action-loop skill. Diagnoses failures on the local software path after the
operator already chose the BOM and started either download_menu.sh or BOM
processing from configuration_menu.sh. Grounded in
docs/local/06-00-software-and-installation.md,
docs/local/troubleshooting.md, and docs/PLUGINS.md. No invented recovery
paths.
When to invoke
Trigger on: "download_menu failed", "BOM downloader 404", "missing archive", "checksum mismatch", "SAPCAR failed", "bom-processing-done missing", "SPS07 media file missing".
Do NOT trigger on: choosing a BOM/version, running a clean first download, or a later DB/SAP install failure after media staging.
Preconditions
- Collect the exact failing command or menu step, exit code, and last 200 lines of output.
- Identify whether the failure happened in:
- the documented media acquisition step; or
- BOM processing during configuration and installation.
- If the operator only says "SPS07" or similar product/version words, ask whether this is a BOM-choice question or a concrete failing file.
Recipe
Step 1 — Classify the failing lane
- Acquisition lane — use
docs/local/06-00-software-and-installation.md § Download softwareand its documented inputs. - Processing lane — use
§ Run configuration and installationand its safe-retry guidance. - If the failure is in a later numbered install playbook rather than BOM
acquisition / processing, stop and route to
sdaf-sap-installationorsdaf-failure-triageif the install-stage owner is still ambiguous.
Step 2 — Walk the symptom map
Use references/media-symptom-map.md and
match the exact signature before suggesting any retry. The map covers:
- missing
sap-parameters.yaml/BOM_CATALOG - BOM not found
s_user/s_passwordor storage-account auth failures- archive
404/ missing blob - checksum mismatch
SAPCAR/.EXEextraction failures- missing
.progress/bom-processing-done - offline / air-gapped asks that the repo does not document
If nothing matches, say the shipped docs/code do not describe this media failure and stop.
Step 3 — Re-read the current BOM and documented inputs
The authoritative inputs are the current sap-parameters.yaml, the selected
BOM YAML, and the operator documentation:
docs/local/06-00-software-and-installation.md § Inputs and BOM ownership—BOM_CATALOGmust point at the samples root;download_menu.shrequiresapplication_bom_name,database_bom_name,sap_kernel_bom_name, andsave_bom_as.docs/local/06-00-software-and-installation.md § Configuration preparation— review the current BOM's URLs, archive names, checksums, and target product versions. Do not rename files, replace URLs, or invent checksums from memory.
Show full SKILL.md (219 more words)Show less
Step 4 — Retry only the minimal documented step
- For acquisition-lane failures, fix the matched precondition or BOM/input
issue, then rerun BOM Downloader from
download_menu.sh. - For processing-lane failures, rerun the smallest applicable playbook from
configuration_menu.sh;docs/local/06-00-software-and-installation.md § Safe retrysays to review the failed numbered playbook, output, and progress marker first. - Use the documented completion evidence; do not create or delete progress markers manually.
Special boundary: SPS-level questions
The local docs tell operators to review BOM names, URLs, archive names, checksums, and target product versions, but they do not ship an SPS07-specific troubleshooting runbook. Use this rule:
- "Which BOM/version do I need for SPS07?" →
sdaf-bom-selection. - "The already-selected SPS07 media set is failing with a missing archive, checksum, or extract error" → stay here and work the exact failing file/log through the symptom map.
Hard rules
- Documented behaviour only.
docs/PLUGINS.mdexplicitly says air-gapped / offline media is outside shipped guidance. - Do not invent new BOM contents, replacement URLs, checksums, or SPS mappings.
- Do not treat a generic later install failure as a media problem without a matching acquisition / processing anchor.
- Do not delete
.progressmarkers or storage blobs merely to force a rerun.
See also
sdaf-bom-selection— choose product vs component BOMs and compatibility guardrails.sdaf-media-acquisition— clean first-time media download once the failure boundary is gone.sdaf-failure-triage— non-media or ambiguous stage failures.docs/local/06-00-software-and-installation.md,docs/local/troubleshooting.md,docs/PLUGINS.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-media-diagnostics of Azure/sap-automation.
- SKILL.md
- references/media-symptom-map.md
Open the folder on GitHubat commit 78835f0
Compare with similar skills
Sdaf Media Diagnostics 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 Diagnostics this skillAzure/sap-automation | 145 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 36k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
Docs Learn PR Preview
netdata/netdata
Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.
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
Categories
Questions about Sdaf Media Diagnostics
What does Sdaf Media Diagnostics do?
Diagnose SDAF software-download and BOM-processing failures after a BOM is already selected. Sdaf Media Diagnostics is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Diagnose SDAF software-download and BOM-processing failures after a BOM is already selected.
When should I use Sdaf Media Diagnostics?
Sdaf Media Diagnostics fits situations like: A user says downloadmenu failed; BOM downloader 404; missing archive; checksum mismatch.
How do I install Sdaf Media Diagnostics in Claude Code?
Run `npx skills add Azure/sap-automation --skill sdaf-media-diagnostics -a claude-code`. Or copy the skill folder (skills/sdaf-media-diagnostics in Azure/sap-automation) into .claude/skills/sdaf-media-diagnostics in your project. Claude Code loads it when a task matches its description.
How do I install Sdaf Media Diagnostics in Codex?
Run `npx skills add Azure/sap-automation --skill sdaf-media-diagnostics -a codex`. Or copy the skill folder (skills/sdaf-media-diagnostics in Azure/sap-automation) into .agents/skills/sdaf-media-diagnostics in your project. Codex loads it when a task matches its description.
Can I use Sdaf Media Diagnostics 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-diagnostics -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-diagnostics, .gemini/skills/sdaf-media-diagnostics, .github/skills/sdaf-media-diagnostics and .opencode/skills/sdaf-media-diagnostics in your project.
What does Sdaf Media Diagnostics need to run?
SKILL.md names no scripts, command-line tools or credentials: Sdaf Media Diagnostics is instructions for the agent only. Its frontmatter pre-approves these tools: shell.
Does Sdaf Media Diagnostics 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 Diagnostics 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 Diagnostics use?
Sdaf Media Diagnostics 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 Diagnostics use?
About 1.3k tokens (SKILL.md is roughly 5.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 289 tokens, read only when the agent opens those files.
What are the alternatives to Sdaf Media Diagnostics?
Skills that share tags, products or a category with Sdaf Media Diagnostics: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sdaf Media Diagnostics?
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 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.