sap-gui-diagnoselisted

Visual triage for SAP GUI scripts that hit unexpected screens (script hung, "control could not be found by id", or an unrecognised popup). Captures a BMP screenshot of every visible window in the active SAP GUI session via the Scripting API's HardCopy method, composes them into a single annotated PNG that mimics the operator's screen, and optionally chains to /sap-gui-object-details so the orchestrator gets both a visual and a structural view of the same state. The orchestrator (Claude) reads the resulting PNG with the Read tool and reasons about the next action. Pairs with /sap-gui-object-details: this skill is the visual view, that one is the structural view. Prerequisites: Active SAP GUI session (use /sap-login first).
sapdev-ai/sap-dev · ★ 4 · AI & Automation · score 77

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

# SAP GUI Diagnose Skill You capture a visual snapshot of the live SAP GUI session — every open window — and hand the resulting PNG to the orchestrator. Use it when another skill is stuck and the structural component dump from /sap-gui-object-details alone isn't enough to figure out what's on screen. Task: $ARGUMENTS --- ## Shared Resources | File | Token | Purpose | |---|---|---| | `<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md` | *(rule)* | Mandatory operating rules | | `<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md` | *(rule)* | 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 | | `<SKILL_DIR>/references/sap_gui_diagnose_capture.vbs` | `%%OUTPUT_DIR%%`, `%%MANIFEST%%` | HardCopy each window's BMP + emit TSV manifest | | `<SKILL_DIR>/references/sap_gui_diagnose_compose.ps1` | `%%MANIFEST%%`, `%%COMPOSITE_PNG%%`, `%%TOPMOST_PNG%%` | Stack BMPs in screen-space order to produce composite PNG + topmost PNG | --- ## When to Invoke (auto-trigger contract) Other skills SHOULD invoke `/sap-gui-diagnose` as the **first resort** — before falling back to manual scripting-recorder probes — when their VBS hits any of: 1. **Hard crash** — `findById` raises `The control could not be found by id`. 2. **Stuck progression** — the script has been waiting on a screen transition for noticeably