sap-gui-object-detailslisted

# SAP GUI Object Details Skill You inspect the currently active SAP GUI screen and dump the component tree, menu bar, all components of a chosen type, or the full property set of a single component identified by its `findById` path. 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/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 **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`. Resolve sap-dev-core paths: 2 levels up from `<SKILL_DIR>` to the plugin root, then `settings.json` and (if present) `settings.local.json`. Read `work_dir`. | Setting | Default if blank | |---|---| | `work_dir` | `C:\sap_dev_work` | Set `{WORK_TEMP}` = `{work_dir}\temp`. Ensure it exists: ```bash cmd /c if not exist "{WORK_TEMP}" mkdir "{WORK_TEMP}" ``` --- ## Step 0.5 — Start Logging Start a structured log run. The helper persists `run_id` in a state file (`{WORK_TEMP}\sap_gui_object_details_run.json`) so subsequent steps and the final log-end call append to the same run