Agent 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 JiglauLicense: GPL-3.0452 GitHub starsUpdated 2 days ago

Directory evidence

Runtimes
Codex and Claude Code
Parsed components
1 skill or MCP entry
Source updated
Sep 21, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology

Install sap-api-policy for Codex and Claude Code

Installs for the current user
codex plugin marketplace add secondsky/sap-skills
codex plugin marketplace upgrade sap-skills
codex plugin add sap-api-policy@sap-skills

Paste and run these commands in a terminal with Codex. They add and refresh the sap-skills catalog, then install this plugin.

Compatibility: the page URL and API slug “sap-api-policy” remain stable.

  • Codex: sap-api-policy@agent-plugin-marketplacesap-api-policy@sap-skills

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/secondsky/sap-skills

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/sap-api-policy/.

Plugin files

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

Included 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.

Plugin 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": "[email protected]",
    "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": "[email protected]",
    "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"
}

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[sap-api-policy on Agent Plugins Marketplace](https://pluginsmp.com/plugins/sap-api-policy)