Official agent skill

Sdaf Quality Assurance

by Azure in 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.

OfficialMITAuto-check passedTesting & QA

Install Sdaf Quality Assurance

skills CLI
$ npx skills add Azure/sap-automation --skill sdaf-quality-assurance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Azure/sap-automation sdaf-quality-assurance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sdaf-quality-assurance .claude/skills/sdaf-quality-assurance && rm -rf skills-src

Use ~/.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/

Facts

Skill name
sdaf-quality-assurance
GitHub stars
146
Token cost
~1.6k tokens
SKILL.md length
581 words
Files
2 (incl. references)
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 4 steps: Change to the system workspace → Confirm required artifacts → Start with configuration checks → …
  • A user says run quality assurance
  • SKILL.md covers When to invoke, Surface availability, Preconditions and Safety and test modes, plus 6 more sections
  • Reaches github.com

What it does

Sdaf Quality Assurance is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. 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. Choose configuration checks vs functional tests, apply TESTGROUPS / TESTCASES safely, interpret qualityassurance/ and logs/, and enforce the documented boundary that the GitHub Actions wrapper is still pending. Use when a user says "run quality assurance", "run configuration checks", "pipeline 13 QA", "offline HA validation", or "why does the report say No…

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/qa-entrypoints.md`).

It sits in Testing & QA, covering QA and bug reports and Test generation. It works with Azure DevOps, GitHub Actions and Microsoft Azure. 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 run quality assurance
  • Run configuration checks
  • Offline HA validation
  • Why does the report say No test results found

Example prompts

  • “run quality assurance”
  • “run configuration checks”
  • “pipeline 13 QA”
  • “/sdaf-quality-assurance”

Requirements

  • Pre-approved tools (allowed-tools): shell

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Change to the system workspace
  2. Confirm required artifacts
  3. Start with configuration checks
  4. Narrow a functional run only by exporting the selection first

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).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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 Quality Assurance loads about 1.6k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 194 tokens; SKILL.md has 581 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~194
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.9k

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). 581 words, ~1,562 tokens.

Download SKILL.mdSave it as .claude/skills/sdaf-quality-assurance/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
sdaf-quality-assurance
description
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. Choose configuration checks vs functional tests, apply `TEST_GROUPS` / `TEST_CASES` safely, interpret `quality_assurance/` and `logs/`, and enforce the documented boundary that the GitHub Actions wrapper is still pending. Use when a user says "run quality assurance", "run configuration checks", "pipeline 13 QA", "offline HA validation", or "why does the report say No test results found". Do NOT use to deploy the SAP system or generate `sap-parameters.yaml` / `<SID>_hosts.yaml` (see `sdaf-sap-system`), or for a generic failed-run report with no QA-stage context (see `sdaf-failure-triage`).
allowed-tools
shell
license
MIT

SDAF Quality Assurance

Action-loop skill. Validate an already deployed and installed SAP system through SDAF's own QA surfaces only. Durable anchors and the full test matrix live in references/qa-entrypoints.md.

When to invoke

Trigger on: "run quality assurance", "run configuration checks", "run SAP functional tests", "pipeline 13 QA", "offline HA validation", "read the QA report", "why does the report say No test results found", or "which TEST_GROUPS / TEST_CASES should I use".

Do NOT trigger on: deploying the SAP-system infrastructure, generating sap-parameters.yaml or <SID>_hosts.yaml, software download, or a generic "my SDAF run failed" report that is not yet tied to the QA stage.

Surface availability

SurfaceAvailabilityWhat to do
Local / scriptedFully documented and runnable through the quality-assurance menuUse this skill directly.
Azure DevOpsThe operator documentation describes pipeline 13; the public bootstrap wrapper is still documented as proposedUse this skill only if the operator already has a real pipeline-13 path.
GitHub ActionsWrapper workflow is still documented as pendingSay the docs mark it pending and stop; do not invent the workflow.

Preconditions

  • The SAP system is already installed and running; QA validates a configured system and does not install one.
  • The system workspace contains sap-parameters.yaml and <SAP_SID>_hosts.yaml.
  • Azure sign-in works and the operator can read the workload-zone Key Vault.
  • The execution host can reach every inventory host over SSH.
  • Local runs additionally require outbound https://github.com, sudo, and ARM_CLIENT_ID on multi-identity hosts.
  • Azure DevOps runs additionally require a self-hosted agent.

Safety and test modes

  • ConfigurationChecks and offline HA validation are non-disruptive.
  • Online SAPFunctionalTests are disruptive; require an approved maintenance window.
  • Supported functional families are DB HA, SCS HA, and Azure Backup DB.
  • Exact menu / pipeline / framework playbook mapping is in the reference file.

Local path

  1. Change to the system workspace:

    bash
    cd "$CONFIG_REPO_PATH/WORKSPACES/SYSTEM/<SAP_SYSTEM>"
  2. Confirm required artifacts:

    bash
    test -f sap-parameters.yaml
    test -f "<SAP_SID>_hosts.yaml"
  3. Start with configuration checks:

    bash
    run_with_key_cleanup() (
      set -e; trap 'rm -f -- "$PWD/sshkey"' EXIT
      "$@"
    )
    run_with_key_cleanup \
      "$SAP_AUTOMATION_REPO_PATH/deploy/ansible/quality_assurance_menu.sh" \
      && test ! -e "$PWD/sshkey"
  4. Narrow a functional run only by exporting the selection first:

    bash
    TEST_GROUPS="HA_SCS" \
    TEST_CASES="ascs-migration" \
    run_with_key_cleanup \
      "$SAP_AUTOMATION_REPO_PATH/deploy/ansible/quality_assurance_menu.sh" \
      && test ! -e "$PWD/sshkey"
Show full SKILL.md (268 more words)Show less

Selection rules

  • TEST_GROUPS is one exact group name.
  • TEST_CASES is a comma-separated list of framework task_name values, not display names; e.g. ascs-migration, not Manual ASCS Migration.
  • Always set TEST_GROUPS when setting TEST_CASES.
  • The preparation playbook writes the resolved selection to artifacts/qa_test_selection.json; use it to confirm the requested scope.
  • Validate group and case names against the pinned framework version from deploy/ansible/vars/ansible-input-api.yaml.
  • Offline HA runs additionally require offline_validation/<inventory host>/cib; otherwise stop before the playbook.

Azure DevOps contract

When an SDAF ADO environment already exposes pipeline 13, this skill owns the stage semantics:

  • queue-time selection lives in test_type, sap_functional_test_type, test_groups, test_cases, and offline_mode;
  • the prep script validates extra_params as -e key=value only;
  • the run performs Quality Assurance Setup, then Quality Assurance Execution for the selected framework;
  • logs and reports are collected from SYSTEM/<config>/logs and SYSTEM/<config>/quality_assurance.

If the operator cannot point to an actual wired pipeline-13 path, stop at the documented availability boundary rather than assuming the proposed wrapper is present.

Validate

Confirm all of the following:

  • quality_assurance/ contains the HTML report.
  • logs/<test_group_invocation_id>.log exists; it is the machine-readable JSONL result record.
  • logs/execution_<timestamp>.log exists and matches the completion banner.
  • No test results found. means no results log was produced, not that the run passed.
  • For functional tests, the cluster returned to its expected state before the maintenance window closed.

Routing boundaries

  • Need to deploy the system first or generate sap-parameters.yaml / <SID>_hosts.yaml → sdaf-sap-system.
  • Generic failed-run triage or a non-QA symptom → sdaf-failure-triage.
  • Asked for a GitHub Actions QA wrapper → say the docs mark it pending and stop.
  • Do not infer undocumented STAF-side behaviour or additional surfaces.

See also

  • references/qa-entrypoints.md
  • sdaf-sap-system, sdaf-failure-triage
  • docs/local/07-10-quality-assurance.md, docs/deployment-options.md, docs/documentation-source-map.md, docs/supportability.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-quality-assurance of Azure/sap-automation.

  • SKILL.md
  • references/qa-entrypoints.md

Open the folder on GitHubat commit 78835f0

Compare with similar skills

Sdaf Quality Assurance 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.

Sdaf Quality Assurance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sdaf Quality Assurance this skillAzure/sap-automation146—~1.6kAutomated safety check: PassMIT
Azsdk Common Pipeline AnalysisAzure/azure-sdk-tools134—~1.2kAutomated safety check: PassMIT
Azure App TestingMicrosoftDocs/Agent-Skills776—~3.6kAutomated safety check: PassCC-BY-4.0
Azure Playwright WorkspacesMicrosoftDocs/Agent-Skills776—~1.5kAutomated safety check: PassCC-BY-4.0
Azure Test PlansMicrosoftDocs/Agent-Skills776—~971Automated safety check: PassCC-BY-4.0
Azure BoardsMicrosoftDocs/Agent-Skills776—~2.4kAutomated safety check: PassCC-BY-4.0

Similar skills

  • Azsdk Common Pipeline Analysis

    Azure/azure-sdk-tools

    Official

    Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format.

    134 GitHub stars~1.2k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Azure App Testing

    MicrosoftDocs/Agent-Skills

    Official

    Expert knowledge for Azure App Testing development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations…

    776 GitHub stars~3.6k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Azure Playwright Workspaces

    MicrosoftDocs/Agent-Skills

    Official

    Expert knowledge for Playwright Workspaces development including troubleshooting, best practices, decision making, limits & quotas, security, and configuration.

    776 GitHub stars~1.5k tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Azure Test Plans

    MicrosoftDocs/Agent-Skills

    Official

    Expert knowledge for Azure Test Plans development including limits & quotas, security, configuration, and integrations & coding patterns.

    776 GitHub stars~971 tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Azure Boards

    MicrosoftDocs/Agent-Skills

    Official

    Expert knowledge for Azure Boards development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, and integrations & coding patterns.

    776 GitHub stars~2.4k tokensUpdated 5 days ago
    Product & Project ManagementAuto-check passed
  • Setup Pipeline

    microsoft/power-platform-skills

    Official

    Sets up a Power Platform Pipeline for automated Power Pages deployments.

    984 GitHub stars~11k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

More from Azure/sap-automation

All 19 skills in this repo
  • Sdaf Bom Selection

    Azure/sap-automation

    Official

    Pick the right SDAF BOM for a target SAP product / release / DB platform / version / kernel / topology.

    146 GitHub stars~1.6k tokensUpdated 3 days ago
    Auto-check passed
  • Sdaf Orientation And Surface

    Azure/sap-automation

    Official

    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…

    146 GitHub stars~1.6k tokensUpdated 3 days ago
    Auto-check passed
  • Sdaf Sap Installation

    Azure/sap-automation

    Official

    Guide SDAF operating-system, database, and SAP installation after the SAP-system workspace and reviewed media are ready.

    146 GitHub stars~1.5k tokensUpdated 3 days ago
    Auto-check passed
  • Sdaf Sovereign Cloud

    Azure/sap-automation

    Official

    Explain the current SDAF sovereign-cloud deltas without inventing a generic "all sovereigns" runbook.

    146 GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check passed
  • Sdaf State Management

    Azure/sap-automation

    Official

    Inspect and repair SDAF Terraform state safely before any reviewed import/remove.

    146 GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed
  • Sdaf Workspace And Tfvars

    Azure/sap-automation

    Official

    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.

    146 GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Sdaf Quality Assurance

What does Sdaf Quality Assurance do?

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. Sdaf Quality Assurance is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. 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.

When should I use Sdaf Quality Assurance?

Sdaf Quality Assurance fits situations like: A user says run quality assurance; run configuration checks; offline HA validation; why does the report say No test results found.

How do I install Sdaf Quality Assurance in Claude Code?

Run `npx skills add Azure/sap-automation --skill sdaf-quality-assurance -a claude-code`. Or copy the skill folder (skills/sdaf-quality-assurance in Azure/sap-automation) into .claude/skills/sdaf-quality-assurance in your project. Claude Code loads it when a task matches its description.

How do I install Sdaf Quality Assurance in Codex?

Run `npx skills add Azure/sap-automation --skill sdaf-quality-assurance -a codex`. Or copy the skill folder (skills/sdaf-quality-assurance in Azure/sap-automation) into .agents/skills/sdaf-quality-assurance in your project. Codex loads it when a task matches its description.

Can I use Sdaf Quality Assurance 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-quality-assurance -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-quality-assurance, .gemini/skills/sdaf-quality-assurance, .github/skills/sdaf-quality-assurance and .opencode/skills/sdaf-quality-assurance in your project.

What does Sdaf Quality Assurance need to run?

SKILL.md names no scripts, command-line tools or credentials: Sdaf Quality Assurance is instructions for the agent only. Its frontmatter pre-approves these tools: shell.

Does Sdaf Quality Assurance access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Sdaf Quality Assurance 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 Quality Assurance use?

Sdaf Quality Assurance 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 Quality Assurance use?

About 1.6k tokens (SKILL.md is roughly 6.2k 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 352 tokens, read only when the agent opens those files.

What are the alternatives to Sdaf Quality Assurance?

Skills that share tags, products or a category with Sdaf Quality Assurance: Azsdk Common Pipeline Analysis (Azure/azure-sdk-tools, 134 stars), Azure App Testing (MicrosoftDocs/Agent-Skills, 776 stars), Azure Playwright Workspaces (MicrosoftDocs/Agent-Skills, 776 stars) and Azure Test Plans (MicrosoftDocs/Agent-Skills, 776 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sdaf Quality Assurance?

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.