sap-gui-probelisted

Drive a SAP transaction step by step against a natural-language scenario, dumping each screen's full property tree via /sap-gui-inspect and emitting a synthesized recording-style VBS at the end. Designed as a skill-authoring aid: probe SE37 before writing a new /sap-se37 flow. Captures more than the SAP recorder -- not just findById paths and actions, but also Changeable, Tooltip, IconName, popup transitions, and the program/transaction/screen identity at every step. Capture modes: * drive (default) -- Claude drives the transaction live (Steps 0-4). * --record [<vbs>] -- fallback when Claude can't reliably drive the flow (unfamiliar or write-heavy transaction, or when a real operator's exact clicks are wanted as ground truth): guides you to record it with SAP GUI's built-in Script Recording and Playback, then parses the saved VBS into the same findById/action map. Replaces the former /sap-gui-record skill; parsing an already-saved recording needs no live session. Two safety modes (drive only): * mode=confirm
sapdev-ai/sap-dev · ★ 7 · Web & Frontend · score 73

Install: claude install-skill sapdev-ai/sap-dev

# 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-inspect 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/safety_policy.md` | **Rule 0 (highest priority)** — environment guard; enforced by the drive-mode write classifier via `sap_safety_gate.ps1` | | `<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md` | Mandatory operating rules | | `<SAP_DEV_CORE_SHARED_DIR>/rules/settings_lookup.md` | Settings model — merge per-key on `.value` (env var → `settings.local.json` → `userconfig.json` → `settings.json`); non-per-connection writes go to `userconfig.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 | | `<SAP_DEV_CORE_SHARED_DIR>/rules/sap_gui_scripting_reference.md`