Official agent skill

Sdaf Ha Topology

Choose the documented SDAF high-availability design before SAP-system deployment.

OfficialMITAuto-check passedDevOps & Cloud

Install Sdaf Ha Topology

skills CLI

$ npx skills add Azure/sap-automation --skill sdaf-ha-topology -a claude-code

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

GitHub CLI

$ gh skill install Azure/sap-automation sdaf-ha-topology --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-ha-topology .claude/skills/sdaf-ha-topology && 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/

Paste into Claude Code

Install the "sdaf-ha-topology" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-ha-topology into .claude/skills/sdaf-ha-topology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-ha-topology", 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

$skill-installer install https://github.com/Azure/sap-automation/tree/main/skills/sdaf-ha-topology

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

skills CLI

$ npx skills add Azure/sap-automation --skill sdaf-ha-topology -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Azure/sap-automation sdaf-ha-topology --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sdaf-ha-topology .agents/skills/sdaf-ha-topology && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sdaf-ha-topology" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-ha-topology into .agents/skills/sdaf-ha-topology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-ha-topology", 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.

skills CLI

$ npx skills add Azure/sap-automation --skill sdaf-ha-topology -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Azure/sap-automation sdaf-ha-topology --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sdaf-ha-topology .cursor/skills/sdaf-ha-topology && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sdaf-ha-topology" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-ha-topology into .cursor/skills/sdaf-ha-topology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-ha-topology", 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

$ gemini skills install https://github.com/Azure/sap-automation.git --path skills/sdaf-ha-topology

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Azure/sap-automation --skill sdaf-ha-topology -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Azure/sap-automation sdaf-ha-topology --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sdaf-ha-topology .gemini/skills/sdaf-ha-topology && rm -rf skills-src

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

Paste into Gemini CLI

Install the "sdaf-ha-topology" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-ha-topology into .gemini/skills/sdaf-ha-topology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-ha-topology", 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.

GitHub CLI

$ gh skill install Azure/sap-automation sdaf-ha-topology

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

skills CLI

$ npx skills add Azure/sap-automation --skill sdaf-ha-topology -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sdaf-ha-topology .github/skills/sdaf-ha-topology && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "sdaf-ha-topology" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-ha-topology into .github/skills/sdaf-ha-topology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-ha-topology", 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.

skills CLI

$ npx skills add Azure/sap-automation --skill sdaf-ha-topology -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Azure/sap-automation sdaf-ha-topology --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Azure/sap-automation.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sdaf-ha-topology .opencode/skills/sdaf-ha-topology && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sdaf-ha-topology" agent skill from https://github.com/Azure/sap-automation/tree/main/skills/sdaf-ha-topology into .opencode/skills/sdaf-ha-topology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdaf-ha-topology", 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-ha-topology
GitHub stars: 146
Token cost: ~1.3k tokens
SKILL.md length: 569 words
Files: 2 (incl. references)
Skills in repo: 19
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Choose the documented SDAF high-availability design before SAP-system deployment.

Works in 7 steps: Confirm the support boundary first.… → Split the question into layers. Treat HA… → Confirm the documented platform path. Use → …
A user asks which HA topology to deploy
SKILL.md covers When to invoke, Preconditions, Decision loop and Validate before deployment, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sdaf Ha Topology is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Choose the documented SDAF high-availability design before SAP-system deployment. Use when a user asks which HA topology to deploy, whether to use AFA or SBD, AFS or ANF, HANA scale-up or scale-out, whether ANGI is allowed, or which HA inputs must be set before deployment. Ground answers in the current support matrix, Ansible roles, sample tfvars, and validation logic. Do NOT use for live cluster diagnosis (sdaf-ha-diagnostics) or for running the installers (sdaf-sap-installation).

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/topology-decision-guide.md`).

It sits in DevOps & Cloud, covering Backup and disaster recovery, Deployment and 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

A user asks which HA topology to deploy
Whether to use AFA
Whether ANGI is allowed
Which HA inputs must be set before deployment

Example prompts

“/sdaf-ha-topology”

Requirements

Pre-approved tools (allowed-tools): shell

Workflow steps

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

Confirm the support boundary first. Start with
Split the question into layers. Treat HA as separate design choices for
Confirm the documented platform path. Use
Choose quorum / fencing deliberately. The tfvar contract exposes AFA,
Choose shared storage deliberately. Use current docs and mount logic
Handle HANA-only forks explicitly. For HANA, decide scale-up vs
Route rather than guess. If the user is asking how to deploy the chosen

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 Ha Topology 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 126 tokens; SKILL.md has 569 words of instructions outside code blocks.

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

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). 569 words, ~1,250 tokens.

Download SKILL.mdSave it as .claude/skills/sdaf-ha-topology/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: sdaf-ha-topology
description: Choose the documented SDAF high-availability design before SAP-system deployment. Use when a user asks which HA topology to deploy, whether to use AFA or SBD, AFS or ANF, HANA scale-up or scale-out, whether ANGI is allowed, or which HA inputs must be set before deployment. Ground answers in the current support matrix, Ansible roles, sample tfvars, and validation logic. Do NOT use for live cluster diagnosis (sdaf-ha-diagnostics) or for running the installers (sdaf-sap-installation).
allowed-tools: shell
license: MIT

SDAF HA Topology

Context-primer for pre-deploy HA design. Keep this skill short and route to references/topology-decision-guide.md for the detailed OS/DB/storage matrices, sample-backed examples, and source map.

When to invoke

Trigger on:

"Which SDAF HA topology should I use?"
"AFA or shared-disk / iSCSI quorum?"
"AFS or ANF for this SAP HA design?"
"Should HANA stay scale-up or move to scale-out?"
"Can I enable SAPHanaSR-angi on this OS release?"
"What HA inputs do I need in system tfvars before deployment?"

Do NOT trigger on:

a live cluster failure, fencing event, or crm / pcs diagnosis — use sdaf-ha-diagnostics
running numbered install stages or partial-install recovery — use sdaf-sap-installation
generic SAP-system Terraform deployment without an HA design question — use sdaf-sap-system

Preconditions

Before answering, know or ask for:

target operating system and version
target database platform
whether HA is required for central services, the database tier, or both
whether the question is design-time or an already-deployed cluster problem

Decision loop

Confirm the support boundary first. Start with docs/supportability.md. A listed OS, database, or storage option does not make every cross-combination valid. If the requested combination is not explicitly backed by current docs and code, say docs are silent and stop.
Split the question into layers. Treat HA as separate design choices for:
- SAP central services: scs_server_count, scs_high_availability, scs_cluster_type
- database tier: database_high_availability, database_cluster_type, and for HANA database_HANA_use_scaleout_scenario
Confirm the documented platform path. Use docs/supportability.md and the current SAP-system input documentation. Do not infer that every listed database has an SDAF-managed HA topology.
Choose quorum / fencing deliberately. The tfvar contract exposes AFA, ASD, and ISCSI for both SCS and DB tiers. AFA needs fencing credentials unless use_msi_for_clusters = true. ASD / ISCSI take the SBD path, so the OS release must satisfy the current role gates before cluster creation.
Choose shared storage deliberately. Use current docs and mount logic:
- AFS for shared SAP file systems only
- ANF for applicable shared and database file systems
- custom NFS as organization-owned design, not a Microsoft-owned reference
Handle HANA-only forks explicitly. For HANA, decide scale-up vs scale-out and, separately, whether use_saphanasr_angi is allowed on the target OS. Do not apply scale-out or ANGI guidance to Oracle, DB2, ASE, or SQL Server.
Route rather than guess. If the user is asking how to deploy the chosen design, hand off to sdaf-sap-system. If the user is asking why an existing cluster failed, hand off to sdaf-ha-diagnostics.

Show full SKILL.md (173 more words)Show less

Validate before deployment

Use the documented SAP-system validation step as the pre-deploy gate. For HA answers, make sure the selected path can supply:

cluster-aware base inputs: database_high_availability, database_cluster_type, scs_high_availability, scs_cluster_type, use_msi_for_clusters, platform
for SCS HA: shared storage, NFS_provider, and central-services load-balancer inputs
for AFA without MSI: fencing client ID, password, subscription, and tenant
for HANA / DB2 AFA database HA: the database load-balancer IP
for HANA scale-out: standby / observer / shared-storage inputs that match the selected path

Hard safety rules

Do not infer support from one sample, one BOM, or one tfvar alone.
Do not promise an ASE database-HA topology from the current DB-HA playbook.
Do not apply HANA-only scale-out or ANGI guidance to non-HANA databases.
Do not use Azure Files NFS as a database-file-system answer.
Do not generalize Pacemaker validation guidance to Windows clustering.
If docs, samples, and current roles disagree, stop and call out the mismatch.

Hand-off

deploy the chosen infrastructure path -> sdaf-sap-system
run OS / DB / SAP install stages -> sdaf-sap-installation
diagnose a live cluster or fencing issue -> sdaf-ha-diagnostics
run post-deploy HA checks -> sdaf-quality-assurance

Files

SKILL.md and 1 other file (references) in skills/sdaf-ha-topology of Azure/sap-automation.

SKILL.md
references/topology-decision-guide.md

Open the folder on GitHubat commit 78835f0

Compare with similar skills

Sdaf Ha Topology 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 Ha Topology compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sdaf Ha Topology this skillAzure/sap-automation	146	—	~1.3k	Automated safety check: Pass	MIT	3 days ago
Spa Create Configsplunk/splunk-platform-automator	138	—	~3.5k	Automated safety check: Pass	Proprietary	5 days ago
Spa Add Test Scenariosplunk/splunk-platform-automator	138	—	~2.2k	Automated safety check: Pass	Proprietary	5 days ago
Ansible Infrastructure AutomationRightNow-AI/openfang	18k	—	~730	Automated safety check: Pass	Apache-2.0	3 mo ago
Supercheck Infrastructure Deploymentsupercheck-io/supercheck	215	—	~1.4k	Automated safety check: Notes	AGPL-3.0	today
Django Deployment Test Loophashgraph-online/awesome-codex-plugins	1.3k	—	~851	Automated safety check: Pass	MIT	yesterday

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…
138 GitHub stars~3.5k tokensUpdated 5 days ago
DevOps & CloudAuto-check passed
Spa Add Test Scenario
splunk/splunk-platform-automator
A skill your agent uses when adding app scope/routing test coverage (deployer, CM, DS, direct).
138 GitHub stars~2.2k tokensUpdated 5 days ago
DevOps & CloudAuto-check passed
Ansible Infrastructure Automation
RightNow-AI/openfang
Guidance for writing idempotent Ansible playbooks, roles and inventories, with patterns for handlers, rolling deployments, Vault secrets and error handling.
18k GitHub stars~730 tokensUpdated 3 mo ago
DevOps & CloudAuto-check passed
Supercheck Infrastructure Deployment
supercheck-io/supercheck
Work on Supercheck Docker Compose, K3s, Kubernetes manifests, gVisor, OpenTofu/Hetzner, secrets, external services, autoscaling, backups, disaster recovery, DNS/TLS, or production deployment.
215 GitHub stars~1.4k tokensUpdated today
DevOps & CloudAuto-check: notes
Django Deployment Test Loop
hashgraph-online/awesome-codex-plugins
Make Django deployment changes test-driven across Docker, production settings, Gunicorn, WhiteNoise/static files, environment variables, Ansible/server setup, staging smoke tests, and release checks.
1.3k GitHub stars~851 tokensUpdated yesterday
DevOps & CloudAuto-check passed
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
367 GitHub starsUsed in 2 repos~2.5k 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 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 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 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

Works with

Ansible

Questions about Sdaf Ha Topology

What does Sdaf Ha Topology do?

Choose the documented SDAF high-availability design before SAP-system deployment. Sdaf Ha Topology is an agent skill from Azure/sap-automation, published by the product's own GitHub organization. Choose the documented SDAF high-availability design before SAP-system deployment.

When should I use Sdaf Ha Topology?

Sdaf Ha Topology fits situations like: A user asks which HA topology to deploy; whether to use AFA; whether ANGI is allowed; which HA inputs must be set before deployment.

How do I install Sdaf Ha Topology in Claude Code?

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

How do I install Sdaf Ha Topology in Codex?

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

Can I use Sdaf Ha Topology 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-ha-topology -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-ha-topology, .gemini/skills/sdaf-ha-topology, .github/skills/sdaf-ha-topology and .opencode/skills/sdaf-ha-topology in your project.

What does Sdaf Ha Topology need to run?

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

Does Sdaf Ha Topology 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 Ha Topology 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 Ha Topology use?

Sdaf Ha Topology 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 Ha Topology use?

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

What are the alternatives to Sdaf Ha Topology?

Skills that share tags, products or a category with Sdaf Ha Topology: Spa Create Config (splunk/splunk-platform-automator, 138 stars), Spa Add Test Scenario (splunk/splunk-platform-automator, 138 stars), Ansible Infrastructure Automation (RightNow-AI/openfang, 18k stars) and Supercheck Infrastructure Deployment (supercheck-io/supercheck, 215 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sdaf Ha Topology?

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.

Install Sdaf Ha Topology

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

SDAF HA Topology

When to invoke

Preconditions

Decision loop

Validate before deployment

Hard safety rules

Hand-off

Files

Compare with similar skills

Similar skills

More from Azure/sap-automation

Related

Questions about Sdaf Ha Topology