Agent guidance
Service by service. An entry here carries what an agent needs for one BTP service or one surface, from the AI Core skillsaicore-skillsFour agent skills for SAP AI Core, published as a plugin inside SAP's AI Skills Library: admin resources, the deployment lifecycle, the foundation models in the Generative AI Hub, and the Context Registry behind tabular prediction.sap official, btp and their deployment lifecycle to the Automation Pilot skillsSAP/automation-pilot-agent-skillsEight skills for writing, reviewing and operating SAP Automation Pilot content — command generation, catalogue exploration, code review, the content and executions APIs, debugging, schedules, and generating an MCP server from a command.sap official, btp and their Commands, the Application Frontend migrationSAP-samples/html5-applications-migration-skills-for-sap-btpA Claude Code plugin with migrate, validate and cleanup skills that move an HTML5 app from SAP Neo, html5-apps-repo or a standalone approuter to the SAP BTP Application Frontend (appFront) service.sap official, btp and the Mobile Development Kit's metadatasap-mdk-appsAn agent skill for Mobile Development Kit projects: the project layout, the metadata syntax, and the rules that prevent the failures those two produce on iOS, Android and the web.independent, btp, and much of it is operational: what to run, against which account, through which command line. The solution diagram is the exception, where several skill sets and an MCP serverARC-DRAWAn MCP server that draws BTP solution diagrams onto a live draw.io canvas, with 111 SAP BTP icons as native shapes and SAP's diagram guidelines handed to the client as drawing rules.independent, btp carry the same SAP visual languageSAP BTP Solution Diagram GuidelinesSAP's visual language for BTP solution diagrams, in line with the SAP Fiori Horizon principles and colour palette, with editable templates for draw.io and PowerPoint.sap official, btp and differ mainly in how its rules reach the agent.
Overview
SAP publishes a skill set per service rather than one for the platform: AI Coreaicore-skillsFour agent skills for SAP AI Core, published as a plugin inside SAP's AI Skills Library: admin resources, the deployment lifecycle, the foundation models in the Generative AI Hub, and the Context Registry behind tabular prediction.sap official, btp, Automation PilotSAP/automation-pilot-agent-skillsEight skills for writing, reviewing and operating SAP Automation Pilot content — command generation, catalogue exploration, code review, the content and executions APIs, debugging, schedules, and generating an MCP server from a command.sap official, btp, LeanIXSAP/leanix-ai-pluginsOne Claude Code plugin, sap-leanix, bundling two skills that build and debug LeanIX automation scripts and create and manage calculations, both working through the LeanIX MCP server.sap official, btp, Joule over A2ASAP-samples/joule-a2a-agent-toolkitFour skills for building an agent that talks to SAP Joule over A2A and getting it onto Cloud Foundry — the agent itself, and the three CLIs the deployment goes through.sap official, btp, the Application Frontend migrationSAP-samples/html5-applications-migration-skills-for-sap-btpA Claude Code plugin with migrate, validate and cleanup skills that move an HTML5 app from SAP Neo, html5-apps-repo or a standalone approuter to the SAP BTP Application Frontend (appFront) service.sap official, btp, Fiori for iOSsap-fiori-iosAn agent skill SAP publishes for SAP Fiori for iOS: it maps a node of the Fiori iOS UI Kit in Figma onto SwiftUI code, and answers which Fiori component a Figma variant becomes.sap official, btp and the developer tutorial APIsap-tutorials-contentAn agent skill that maps the public developers.sap.com content API: the catalogue, the navigation, a tutorial's HTML or JSON, and full-text search, all anonymous and read-only.sap official, btp each have their own, written in the open Agent Skills format and installed through the same third-party skills command line the rest of the ecosystem uses. Beside them sap-devsSAP-samples/sap-devs-cliA CLI that injects current SAP developer knowledge packs into an AI coding tool's context and wires up SAP's own MCP servers for it, shipped as a single binary through Homebrew, Scoop or GitHub Releases.sap official, btp is a command line that writes SAP context into whichever AI tool is configured, with a sync command for keeping that content current.
Not covered: At the service each set is about. None of them carries the platform as a whole, and SAP's own registry at skills.cloud.sap keeps the code in the publisher's repository, so a skill listed there is published by whoever owns that repository and not by SAP.
Both halves are present in the same shape. SAP's sets are written as Agent Skills and install through the same third-party skills command line the independent ones use, and SAP's registry indexes other people's repositories rather than hosting their code. Which half was first behind this door is not established, so the pattern is left unassessed rather than read off the dates the entries happened to enter the atlas.
The platform-wide and the cross-service questions. Independent skill sets carry SAP's own solution-diagram visual language and differ in how its rules reach the agent; broad collections cover BTP beside the other doors; and Datasphere, the Mobile Development Kit and the Integration Suite's Pipeline Concept have guidance behind this door.
Artifacts
Tasks
Change a BTP service from an agent session
A developer working with an agent wants the change made in their own BTP account or service, a Command deployed, an agent pushed, a deployment created, rather than a command to copy out and run themselves.
About whether a skill set carries the reach as well as the knowledge, and what it asks for before it does. What an agent can read and change in the project's own source is agent access to your code. Entitlements, logins and authorisations stay the developer's, and nothing here was run.
aicore-skillsIts lifecycle skill manages AI Core scenarios, executables, configurations and deployments by running the skill's own Python scripts, and states that a script which deletes or mutates state requires an explicit --confirm.
Conditions: An SAP AI Core instance with credentials configured, which the README states Python with uv and the sap-ai-sdk-core package, which the README lists; the tabular skill states Python 3.11 or later and the BTP command line for registering HDL access A mutating or deleting script is passed --confirm, which the skill states explicitly
Remaining work: Configure the instance credentials and the Python toolchain, and decide what may be mutated: the --confirm flag is the skill's own gate and the agent passes it.
SAP-samples/html5-applications-migration-skills-for-sap-btpThe migration is local: the README states that no MCP servers or network access are required and that the plugin operates entirely on local files. Its cleanup skill undeploys a deployed appFront app from Cloud Foundry, optionally deleting service instances and keys, and removes the local output folder.
Conditions: The CF command line logged in and targeted at an org and space before deploying, which the requirements state The MultiApps Build Tool for building the MTA and the CF multiapps plugin for cf deploy, both named in the requirements A subaccount with the Application Frontend service entitlement and the Cloud Foundry environment enabled
Remaining work: Build and deploy with the named tools; the appFront command line is listed as optional and is what fetches the runtime URL after a deployment.
SAP-samples/joule-a2a-agent-toolkitIts four skills generate the btp, cf and Joule commands rather than running them. Beside them the Quick Start uses a user-invoked command, deploy-agent, on the scaffolded agent, and the Getting Started step is to start Claude Code with the plugin and then log in to Cloud Foundry and Joule.
Conditions: cf login and joule login done before the toolkit is used, which the Getting Started step states A BTP Cloud Foundry account with the entitlements the generated commands act on
Remaining work: Run the two logins, then read what the generated commands would do against the account they are pointed at: what the skills hand over is text until something runs it.
SAP/automation-pilot-agent-skillsThe skill set covers deploying, updating, listing and deleting Commands, Inputs and MCP servers through the API, and triggering a Command, watching its status and reading its logs.
Conditions: An SAP Automation Pilot tenant with API credentials, which the prerequisites state The four AUTOPI_ variables written into a .env file and sourced before the API skills are used curl and jq on the machine, which the prerequisites list for the API calls and the JSON parsing Claude Code, which the prerequisites name as required to use the skills
Remaining work: Create the tenant's technical user, put the credentials in the environment and verify the connection with the listing call the README gives. The repository is opened in Claude Code rather than installed as a package.
sap-cloud-integration-pipeline-assistantIts scope section says what it answers on and what it leaves out: implementation assistance, Partner Directory guidance, XSLT and Groovy examples, architecture decisions and troubleshooting, and not generating or deploying complete iFlow artifacts.
Remaining work: Build and ship the integration flows in the tenant by hand, or with something else.
SAP/leanix-ai-pluginsIts setup section describes installing the plugin and the LeanIX MCP server connecting on first use with an OAuth sign-in, and no sentence read on 2026-10-15 states that the skills themselves deploy or run an automation in a LeanIX instance. Whether the reach belongs to the skills or only to the server is the open question.
Remaining work: Read the two skills' own SKILL.md files, which this pass did not read, and the MCP server's documented tool surface.
Hand an agent SAP's BTP diagram rules
Someone asks an agent for a BTP solution diagram and wants it drawn in SAP's own visual language without the rules being typed into the prompt.
About how the rules reach the agent. What the resulting file is, and what checks it afterwards, is architecture diagrams and is assessed there. Whether the architecture the diagram shows is a sound one is a different question that nothing here answers.
ARC-DRAWThe guideline reaches the MCP client as a drawing constitution the moment it connects, rather than being loaded as a skill the agent decides to read. Two tools, get-sap-examples and get-sap-guideline, let the agent ask for a canonical pattern or a rule by topic afterwards.
Remaining work: Install from source and keep a draw.io canvas open and connected, since that is what the drawing tools work against. Nothing here checks the result: the maintainer keeps a diagram linter on the roadmap.
btp-solution-diagram-generatorA core SKILL.md carries the design system and the L0 to L3 level model, six reference files cover the Horizon colours and styles, the area and nesting rules, the connector semantics, the icon catalogue, the mxGraph XML schema and the levels, and the official SAP shape library is bundled with the statement that no network is needed.
Remaining work: Add the marketplace and install the plugin in Claude Code or Cowork. The rules then load with the skill, so what the agent follows is the copy in the installed version.
drawio-btp-diagram-skillsA table in SKILL.md says which document is read when: the Conventions section at the Mermaid stage, references/layout.md and references/elements.md for the draw.io XML, and references/guidelines.md when a style decision is in doubt. That file is the maintainer's English summary of SAP's guidelines and is named the source of truth above the implementation layer. The review skill has independent triggers, so it runs on a finished XML or a pasted screenshot without being asked for.
Remaining work: Fork the repository, clone it, symlink the two skill folders into ~/.claude/skills and restart Claude Code. The workflow is written for a person and Claude together, so the steps it assigns to the person stay theirs: pasting the XML into draw.io, and placing the Generic Icons.
drawio-skill-sapWritten for an Agent Skills location a Copilot environment recognises, and it states the icon rule as a prohibition: every persona and every SAP system, service or product has to render as a real SAP icon or product logo.
Remaining work: Place the skill folder where the Copilot environment reads it, or install it through the skills command line. The vision self-check in its routine is skipped where no vision-capable model is available.
sap-architectureBundles the icons, the reference templates and the Python scripts locally and states that there are no cloud calls. The skill is plain Markdown plus dependency-free scripts, and the README names the instruction file to point at it for Codex, GitHub Copilot, Cursor and the tools that read AGENTS.md.
Remaining work: On Claude the skill auto-loads; on the other tools the README says the instruction file wires it in per project, and the scripts need shell access and Python 3.8 or later.
Keep the SAP knowledge an agent follows current
A developer wants what their agent is told about SAP to come from what SAP documents now, rather than from what the model learnt or what a skill file froze when it was written.
About where the knowledge comes from at the moment the agent reads it. Whether that knowledge is right, and whether the agent then produces correct work, are separate questions; checking what an agent produces is agent evals.
SAP-samples/sap-devs-cliA command line rather than a skill. One command injects SAP context into the AI tools that are configured, and a second is documented as the one that keeps the content current.
Remaining work: Run the sync. The README read on 2026-10-15 names no schedule and no list of supported assistants, so when the content is refreshed and which tool receives it are the developer's to establish.
sap-tutorials-contentThe skill carries the paths of the public developers.sap.com content API rather than the tutorials themselves, so what the agent gets is whatever the catalogue serves when it calls. It states that everything there is anonymous and read-only, dates its own check of the endpoints, and tells the agent to honour the ETag and Cache-Control headers on what it calls a shared public service.
Remaining work: The agent makes the calls, and what the tutorials say is SAP's. The skill dates its check of the endpoints rather than claiming they are watched, so a path that moves is noticed when a call fails.
sap-architectureStands here for the bundled sets behind this door. It states that every icon, template and script is bundled and runs locally with no cloud calls, which says what the agent reads is the copy in the installed version. Whether that copy tracks the current SAP guideline is not stated: the README read on 2026-10-15 names no guideline revision and no refresh mechanism beyond updating the plugin.
Remaining work: Update the installed plugin and compare its bundled templates against the current guideline by hand, since nothing in the package dates them.
Content
Details
Coverage
Designs that place it
Comparison properties
These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.
For your agent
- Ref
capability:agent-guidance- JSON
- /capabilities/agent-guidance.json
- MCP
- Connecting an agent