How do I install the Sap Incident Resolution skill?

Run npx skillmds@latest add williamcorrea23/sap-incident-resolution in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sap Incident Resolution safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sap Incident Resolution?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sap Incident Resolution free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sap Incident Resolution?

williamcorrea23 (@williamcorrea23) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sap Incident Resolution by williamcorrea23

Name: Sap Incident Resolution
Author: williamcorrea23

Sap Incident Resolution

SAP intelligent incident resolution and self-healing engine. Use when investigating system dumps (ST22), analyzing lock entries (SM12), triaging failed background jobs (SM37), diagnosing update errors (SM13), resolving CPI/RFC communication breakdowns, or triggering automated self-healing remediation plans under fail-closed approval gates.

File contents

SAP Intelligent Incident Resolution & Self-Healing Agent

Automated triage, root-cause analysis, and remediative self-healing for SAP landscapes (ABAP, CPI, S/4HANA, NetWeaver).

Incident Domains Covered

Domain	Detection Tool	Diagnostic Action	Remediation / Self-Healing
ABAP Short Dumps	ST22 / SNAP table	Parse error class, line number, termination point	Generate patch via ADT/ZROUTER or suggest OSS note
Lock Collisions	SM12	Inspect lock arguments, user, duration	Suggest enqueue dequeue with safety checks
CPI Message Failures	MPL / Trace	Error step isolation, payload inspection	Automated re-trigger, error subprocess routing
Background Jobs	SM37 / TBTCO	Job log analysis, step variant verification	Reschedule with corrected parameters
RFC / Communication	SM59 / SM21	Ping RFC destination, check gateway buffer	Reconnect destination, verify SNC / credentials

Autonomous Execution Rules

Diagnosis is Always Read-Only: Diagnostics through sap.incident.resolution.diagnose or arc-1 / ST22_SCAN never modify system state.
Remediation Requires Explicit Approval: Any write, cancellation, or restart must go through approval_broker.py plan-and-commit.
Audit Trail: Every incident step, diagnostic hypothesis, and resolution outcome is logged in MEMORY.md.

Harness Integration

Run automated incident triage directly through the harness:

# Run incident triage on latest dumps
python scripts/sap_harness.py run --agent sre --task "diagnose recent ST22 dumps and lock conflicts"

# Evaluate incident resolution capability in sandbox
python scripts/sap_harness.py eval --scenario incident_triage

---name: sap-incident-resolutiondescription: SAP intelligent incident resolution and self-healing engine. Use when investigating system dumps (ST22), analyzing lock entries (SM12), triaging failed background jobs (SM37), diagnosing update errors (SM13), resolving CPI/RFC communication breakdowns, or triggering automated self-healing remediation plans under fail-closed approval gates.---# SAP Intelligent Incident Resolution & Self-Healing AgentAutomated triage, root-cause analysis, and remediative self-healing for SAP landscapes (ABAP, CPI, S/4HANA, NetWeaver).## Incident Domains Covered| Domain | Detection Tool | Diagnostic Action | Remediation / Self-Healing ||---|---|---|---|| **ABAP Short Dumps** | ST22 / SNAP table | Parse error class, line number, termination point | Generate patch via ADT/ZROUTER or suggest OSS note || **Lock Collisions** | SM12 | Inspect lock arguments, user, duration | Suggest enqueue dequeue with safety checks || **CPI Message Failures** | MPL / Trace | Error step isolation, payload inspection | Automated re-trigger, error subprocess routing || **Background Jobs** | SM37 / TBTCO | Job log analysis, step variant verification | Reschedule with corrected parameters || **RFC / Communication** | SM59 / SM21 | Ping RFC destination, check gateway buffer | Reconnect destination, verify SNC / credentials |## Autonomous Execution Rules1. **Diagnosis is Always Read-Only**: Diagnostics through `sap.incident.resolution.diagnose` or `arc-1` / `ST22_SCAN` never modify system state.2. **Remediation Requires Explicit Approval**: Any write, cancellation, or restart must go through `approval_broker.py` plan-and-commit.3. **Audit Trail**: Every incident step, diagnostic hypothesis, and resolution outcome is logged in `MEMORY.md`.## Harness IntegrationRun automated incident triage directly through the harness:```bash# Run incident triage on latest dumpspython scripts/sap_harness.py run --agent sre --task "diagnose recent ST22 dumps and lock conflicts"# Evaluate incident resolution capability in sandboxpython scripts/sap_harness.py eval --scenario incident_triage```

Frequently asked questions