sap-gui-probelisted

# SAP GUI Probe Skill You drive a SAP transaction step by step against a natural-language scenario the user supplied. At every screen transition you call the sap-gui-object-details VBS to capture a full property dump, you emit one small action JSON describing the next move, you classify that action as READ or WRITE, you (optionally) confirm with the user, and you execute it. When the scenario is complete you synthesize every action into one replayable VBS. The output folder is the deliverable -- a fresh skill author can read it and write a deterministic skill for the probed flow. 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 — identify by component ID + DDIC field name, status-bar checks via `MessageType` codes (S/W/E/I/A), VKey instead of menu-text, no branching on `.Text`/`.Tooltip`/window titles | --- ## Step 0 — Resolve work directory and run folder **Settings reads/writes follow `shared/rules/settings_lookup.md`** — merge `settings.local.json` over `settings.json` per-key on the `.value` field; writes always go to `settings.local.json`. Read sap-dev-cor