skills.rest
sapdev-ai
sapdev-aiOFFICIAL
Explore all skills by this author →
GitHub

sap-diagnose

Consolidate evidence from read-only SAP readers and rank root-cause hypotheses.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Incident triage for SAP incidents by quickly gathering evidence from multiple read-only readers and surfacing prioritized root-cause hypotheses.

Core Features & Use Cases

  • Collects evidence from read-only SAP readers (ST22, SM13, SM12, SLG1, SM37) and correlates it into incident clusters.
  • Produces ranked root-cause hypotheses with recommended next actions, while never mutating SAP data.
  • Supports a gated fix hand-off to /sap-fix-incident for write-capable remediation, ensuring safety rails and approvals.

Quick Start

Provide an incident anchor and optional filters, then run sap-diagnose to obtain ranked hypotheses.

Frequently Asked Questions about sap-diagnose

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

FAQPage Schema
How do I automate SAP incident triage across multiple read-only readers?▼

SAP incident triage is automated by consolidating evidence from read-only readers like ST22, SM13, SM12, SLG1, and SM37 into correlated incident clusters. The process ranks root-cause hypotheses and recommends next actions without mutating live SAP systems.

What is the best way to correlate SAP evidence from ST22 and SLG1 for root-cause analysis?▼

Correlating SAP evidence from ST22, SLG1, and other readers requires server-time anchored windowing to align logs into incident clusters. This approach generates ranked root-cause hypotheses by matching timestamps and contextual data across multiple diagnostic sources.

Do I need an RFC connection and saved SAP login profile to diagnose incidents?▼

Diagnosing SAP incidents requires a saved SAP login profile, an active RFC connection, and server-time anchored windowing. These prerequisites ensure robust evidence correlation and secure read-only access to system diagnostic readers.

Can I apply fixes directly while triaging SAP incidents with read-only readers?▼

Read-only SAP incident triage never mutates live system data. Any required write actions for remediation are handed off to a gated fix skill, ensuring safety rails and approvals are enforced before applying changes to the SAP environment.

Why does SAP incident triage require server-time anchored windowing?▼

Server-time anchored windowing is required to robustly correlate evidence across SAP readers like SM37 and SM13. It synchronizes log entries by the server clock, ensuring accurate incident clustering and reliable root-cause hypothesis ranking.

Related Skills

Explore More Software Engineering Skills→
sapdev-aisapdev-ai
7

sap-sm37

Retrieve SAP SM37 background-job data via RFC and emit diagnostic evidence per job.

Official
Intermediate
RayOfSteel-DHBWRayOfSteel-DHBW

diagnose-issues

Ugh. Yet another repetitive task, automated perfectly.

Community
Advanced
sapdev-aisapdev-ai
7

sap-sm13

Read VBHDR and join VBERROR over VBKEY to surface SM13 update-task failures.

Official
Intermediate
openeuler-mirroropeneuler-mirror
3

grub-ibmc-diagnosis

Analyze iBMC out-of-band logs to diagnose server boot failures.

Official
Advanced