sap-gui-diagnose

Generates annotated PNG summaries of SAP GUI windows from BMP captures.

7|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/sapdev-ai/sap-dev --skill sap-gui-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sap-gui-diagnose
Source: https://github.com/sapdev-ai/sap-dev/tree/main/plugins/sap-dev-core/skills/sap-gui-diagnose
Command: npx skills add https://github.com/sapdev-ai/sap-dev --skill sap-gui-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Visual triage for SAP GUI scripts that hit unexpected screens (script hung, "control could not be found by id", or an unrecognised popup). It captures a BMP screenshot of every visible SAP GUI window 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. Prerequisites: Active SAP GUI session (use /sap-login first).

Core Features & Use Cases

  • Visual capture: capture every open SAP GUI window as a BMP.
  • Composite view: assemble the BMPs into an annotated PNG and provide a topmost PNG.
  • Structural pairing: optionally invoke /sap-gui-object-details for deeper context.
  • Safe orchestration: integrates with the Read tool for downstream reasoning and decisions.

Quick Start

Capture the current SAP GUI session visuals in composite mode to generate a visual summary for the orchestrator.

Frequently Asked Questions about sap-gui-diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose an SAP GUI script that is hung on an unexpected popup?

To diagnose SAP GUI hangs or unexpected popups, capture BMP screenshots of all open windows via the Scripting API's HardCopy method and assemble them into an annotated composite PNG for visual triage and debugging.

Why does my SAP GUI automation fail with the error control could not be found by id?

SAP GUI automation fails with control ID errors due to component-ID drift or unexpected screen changes. Generate a visual summary of all open SAP GUI windows to identify the active screen state and pinpoint the missing component.

How to capture a visual summary of all open SAP GUI windows for troubleshooting?

Capture a visual summary of SAP GUI windows by using the Scripting API HardCopy method to grab BMPs of every visible session, then compose them into a single annotated PNG mimicking the operator's screen for orchestrator reasoning.

Can I get structural context alongside visual screenshots of my SAP GUI session?

Yes, you can get structural context alongside visual screenshots by optionally chaining the composite PNG capture to a structural object dump, providing both visual and component-level views of the same SAP GUI state.

Do I need an active SAP GUI session to run visual diagnostic captures?

Yes, an active SAP GUI session is required to run visual diagnostic captures. You must establish an active session beforehand so the Scripting API can access open windows and execute the HardCopy method for screenshot generation.

What is the best way to troubleshoot unexpected SAP GUI screens during automated scripting?

The best way to troubleshoot unexpected SAP GUI screens is capturing composite annotated PNGs of all open windows. This visual basis allows the orchestrator to read the screen state and reason about the next corrective action safely.