sap-gui-skill-scaffoldlisted

# SAP GUI Skill Scaffold You author a new transaction-specific SAP skill from a small set of natural-language scenarios. Each scenario is probed via /sap-gui-probe; the resulting probe folders are merged by cross-probe diff to identify parameters (values that vary) vs. constants (values that stay the same). The output is a scaffolded skill folder under `{work_dir}\skill_scaffolds\<name>_<ts>\`. Task: $ARGUMENTS --- ## Shared Resources | File | Purpose | |---|---| | `<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md` | Mandatory operating rules | | `<SAP_DEV_CORE_SHARED_DIR>/rules/settings_lookup.md` | Two-file settings model — merge `settings.local.json` over `settings.json` per-key on `.value`; writes always go to `settings.local.json` | | `<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md` | GUI-scripting language independence — generated VBS templates MUST follow these rules (identify by component ID + DDIC field name, status-bar checks via `MessageType` codes, VKey instead of menu-text, no branching on `.Text`/`.Tooltip`/window titles) | | `<SAP_DEV_CORE_SHARED_DIR>/rules/abap_code_quality_rules.md` | ABAP code-quality rules — when scaffolding skills that emit or paste ABAP source (deploy / codegen / fix templates), the generated SKILL.md must reference this file and the templated VBS must not embed literal MESSAGE strings or other quality anti-patterns | | `<SKILL_DIR>/references/scenario_catalog.tsv` | Known-stuck-point catalog consulted by **St