Sdaf Sap Installation

What it does

When your agent uses it

• Run the SAP install playbooks
• Which installation stage should I select
• Resume after a partial DB/SAP playbook run
• Run configurationmenu.sh

Example prompts

• “run the SAP install playbooks”
• “which installation stage should I select”
• “resume after a partial DB/SAP playbook run”
• “/sdaf-sap-installation”

Requirements

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

Workflow steps

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

1. 1Preserve ordering
2. 2Local execution
3. 3Azure DevOps execution
4. 4Validate and recover

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

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

Always · name and description, kept in context so the agent knows when to use it

~177

When it runs · the whole SKILL.md, loaded when a task matches

~1.5k

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

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). 594 words, ~1,527 tokens.

name

sdaf-sap-installation

description

Guide SDAF operating-system, database, and SAP installation after the SAP-system workspace and reviewed media are ready. Covers the local `configuration_menu.sh` path, the Azure DevOps `05-DB-and-SAP-installation` booleans, `.progress`-based recovery, and the boundary between infrastructure deployment, media acquisition, and software installation. Use for "run the SAP install playbooks", "which installation stage should I select", "resume after a partial DB/SAP playbook run", "run configuration_menu.sh", or "queue 05-DB-and-SAP-installation with the right booleans". Do NOT use for `sdaf-sap-system`, `sdaf-media-acquisition`, `sdaf-media-diagnostics`, or `sdaf-quality-assurance`.

allowed-tools

shell

license

MIT

cd "$CONFIG_REPO_PATH/WORKSPACES/SYSTEM/<SAP_SYSTEM>"
run_with_key_cleanup() (
  set -e
  trap 'rm -f -- "$PWD/sshkey"' EXIT
  "$@"
)
run_with_key_cleanup \
  "$SAP_AUTOMATION_REPO_PATH/deploy/ansible/configuration_menu.sh" \
  && test ! -e "$PWD/sshkey"

© 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-sap-installation of Azure/sap-automation.

• SKILL.md
• references/install-stage-map.md

Open the folder on GitHubat commit 78835f0