plugins marketplace
← All plugins

sap-api-policy

v2.4.1

Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/"confidential" API status, "Documented Use", whether a third-party tool / iPaaS / middleware / RPA bot / AI agent / MCP server may call SAP APIs, agentic or generative-AI access to SAP, bulk data extraction or replication into a lake/warehouse, custom Z/Y OData or RFC/BAPI wrappers and Clean Core, ADT/developer-tooling boundaries, ODP-RFC and other "not permitted" interfaces, partner Integration Certification, or RISE integration remediation. Trigger even when the policy is not named, e.g. "are we allowed to…", "is it compliant to…", "can we connect X to SAP…", "will this break under the new API policy". Produces a sourced technical assessment with a confidence level — explicitly NOT legal advice and NOT a final SAP compliance decision.

CodexClaude Code1 skill

by Eduard JiglauGPL-3.0404updated 1 day ago

Source

git clone https://github.com/secondsky/sap-skills

Clone the source, then follow the repository's marketplace instructions for your runtime. The plugin root is plugins/sap-api-policy/ inside the repository.

Layout

plugins/sap-api-policy/
├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
└── skills/sap-api-policy/SKILL.md

Skills1

sap-api-policyskills/sap-api-policy/SKILL.md

Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/"confidential" API status, "Documented Use", whether a third-party tool / iPaaS / middleware / RPA bot / AI agent / MCP server may call SAP APIs, agentic or generative-AI access to SAP, bulk data extraction or replication into a lake/warehouse, custom Z/Y OData or RFC/BAPI wrappers and Clean Core, ADT/developer-tooling boundaries, ODP-RFC and other "not permitted" interfaces, partner Integration Certification, or RISE integration remediation. Trigger even when the policy is not named, e.g. "are we allowed to…", "is it compliant to…", "can we connect X to SAP…", "will this break under the new API policy". Produces a sourced technical assessment with a confidence level — explicitly NOT legal advice and NOT a final SAP compliance decision.

Manifests2

plugins/sap-api-policy/.codex-plugin/plugin.json
{
  "name": "sap-api-policy",
  "version": "2.4.1",
  "description": "Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/\"confidential\" API status, \"Documented Use\", whether a third-party tool / iPaaS / middleware / RPA bot / AI agent / MCP server may call SAP APIs, agentic or generative-AI access to SAP, bulk data extraction or replication into a lake/warehouse, custom Z/Y OData or RFC/BAPI wrappers and Clean Core, ADT/developer-tooling boundaries, ODP-RFC and other \"not permitted\" interfaces, partner Integration Certification, or RISE integration remediation. Trigger even when the policy is not named, e.g. \"are we allowed to…\", \"is it compliant to…\", \"can we connect X to SAP…\", \"will this break under the new API policy\". Produces a sourced technical assessment with a confidence level — explicitly NOT legal advice and NOT a final SAP compliance decision.",
  "author": {
    "name": "Eduard Jiglau",
    "email": "hello@sap-ai-skills.com",
    "url": "https://sap-ai-skills.com"
  },
  "homepage": "https://sap-ai-skills.com",
  "repository": "https://github.com/secondsky/sap-skills",
  "license": "GPL-3.0",
  "keywords": [
    "api",
    "automation",
    "cli",
    "development",
    "odata",
    "policy",
    "productivity",
    "sap",
    "sap-api-policy",
    "tools"
  ],
  "skills": "./skills/",
  "interface": {
    "displayName": "SAP API Policy",
    "shortDescription": "Evidence-based assessment of whether an SAP API/interface usa...",
    "longDescription": "Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/\"confidential\" API status, \"Documented Use\", whether a third-party tool / iPaaS / middleware / RPA bot / AI agent / MCP server may call SAP APIs, agentic or generative-AI access to SAP, bulk data extraction or replication into a lake/warehouse, custom Z/Y OData or RFC/BAPI wrappers and Clean Core, ADT/developer-tooling boundaries, ODP-RFC and other \"not permitted\" interfaces, partner Integration Certification, or RISE integration remediation. Trigger even when the policy is not named, e.g. \"are we allowed to…\", \"is it compliant to…\", \"can we connect X to SAP…\", \"will this break under the new API policy\". Produces a sourced technical assessment with a confidence level — explicitly NOT legal advice and NOT a final SAP compliance decision.",
    "developerName": "Eduard Jiglau",
    "category": "Tooling",
    "capabilities": [
      "Interactive",
      "Read",
      "Write"
    ],
    "defaultPrompt": [
      "Use SAP API Policy for SAP guidance."
    ],
    "websiteURL": "https://sap-ai-skills.com"
  }
}
plugins/sap-api-policy/.claude-plugin/plugin.json
{
  "name": "sap-api-policy",
  "description": "Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/\"confidential\" API status, \"Documented Use\", whether a third-party tool / iPaaS / middleware / RPA bot / AI agent / MCP server may call SAP APIs, agentic or generative-AI access to SAP, bulk data extraction or replication into a lake/warehouse, custom Z/Y OData or RFC/BAPI wrappers and Clean Core, ADT/developer-tooling boundaries, ODP-RFC and other \"not permitted\" interfaces, partner Integration Certification, or RISE integration remediation. Trigger even when the policy is not named, e.g. \"are we allowed to…\", \"is it compliant to…\", \"can we connect X to SAP…\", \"will this break under the new API policy\". Produces a sourced technical assessment with a confidence level — explicitly NOT legal advice and NOT a final SAP compliance decision.",
  "version": "2.4.1",
  "author": {
    "name": "Eduard Jiglau",
    "email": "hello@sap-ai-skills.com",
    "url": "https://sap-ai-skills.com"
  },
  "license": "GPL-3.0",
  "homepage": "https://sap-ai-skills.com",
  "repository": "https://github.com/secondsky/sap-skills",
  "keywords": [
    "api",
    "automation",
    "cli",
    "development",
    "odata",
    "policy",
    "productivity",
    "sap",
    "sap-api-policy",
    "tools"
  ],
  "category": "tooling"
}