New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Sdaf Readiness Check

by Azure in Azure/sap-automation

Pre-flight an SDAF host, subscription, and configuration set BEFORE any deploy.

OfficialMITAuto-check passedDevOps & Cloud

Install Sdaf Readiness Check

skills CLI
$ npx skills add Azure/sap-automation --skill sdaf-readiness-check -a claude-code

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

GitHub CLI
$ gh skill install Azure/sap-automation sdaf-readiness-check --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-readiness-check .claude/skills/sdaf-readiness-check && 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-readiness-check
GitHub stars
146
Token cost
~1.2k tokens
SKILL.md length
514 words
Files
2 (incl. references)
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

Pre-flight an SDAF host, subscription, and configuration set BEFORE any deploy.

  • Works in 3 steps: Documented "Before you begin" gates → Run the documented readiness checks → Route any failure before deploying
  • A user says pre-flight SDAF
  • SKILL.md covers When to invoke, Preconditions, Recipe and Hard rules, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sdaf Readiness Check is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Pre-flight an SDAF host, subscription, and configuration set BEFORE any deploy. Runs the required Linux toolchain check (checkworkstation.sh) as documented in docs/local/02-00-prepare-execution-environment.md § Readiness verification. Also walks the documented "Before you begin" gates from docs/local/01-00-prerequisites.md. Use when a user says "pre-flight SDAF", "check SDAF readiness", "review my tfvars", "am I ready to deploy the control plane", or "check SDAF prerequisites". Do NOT use to actually deploy (see…

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/host-readiness.md`).

It sits in DevOps & Cloud. It works with Linux. 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 pre-flight SDAF
  • Check SDAF readiness
  • Review my tfvars
  • Am I ready to deploy the control plane

Example prompts

  • “Before you begin”
  • “pre-flight SDAF”
  • “check SDAF readiness”
  • “/sdaf-readiness-check”

Requirements

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

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Documented "Before you begin" gates
  2. Run the documented readiness checks
  3. Route any failure before deploying

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 Readiness Check loads about 1.2k tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 167 tokens; SKILL.md has 514 words of instructions outside code blocks.

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

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). 514 words, ~1,226 tokens.

Download SKILL.mdSave it as .claude/skills/sdaf-readiness-check/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
sdaf-readiness-check
description
Pre-flight an SDAF host, subscription, and configuration set BEFORE any deploy. Runs the required Linux toolchain check (`check_workstation.sh`) as documented in `docs/local/02-00-prepare-execution-environment.md § Readiness verification`. Also walks the documented "Before you begin" gates from `docs/local/01-00-prerequisites.md`. Use when a user says "pre-flight SDAF", "check SDAF readiness", "review my tfvars", "am I ready to deploy the control plane", or "check SDAF prerequisites". Do NOT use to actually deploy (see sdaf-control-plane-bootstrap / sdaf-workload-zone / sdaf-sap-system) or to triage a failed run (see sdaf-failure-triage).
allowed-tools
shell
license
MIT

SDAF Readiness Check

Action-loop skill. Drives the shipped readiness helpers per the documented Readiness verification subsection, and honours the documented pre-deploy gates. Reports what was checked and what failed; refuses to invent checks the docs and shipped scripts do not describe.

When to invoke

Trigger on: "pre-flight", "readiness", "review tfvars", "before I deploy", "prerequisites for SDAF".

Do NOT trigger on: deploying a stage; installing SDAF; troubleshooting a run that already failed (use sdaf-failure-triage).

Preconditions

  • The SDAF checkout is available (env SAP_AUTOMATION_REPO_PATH).
  • The config workspace is available (env CONFIG_REPO_PATH).
  • Target subscription is picked (env ARM_SUBSCRIPTION_ID).

If any of the three env vars is unset, stop and print docs/local/troubleshooting.md § A required export is missing.

Recipe

Step 1 — Documented "Before you begin" gates

Walk the operator through the two doc-defined gates in this order:

  • docs/local/01-00-prerequisites.md § Before you begin, § Pin versions, § Plan identity and access, § Review networking, DNS, and quota, § Review configuration ownership, § Review gate.
  • docs/local/02-00-prepare-execution-environment.md § Before you begin, § Prepare the host, § Prepare configuration, § Protect secrets and transient files, § Review gate.

Do NOT summarise the identity role set from memory; the docs point at the identity-and-access section rather than restating the role set inline. Point the operator at that section and stop.

Step 2 — Run the documented readiness checks

docs/local/02-00-prepare-execution-environment.md § Readiness verification requires check_workstation.sh. Read its output as the authority on what it checks; do not narrate behaviour beyond what the script prints. Require non-empty versions for az, terraform, ansible, and jq, even when the script exits 0. See references/host-readiness.md for the minimal notes needed to route failures.

Do not run validate.sh against current workspace .tfvars; it expects the legacy JSON parameter shape, while current .tfvars use Terraform HCL. Review configuration through the documented stage-specific plan and review gate.

Exit-code discipline for each invocation:

  • 0 — the script signalled success. Read the output anyway; a printed warning is a real signal.
  • non-zero — a failure or a validation-gate refusal. Do not claim the check passed. Route the failure by the section named in references/host-readiness.md.
Show full SKILL.md (186 more words)Show less
Step 3 — Route any failure before deploying

If the required check reports a failure or any required version is blank, do not proceed to deploy. Route via sdaf-failure-triage if the failure symptom is ambiguous, or directly to the doc anchor named in references/host-readiness.md.

Hard rules

  • Do not infer or reconstruct undocumented behaviour of any readiness script (D19). If the docs, Get-Help, or shipped script output are silent, say so and stop.
  • Do not grant broad Azure roles "to bypass an error" (docs/local/troubleshooting.md § Azure authentication or authorization fails).
  • Do not claim success without checking the shipped script's exit code.
  • Do not replace the shipped scripts with an ad-hoc reimplementation.

What this skill does NOT do

  • Does not deploy anything.
  • Does not rotate credentials, mint identities, or grant roles.
  • Does not attempt to diagnose network paths beyond running the shipped URL check.
  • Does not summarise identity-role sets from memory (docs point to code / the identity-and-access section).

See also

  • sdaf-orientation-and-surface — surface choice, prints install commands.
  • sdaf-workspace-and-tfvars — current workspace layout and naming.
  • sdaf-control-plane-bootstrap — the first deploy step.
  • sdaf-failure-triage — for a run that has already failed.
  • docs/local/01-00-prerequisites.md, docs/local/02-00-prepare-execution-environment.md § Readiness verification, docs/local/troubleshooting.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-readiness-check of Azure/sap-automation.

  • SKILL.md
  • references/host-readiness.md

Open the folder on GitHubat commit 78835f0

Compare with similar skills

Sdaf Readiness Check 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 Readiness Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sdaf Readiness Check this skillAzure/sap-automation146—~1.2kAutomated safety check: PassMIT
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT
Helm Chart ScaffoldingCybereason-Public/owLSM28013 repos~381Automated safety check: PassGPL-2.0
Kubernetes ArchitectCybereason-Public/owLSM2809 repos~2.6kAutomated safety check: PassGPL-2.0
Swig CI Reproswig/swig6.3k—~1.2kAutomated safety check: PassCustom licence
Youtubeeat-pray-ai/yutu699—~1.1kAutomated safety check: PassMIT

Similar skills

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

    392k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Helm Chart Scaffolding

    Cybereason-Public/owLSM

    Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.

    280 GitHub starsUsed in 13 repos~381 tokens
    DevOps & CloudAuto-check passed

  • Kubernetes Architect

    Cybereason-Public/owLSM

    Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration.

    280 GitHub starsUsed in 9 repos~2.6k tokens
    DevOps & CloudAuto-check passed

  • Swig CI Repro

    swig/swig

    Reproduce a GitHub Actions Linux CI failure locally when it does not happen on your machine: a podman/docker image that mirrors the ubuntu-22.04 runner by reusing the real Tools/CI-linux-.sh install…

    6.3k GitHub stars~1.2k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed

  • Youtube

    eat-pray-ai/yutu

    A skill your agent uses whenever the user mentions YouTube, video uploads, channel management, playlists, video SEO, or any YouTube Data API operation.

    699 GitHub stars~1.1k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed

  • .NET Crash Dump Collection

    dotnet/skills

    Official

    Configures automatic crash dumps or captures dumps from running processes for modern .NET apps on Linux, macOS and Windows, including Docker and Kubernetes.

    5.6k GitHub starsUsed in 2 repos~1.1k tokens
    DevOps & CloudAuto-check passed

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 2 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 2 days ago
    Auto-check passed

  • Sdaf Quality Assurance

    Azure/sap-automation

    Official

    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.

    146 GitHub stars~1.6k tokensUpdated 2 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 2 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 2 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 2 days ago
    Auto-check passed

Works with

Categories

Questions about Sdaf Readiness Check

What does Sdaf Readiness Check do?

Pre-flight an SDAF host, subscription, and configuration set BEFORE any deploy. Sdaf Readiness Check is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Pre-flight an SDAF host, subscription, and configuration set BEFORE any deploy.

When should I use Sdaf Readiness Check?

Sdaf Readiness Check fits situations like: A user says pre-flight SDAF; check SDAF readiness; review my tfvars; am I ready to deploy the control plane.

How do I install Sdaf Readiness Check in Claude Code?

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

How do I install Sdaf Readiness Check in Codex?

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

Can I use Sdaf Readiness Check 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-readiness-check -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-readiness-check, .gemini/skills/sdaf-readiness-check, .github/skills/sdaf-readiness-check and .opencode/skills/sdaf-readiness-check in your project.

What does Sdaf Readiness Check need to run?

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

Does Sdaf Readiness Check 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 Readiness Check 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 Readiness Check use?

Sdaf Readiness Check 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 Readiness Check use?

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

What are the alternatives to Sdaf Readiness Check?

Skills that share tags, products or a category with Sdaf Readiness Check: Openclaw Live Updater (openclaw/openclaw, 392k stars), Helm Chart Scaffolding (Cybereason-Public/owLSM, 280 stars), Kubernetes Architect (Cybereason-Public/owLSM, 280 stars) and Swig CI Repro (swig/swig, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sdaf Readiness Check?

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.