writing-skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
sap-cpi-flowpilotAutonomous SAP Cloud Integration (CPI) co-pilot and lifecycle engine. Use when triaging CPI message failures (MPL), packaging or testing iFlow bundles with FlowMate toolkit, managing multi-tenant CPI landscapes, validating Groovy/XSLT mappings, or orchestrating automated iflow deployment and rollback with fail-closed approval governance.
Independent GitHub snapshot · Automated classification · Original documentation governs
name: sap-cpi-flowpilot description: >- Autonomous SAP Cloud Integration (CPI) co-pilot and lifecycle engine. Use when triaging CPI message failures (MPL), packaging or testing iFlow bundles with FlowMate toolkit, managing multi-tenant CPI landscapes, validating Groovy/XSLT mappings, or orchestrating automated iflow deployment and rollback with fail-closed approval governance. trigger:
Orchestration, automated diagnostics, and testing toolkit for SAP Cloud Integration (CPI / SAP Integration Suite).
approval_broker.py.sap-cpi-mcp (sap.cpi.artifact.*, sap.cpi.message.*, sap.cpi.bundle.package)integration-suite-ui-mcp (Playwright bridge via user session when OAuth API access is blocked)sap.cpi.multitenant.manage[Failed Message MPL]
│
▼
1. Query Message Log (sap.cpi.message.read)
│
▼
2. Fetch Trace / Attachment (sap.cpi.trace.read)
│
▼
3. Classify Root Cause (Groovy error / Mapping failure / Receiver Timeout / Auth error)
│
▼
4. Generate Fix Plan (Patch Groovy script / Adjust Content Modifier / Re-trigger payload)
│
▼
5. Propose & Commit (approval_broker.py plan -> commit)
# Triage failed messages in CPI
python scripts/sap_harness.py run --agent cpi --task "triage failed messages in CPI tenant"
# Validate and package iFlow using local toolkit
python scripts/cpi_iflow_packager.py validate --input src/my-iflow.zip