Agent guidance
Narrows to what the released-API surface and the RAP object model force onto an agent's rules: claude-abap-skillsclaude-abap-skillsTwo Claude Code plugins of always-on Clean ABAP rules, templates and slash commands — deliberately not an MCP server, and explicit about routing each capability to the server that should answer it.independent, abap ships a dedicated plugin for allowed @AbapCatalog annotations, released APIs and clean core audits, rap-skillsrap-skillsRAP skills delivered branch-per-target, so the playbook you check out only references patterns valid for your deployment — managed on BTP, unmanaged with BAPI wrappers, and S/4HANA Cloud editions planned.independent, abap splits its RAP guidance itself by deployment target so a checked-out branch never states a pattern invalid for its target, and abap-skillsabap-skillsSeventeen agent skills for ABAP development in one repository: RAP, CDS view entities, ABAP SQL and AMDP, unit testing, authorisation, eventing, abapGit, ABAP Cloud and the clean core levels.independent, abap is the one place in the corpus that writes the clean core levels A to D down in full.
Showing artifacts, examples and content with confirmed ABAP Cloud applicability. View All ABAP
Overview
No core answer is documented.
Not covered: At the independent skill sets built for it specifically. claude-abap-skillsclaude-abap-skillsTwo Claude Code plugins of always-on Clean ABAP rules, templates and slash commands — deliberately not an MCP server, and explicit about routing each capability to the server that should answer it.independent, abap's abap-cloud-rap plugin carries ABAP Cloud and RAP rules read when a skill is invoked, among them the released-API surface, the allowed @AbapCatalog annotations and a clean core audit; rap-skillsrap-skillsRAP skills delivered branch-per-target, so the playbook you check out only references patterns valid for your deployment — managed on BTP, unmanaged with BAPI wrappers, and S/4HANA Cloud editions planned.independent, abap forks its RAP rules by deployment target because the available APIs and BDEF patterns differ between BTP ABAP Environment, S/4HANA Cloud and on-premise, and two of its five branches are available with the three S/4HANA ones marked planned; and abap-skillsabap-skillsSeventeen agent skills for ABAP development in one repository: RAP, CDS view entities, ABAP SQL and AMDP, unit testing, authorisation, eventing, abapGit, ABAP Cloud and the clean core levels.independent, abap writes SAP's clean core levels A to D down in full, including which authorisation object decides whether a developer may create Standard ABAP objects at all.
SuperClaude for SAPSuperClaude for SAPA Claude Code plugin that installs and wires its own ABAP MCP server, then puts a two-layer write guard between the agent and any system profile marked QA or production.independent, abap also states this flavor, but for its own MCP server and write governance across system profiles rather than for RAP or released-API rules.
Artifacts
Tasks
Get an agent to write ABAP that follows Clean ABAP
A developer wants the ABAP an agent writes to follow SAP's Clean ABAP conventions without the rules being pasted into the prompt each time, and wants what it wrote read back against them.
About how the conventions reach the agent and in what shape. The conventions themselves are Clean ABAP and belong to clean code; running a linter or ATC over the result mechanically is static analysis. Whether the code a reader gets is actually clean is not something any of these records establishes.
claude-abap-skillsThe clean-abap plugin carries rules its README calls universal, written into a CLAUDE.md each skill reads when it is invoked, with commands for a review and a refactor beside them. The repository states it is not an MCP server and ships no connector, so what it contributes to this outcome is the rules and the read, never the check against a system.
Remaining work: Install the plugin in Claude Code. A review it produces is a reasoned read of the code; what ATC or a linter says about the same code comes from somewhere else, and the repository's other plugin scopes itself to the ABAP Cloud development model rather than to classic code.
Get RAP patterns that match the target system
A developer building a RAP business object wants the patterns the agent follows to be the ones valid for the system it will be deployed to, rather than advice averaged across BTP ABAP Environment, S/4HANA Cloud and on-premise.
About what the agent is told before it writes, and how the guidance is scoped to one target. Activating the objects, running the ATC check and carrying the change in a transport are reached through an MCP server and belong to agent access to your code. Whether a generated business object works is not something any of these records establishes.
claude-abap-skillsRather than forking by target, the repository scopes a whole plugin: the abap-cloud-rap plugin carries ABAP Cloud and RAP rules read when a skill is invoked, and the targets it states are the BTP ABAP Environment and S/4HANA under the ABAP Cloud development model. The scoping happens once, when the plugin is chosen, rather than per session.
Remaining work: Install the plugin, and know that it is the ABAP Cloud model being followed: a classic codebase is not what these rules are written against. The repository ships no connector, so activation and ATC come from a server you connect.
rap-skillsThe distribution is the contribution. Its README states that the syntax, the available APIs, the BDEF patterns and the tooling constraints differ between BTP Steampunk, S/4HANA Cloud and on-premise, and the repository answers that by putting each target on its own branch, so the checked-out playbook only references patterns valid for that target. Five skills sit on each branch, from scaffolding a managed business object to diagnosing activation errors and runtime dumps.
Conditions: The branch matching the deployment target is the one checked out, since the guidance is correct for that target and not for the others Only the two BTP ABAP Environment branches are available; the S/4HANA Cloud public, private and on-premise branches are marked planned A VSP MCP server is configured, which the README names as the bridge between the agent and the SAP system
Remaining work: Check out the branch that matches the target, which is the step the whole idea rests on, and connect a server for anything that touches the system. Two of the five branches are available today: BTP managed and BTP unmanaged with BAPI wrappers.
abap-skillsThe repository ships a rap skill beside its sixteen others, and its abap-cloud skill is where the repository states which development model it answers against. What the rap skill itself says about deployment targets was not read in this pass, so whether it scopes its patterns is not established.
Remaining work: Read skills/rap/SKILL.md and record whether it states a target. Until then the entry is listed here as unassessed for this outcome rather than as an option that does or does not scope.
Work on ABAP with an agent and no system connection
A developer wants to review, write or test ABAP with an agent on a machine that has no connection to an SAP system — a serialised repository checked out, or source pasted into the session, and nothing else.
About what an agent has to work with when nothing is connected: the packaged knowledge it is handed, and the tooling that does on the local machine what a system would otherwise do. What a connected agent can read, change, activate or run in a live system is agent access to your code, and an entry that offers both is assessed here for its off-system half only. This record does not say that working without a system is equivalent to working with one, and the contributions state where the difference falls.
claude-abap-skillsThe repository ships no connector at all and states so plainly, and it names what happens when no server is connected: all five skills still work on source a person pastes in. So the rules and the review survive the loss of reach, and what does not survive is anything that has to read or change the system.
Conditions: The source is pasted into the session, since there is no connector and no server is connected
Remaining work: Paste the source. Nothing here can read what exists, run ATC or activate anything, and the repository's own routing table assumes a server for exactly those operations.
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