Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Triage a failed or suspicious SDAF run: distinguish a real failure from a green no-op or a clean plan reported as failure, map the observed symptom to a documented cause in…
Install Sdaf Failure Triage
$ npx skills add Azure/sap-automation --skill sdaf-failure-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/sap-automation sdaf-failure-triage --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-failure-triage .claude/skills/sdaf-failure-triage && 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-failure-triage" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-failure-triage into .claude/skills/sdaf-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-failure-triage", 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-failure-triageType 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-failure-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/sap-automation sdaf-failure-triage --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-failure-triage .agents/skills/sdaf-failure-triage && 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-failure-triage" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-failure-triage into .agents/skills/sdaf-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-failure-triage", 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-failure-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/sap-automation sdaf-failure-triage --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-failure-triage .cursor/skills/sdaf-failure-triage && 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-failure-triage" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-failure-triage into .cursor/skills/sdaf-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-failure-triage", 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-failure-triage--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-failure-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/sap-automation sdaf-failure-triage --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-failure-triage .gemini/skills/sdaf-failure-triage && 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-failure-triage" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-failure-triage into .gemini/skills/sdaf-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-failure-triage", 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-failure-triageInstalls 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-failure-triage -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-failure-triage .github/skills/sdaf-failure-triage && 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-failure-triage" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-failure-triage into .github/skills/sdaf-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-failure-triage", 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-failure-triage -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-failure-triage --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-failure-triage .opencode/skills/sdaf-failure-triage && 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-failure-triage" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-failure-triage into .opencode/skills/sdaf-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-failure-triage", 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-failure-triage- GitHub stars
- 146
- Token cost
- ~1.7k tokens
- SKILL.md length
- 688 words
- Files
- 2 (incl. references)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Triage a failed or suspicious SDAF run: distinguish a real failure from a green no-op or a clean plan reported as failure, map the observed symptom to a documented cause in…
- Works in 4 steps: Establish exit-code intent → Map the symptom → Route to the stage-owning skill → …
- A user says SDAF run failed
- SKILL.md covers When to invoke, Preconditions, Recipe and Special cases (documented), plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sdaf Failure Triage is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Triage a failed or suspicious SDAF run: distinguish a real failure from a green no-op or a clean plan reported as failure, map the observed symptom to a documented cause in docs/local/troubleshooting.md, and hand off to the stage-owning skill for retry. Use when a user says "SDAF run failed", "my deploy exited non-zero", "the plan was clean but exit 1", "the run said success but nothing was deployed", "state lock error", "unexpected replacement", "control plane stopped partway", "generated hosts.yaml missing"…
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/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 SDAF run failed
- My deploy exited non-zero
- The plan was clean but exit 1
- The run said success but nothing was deployed
Example prompts
- “SDAF run failed”
- “my deploy exited non-zero”
- “the plan was clean but exit 1”
- “/sdaf-failure-triage”
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 Failure Triage loads about 1.7k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 176 tokens; SKILL.md has 688 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). 688 words, ~1,734 tokens.
Download SKILL.mdSave it as
.claude/skills/sdaf-failure-triage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- sdaf-failure-triage
- description
- Triage a failed or suspicious SDAF run: distinguish a real failure from a green no-op or a clean plan reported as failure, map the observed symptom to a documented cause in `docs/local/troubleshooting.md`, and hand off to the stage-owning skill for retry. Use when a user says "SDAF run failed", "my deploy exited non-zero", "the plan was clean but exit 1", "the run said success but nothing was deployed", "state lock error", "unexpected replacement", "control plane stopped partway", "generated hosts.yaml missing", "workload-zone private endpoint failure", "workload-zone subnet policy failure", or "SDAF exit 2". Do NOT use to actually deploy or to redesign the workspace layout.
- allowed-tools
- shell
- license
- MIT
SDAF Failure Triage
Action-loop skill. The entry point for "it broke". Maps observed symptoms to
the documented cause in docs/local/troubleshooting.md (and the stage docs'
own § Validate / § Configuration preparation sections), then hands off
to the stage-owning skill. This skill is a router, not the owner of any
per-stage fix.
When to invoke
Trigger on: "SDAF run failed", "the plan was clean but the run exited 1", "success but nothing deployed", "state lock", "unexpected replacement", "control plane stopped partway", "generated hosts.yaml missing", "BOM files not found", "removal is incomplete", "Ansible playbook failed", "workload-zone private endpoint failure", "workload-zone subnet policy failure", "SDAF exit 2".
Do NOT trigger on: pre-flight readiness (sdaf-readiness-check), authoring
tfvars (sdaf-workspace-and-tfvars), fresh deploy of a stage.
Preconditions
- Collect the exit code and the last 200 lines of the run log before invoking. If you have neither, ask for them; do not guess.
Recipe
Step 1 — Establish exit-code intent
0— Terraform / script signalled success. Still worth verifying the expected artefacts exist (some symptoms below are "success but nothing deployed").- non-zero — real failure OR a validation-gate refusal (
exit 2fromvalidate.shor a stage script). Treatexit 2as a validation gate that was intentionally tripped, not a bug; do not silence it.
Step 2 — Map the symptom
Walk references/symptom-map.md, which lists
every named failure class from docs/local/troubleshooting.md plus the
documented workload-zone private-endpoint / subnet-policy case, with the
owning skill for removal/state/install/HA/media/sovereign routes. Pick the
first row whose symptom matches the observed signature.
If nothing matches, walk the "canonical 'clean plan reported as failure'
note" in references/symptom-map.md, which walks the stage § Validate
sections. If nothing there matches either, say docs are silent on this
symptom and stop — do not invent a cause.
Step 3 — Route to the stage-owning skill
Route to the stage-owning skill for the actual retry:
| Stage / symptom | Owning skill |
|---|---|
| Control plane | sdaf-control-plane-bootstrap |
| Workload zone (including the private-endpoint / subnet-policy workaround) | sdaf-workload-zone |
| SAP system | sdaf-sap-system |
| SAP installation / numbered playbooks | sdaf-sap-installation |
| Media acquisition preconditions / clean downloader path | sdaf-media-acquisition |
| Media archive / checksum / extractor / BOM-processing failures | sdaf-media-diagnostics |
HA cluster evidence / crm / pcs / fencing | sdaf-ha-diagnostics |
| Explicit Terraform state lock / import / remove / drift repair | sdaf-state-management |
| Safe teardown / incomplete removal / control-plane step trap | sdaf-safe-removal |
| Azure Government / sovereign-cloud deltas | sdaf-sovereign-cloud |
| WORKSPACES/tfvars authoring issue | sdaf-workspace-and-tfvars |
| BOM file location / selection | sdaf-bom-selection |
Step 4 — Confirm before retry
The retry safety rules — no --force / no --auto-approve / no state
edits / no concurrent execution / do not delete .progress markers — are
enforced by the shipped repo instructions (.github/copilot-instructions.md)
and by each stage skill's own recipe. This triage skill defers to the
stage-owning skill's retry section rather than restating those rules.
Show full SKILL.md (264 more words)Show less
Special cases (documented)
Interrupted control-plane removal reports success
docs/local/troubleshooting.md § Removal is incomplete and
docs/local/07-00-operations.md § Remove resources: an interrupted
control-plane removal can exit "successfully" after step=1 without
deleting the deployer. Diagnostic path: inspect
.sap_deployment_automation, persisted step, library destroy result, and
remaining deployer state / resources. Do not edit step to bypass the
guard. sdaf-safe-removal owns the documented diagnostic path and any
approved retry.
success but nothing was deployed
Cross-check the expected artefacts for the stage:
- Control plane: state in library storage account, metadata under
.sap_deployment_automation, summary written (docs/local/03-00-control-plane.md § Validate,§ Outcome). - Workload zone:
.tfvarsand backend metadata in the state account'stfvarscontainer, zone Key Vault deployed (docs/local/04-00-workload-zone.md § Validate,§ Outcome). - SAP system: infra deployed and
<SID>_hosts.yaml/sap-parameters.yamlpresent (docs/local/05-00-sap-system.md § Validate,§ Outcome).
If artefacts are missing, treat the "success" as false and route to the stage-owning skill.
Hard rules
- Documented behaviour only (D19). If the symptom does not match a
docs/local/troubleshooting.mdsection, a documented§ Configuration preparation/§ Validatecross-check, or a named owner row inreferences/symptom-map.md, say docs are silent and stop. - Do not silently pass a non-zero exit code.
- Do not narrate benign log noise as a failure without a documented anchor.
What this skill does NOT do
- Does not deploy or retry directly.
- Does not repair Terraform state;
sdaf-state-managementowns that. - Does not restate stage-specific safety rules — the stage skills and
.github/copilot-instructions.mdown those. - Does not replace the documented media/install/HA/removal/sovereign owners.
- Does not reason about undocumented failure modes (e.g. end-to-end Government
beyond
sdaf-sovereign-cloud, air-gapped, or undocumentedARM_ENVIRONMENTflows).
See also
sdaf-control-plane-bootstrap,sdaf-workload-zone,sdaf-sap-system,sdaf-sap-installation,sdaf-media-acquisition,sdaf-media-diagnostics,sdaf-ha-diagnostics,sdaf-state-management,sdaf-safe-removal,sdaf-sovereign-cloud,sdaf-workspace-and-tfvars,sdaf-bom-selection.docs/local/troubleshooting.md,docs/local/07-00-operations.md,docs/local/04-00-workload-zone.md § Configuration preparation.
© 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-failure-triage of Azure/sap-automation.
- SKILL.md
- references/symptom-map.md
Open the folder on GitHubat commit 78835f0
Compare with similar skills
Sdaf Failure Triage 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 Failure Triage this skillAzure/sap-automation | 146 | — | ~1.7k | 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 Failure Triage
What does Sdaf Failure Triage do?
Triage a failed or suspicious SDAF run: distinguish a real failure from a green no-op or a clean plan reported as failure, map the observed symptom to a documented cause in…. Sdaf Failure Triage is an agent skill from Azure/sap-automation, published by the product's own GitHub organization.md, and hand off to the stage-owning skill for retry.
When should I use Sdaf Failure Triage?
Sdaf Failure Triage fits situations like: A user says SDAF run failed; my deploy exited non-zero; the plan was clean but exit 1; the run said success but nothing was deployed.
How do I install Sdaf Failure Triage in Claude Code?
Run `npx skills add Azure/sap-automation --skill sdaf-failure-triage -a claude-code`. Or copy the skill folder (skills/sdaf-failure-triage in Azure/sap-automation) into .claude/skills/sdaf-failure-triage in your project. Claude Code loads it when a task matches its description.
How do I install Sdaf Failure Triage in Codex?
Run `npx skills add Azure/sap-automation --skill sdaf-failure-triage -a codex`. Or copy the skill folder (skills/sdaf-failure-triage in Azure/sap-automation) into .agents/skills/sdaf-failure-triage in your project. Codex loads it when a task matches its description.
Can I use Sdaf Failure Triage 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-failure-triage -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-failure-triage, .gemini/skills/sdaf-failure-triage, .github/skills/sdaf-failure-triage and .opencode/skills/sdaf-failure-triage in your project.
What does Sdaf Failure Triage need to run?
SKILL.md names no scripts, command-line tools or credentials: Sdaf Failure Triage is instructions for the agent only. Its frontmatter pre-approves these tools: shell.
Does Sdaf Failure Triage 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 Failure Triage 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 Failure Triage use?
Sdaf Failure Triage 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 Failure Triage use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 1.2k tokens, read only when the agent opens those files.
What are the alternatives to Sdaf Failure Triage?
Skills that share tags, products or a category with Sdaf Failure Triage: 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 Failure Triage?
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.