{"ref":"capability:agent-guidance","page":"/capabilities/agent-guidance","json":"/capabilities/agent-guidance.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"agent-guidance","name":"Agent guidance","domain":"ai-and-agents","ecosystems":["cap","ui5","btp","abap","commerce"],"universal":true,"description":"Packaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.","short":"Packaged knowledge that teaches a coding agent a framework","core_coverage":{"state":"core-and-community","assessed_at":"2026-09-07","what_core_does":"SAP publishes [capire/skills](artifact:capire-skills) — four curated skills for CAP in the open skill standard, Apache-2.0 under SAP's OSPO, installable through the skills CLI, a Claude Code plugin marketplace, a Copilot marketplace source or a plain symlink. Two of the four ship evals beside them.","where_it_stops":"It stops at four skills — cap-developer, cap-add-remote-service, cap-upgrade and cap-trivia — against a corpus of dozens of capabilities. Getting started, consuming a remote service and upgrading are covered; for anything else an agent is still looking things up rather than following a rule it was handed.","sources":[{"url":"https://github.com/capire/skills","title":"capire/skills — README","checked":"2026-09-07","quote":"Curated set of skills helping AI coding agents build and maintain CAP applications."},{"url":"https://github.com/capire/skills/tree/main/skills","title":"capire/skills — the four skill directories","checked":"2026-09-07"},{"url":"https://github.com/capire/skills/blob/main/REUSE.toml","title":"capire/skills — REUSE.toml, SPDX-PackageSupplier ospo@sap.com","checked":"2026-09-07","quote":"2026 SAP SE or an SAP affiliate company and capire/skills contributors"}],"relationship":"core-adopted-it"},"gap":{"open_since":"2026-09-01","note":"Narrowed rather than closed. The original gap was that nothing SAP-published carried rules an agent should follow without asking; [capire/skills](artifact:capire-skills) now does. What stays open is breadth — four skills against dozens of capabilities — and that is a gap in coverage, not in intent. Hard rule 7 still applies: the atlas indexes skills, it does not write them."},"history":[{"date":"2026-09-07","field":"core_coverage.state","from":"community-only","to":"core-and-community","reason":"The note left on 2026-09-01 said this state would be wrong if an SAP-published skill existed. capire/skills does: four CAP skills under SAP's OSPO, Apache-2.0, found through the npm sap-cap keyword. Corrected as instructed, and the validator caught it on the same commit that added the artifact."},{"date":"2026-09-07","field":"gap.note","from":"The gap this atlas intends to fill itself, which is a reason to be careful rather than a reason to hurry — see VISION §11.3 and hard rule 7.","to":"Narrowed to breadth: four skills against dozens of capabilities.","reason":"The gap's premise was that no SAP-published skill existed. One does now, so the gap is no longer about absence — it is about how much of the corpus four skills reach."},{"date":"2026-09-09","field":"description","from":"Packaged knowledge you hand a coding agent so it writes correct CAP unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from MCP servers, which answer questions an agent thinks to ask.","to":"Packaged knowledge you hand a coding agent so it writes correct CAP unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.","reason":"The clause pointed at MCP servers for the contrast, but the thing it was contrasting with — an agent reading the real project — moved to capability:agent-code-access when the MCP bucket was split. Guidance's true neighbour is that one: both put project knowledge in front of an agent, one as files and one by reading the thing itself."},{"date":"2026-09-09","field":"ecosystems","from":"cap","to":"cap, ui5, btp","reason":"Seven SAP-published skill repositories entered from the sap-ai-mcp-servers catalogue, three of them UI5's and three BTP's, and the capability existed on the CAP door alone."},{"date":"2026-09-09","field":"description","from":"Packaged knowledge you hand a coding agent so it writes correct CAP unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.","to":"Packaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.","reason":"The cross-ecosystem sentence said \"writes correct CAP\", which was true when CAP was the only door. The CAP-specific wording moved into framing_by_ecosystem.cap where it belongs, and the node's own description now describes the concern rather than one ecosystem's version of it."},{"date":"2026-09-10","field":"ecosystems","from":"cap, ui5, btp","to":"cap, ui5, btp, abap","reason":"Artifacts that answer this concern sat behind the ABAP door with no tile to appear under, so browse counted them and rendered nothing. The concern is one a ABAP developer actually decides there, which is the test for opening a door rather than trimming a serves claim."},{"date":"2026-09-14","field":"coverage_by_flavor.abap-cloud","from":null,"to":"community-only","reason":"The ABAP-door providers of this capability that state the abap-cloud flavor are matt1as-claude-abap-skills, weiserman-rap-skills and babamba2-superclaude-for-sap, all independent; jfilak-sapcli-claude-plugin states no flavor and adam0thman-sap-basis-ops states standard-abap only. No sap-official ABAP provider in the corpus states abap-cloud, so the flavor reading matches the door's own community-only state rather than forking from it."},{"date":"2026-09-14","field":"framing_by_flavor.abap-cloud","from":null,"to":"Narrows to the released-API, RAP and clean-core rules two of the door's providers wrote specifically for ABAP Cloud, quoted from their own READMEs.","reason":"The door-level framing names four providers, two of which (jfilak-sapcli-claude-plugin, adam0thman-sap-basis-ops) do not target ABAP Cloud; a flavor paragraph naming the two that do, and what they actually encode, is a narrower and truer sentence than the door's."},{"date":"2026-09-14","field":"coverage_by_flavor.web-components","from":null,"to":"core-only","reason":"Of the UI5 door's three sap-official providers, only [ui5-webcomponents-agent-skills](artifact:ui5-webcomponents-agent-skills) states the web-components flavor, in its own accessibility and styling SKILL.md files; [ui5-plugins-coding-agents](artifact:ui5-plugins-coding-agents) states freestyle and fiori-elements only, and [sap-ui-theme-designer-plugins](artifact:sap-ui-theme-designer-plugins) states no flavor. One sap-official provider stating the flavor, none independent, reads as core-only rather than a fork of the door's own core-only state."},{"date":"2026-09-14","field":"framing_by_flavor.web-components","from":null,"to":"Narrows to accessibility and styling, the two concerns the shadow DOM raises, versioned inside the component library's own repository.","reason":"The door-level framing already says the Web Components skills ship inside the library and version with it; a flavor paragraph names the two skills the flavor's provider actually carries rather than repeating the door's sentence."},{"date":"2026-10-09","field":"ecosystems","from":"cap, ui5, btp, abap","to":"cap, ui5, btp, abap, commerce","reason":"SAP Commerce opened as a product door (docs/concepts/product-doors.md, ADR-0033) and [sap-commerce-skill](artifact:emenowicz-sap-commerce-skill) entered behind it with no tile to sit under. Packaged knowledge for the Commerce type system, service layer, ImpEx and OCC API is the same concern the node already holds on four doors, so the key was added rather than the capability forked."},{"date":"2026-10-15","field":"coverage_by_ecosystem.btp.state","from":"core-only","to":"core-and-community","reason":"The state was read on 2026-09-09, when the door held three providers and all three were SAP's. The door now holds nineteen of its own: eight sap-official and eleven independent, among them four solution-diagram skill sets, an MCP server that pushes SAP's diagram guideline to its client, two broad collections, and guidance for Datasphere, the Mobile Development Kit and the Integration Suite's Pipeline Concept. Four more serve the door from the CAP, ABAP and SAP Commerce doors. core-only was a statement about who is present and is no longer true."},{"date":"2026-10-15","field":"coverage_by_ecosystem.btp.what_core_does","from":null,"to":"One skill set per service, in the open Agent Skills format, plus the sap-devs command line.","reason":"The field was left empty on 2026-09-09 with the note that no page had been checked stating an intent here. Eight SAP-published entries now sit behind the door and their own READMEs say what each is for and how it installs, so the shape is checkable: a set per service rather than one for the platform, written in a format SAP does not own and installed through a command line SAP does not publish. The old note is replaced, since the sentence it explained is gone."},{"date":"2026-10-15","field":"coverage_by_ecosystem.btp.where_it_stops","from":"At the instruction. Every one of these still runs against a real account with real entitlements, and a skill that generates a command is not the command.","to":"At the service each set is about, and at the registry's bring-your-own-repo model.","reason":"The old sentence described the three operational sets of 2026-09-09 and is not true of the eight that are there now: the Fiori for iOS and developer-tutorial skills generate no commands at all. What the eight share is that each is scoped to one service, which is the boundary a reader needs, and that being listed in SAP's own registry is not SAP publishing it, which the registry states itself."},{"date":"2026-10-15","field":"coverage_by_ecosystem.btp.community_adds","from":null,"to":"The platform-wide and cross-service questions, the solution diagram above all.","reason":"Required by the new state: eleven independent providers are present behind the door and the coverage object said nothing about what they answer beyond SAP's per-service sets."},{"date":"2026-10-15","field":"framing_by_ecosystem.btp","from":"Here the knowledge is mostly operational — what to run, against which account, through which command line. [The Joule A2A toolkit](artifact:sap-samples-joule-a2a-agent-toolkit) scaffolds an agent and generates the btp, cf and joule commands its deployment goes through; [the Automation Pilot skills](artifact:sap-automation-pilot-agent-skills) cover authoring, reviewing, running and debugging Commands against a tenant; [the LeanIX plugin](artifact:sap-leanix-ai-plugins) carries the automation and calculation workflows and calls a hosted MCP server for the reach.","to":"One service at a time, with the solution diagram as the exception where four skill sets carry the same rules.","reason":"The old paragraph named the door's three providers of 2026-09-09 and read \"mostly operational\", which was true of those three. Of the twenty-three options now behind the door, the diagram skill sets, the Fiori for iOS design mapping and the developer-tutorial endpoint map are not operational at all, so the framing described a minority. The sentence now says what the entries have in common, that each is about one service or one surface, and names the one concern several of them answer at once."},{"date":"2026-10-15","field":"facets","from":null,"to":"installs_into, scoped to the BTP door","reason":"Twenty-three options behind one door, all of them packaged knowledge, and the first thing that separates them is whether they load in the assistant the reader already runs: one is a Kiro power, one is placed where a Copilot environment reads it, several install only through Claude Code's plugin marketplace, and two name five or six clients in a single sentence. Each answer is a sentence in the maintainer's own install section. Scoped to btp because this pass assessed that door only; the question is the same on the other four and a later pass can widen the scope rather than a column appearing on doors nobody has filled."},{"date":"2026-10-15","field":"facets.installs_into.ecosystems","from":"btp","to":"btp, abap","reason":"The scope note left on this facet earlier the same day said the question is the same on the other doors and that a later pass could widen it. The ABAP pass is that pass: of the thirteen options behind this door, one installs only through Claude Code's plugin marketplace, one is a VS Code extension whose packs only GitHub Copilot loads, four name between four and six clients in a single install sentence, and two name none at all. \"Pi Coding Agent\" was added to the values for the one entry that names it."},{"date":"2026-10-15","field":"facets","from":"installs_into","to":"installs_into, system_reach","reason":"The question that separates this door's options after the install is what they bring with them. Three groups each state it in their own words: a set that installs a server and connection-tests it, a set that ships no connector and routes each operation to whichever server is already connected, and one that needs no system at all. The three states are what a reader checks their own setup against, and each value rests on a sentence in the maintainer's own documentation. Scoped to abap: the same question could be asked on the other doors, and no pass has filled them."},{"date":"2026-10-15","field":"coverage_by_ecosystem.abap.where_it_stops","from":"At knowledge. What an agent can then read or change in a system comes from an MCP server; a skill says what to write and what to avoid, never what exists.","to":"At knowledge, and the sentence now says what SAP publishes for ABAP and in what form.","reason":"The old sentence was true and said nothing about the official side, which the state makes the reader's first question. SAP's ABAP conventions are published as [Clean ABAP](artifact:sap-styleguides-clean-abap), a document with nothing to install, and SAP's own skills registry keeps each listed skill in its publisher's repository, which the registry states itself. Both are facts about what SAP ships here and both change how the community-only state reads."},{"date":"2026-10-15","field":"coverage_by_ecosystem.abap.community_adds","from":null,"to":"All of it, and the most varied set of any door.","reason":"The state was read on 2026-09-10 against four providers. Thirteen now sit behind the door and four more serve it, and the coverage object said nothing about what any of them answer. The field is where the options belong, since the two sentences on the SAP side may not name them."},{"date":"2026-10-15","field":"coverage_by_ecosystem.abap.note","from":"Every provider here is independent. SAP's own ABAP skills are not in the corpus, which may be absence of evidence rather than evidence of absence.","to":"The same reading, re-checked against thirteen providers, with the registry's own model named.","reason":"Re-checked on 2026-10-15: every one of the thirteen providers behind this door and the four that serve it is independent, so community-only still holds. The registry fact is added because a reader who finds an ABAP skill listed at SAP's own address would otherwise read that as SAP publishing it, and the registry's README says the code stays in the publisher's repository."},{"date":"2026-10-15","field":"framing_by_ecosystem.abap","from":"ABAP has the most varied set of any door, because the same language spans very different targets. [claude-abap-skills](artifact:matt1as-claude-abap-skills) carries [Clean ABAP](artifact:sap-styleguides-clean-abap) and routes each operation to the MCP server that should answer it; [rap-skills](artifact:weiserman-rap-skills) splits RAP guidance by deployment target across branches; [sapcli-claude-plugin](artifact:jfilak-sapcli-claude-plugin) layers agents over an established CLI; [sap-basis-ops](artifact:adam0thman-sap-basis-ops) covers the OS and database plane everyone else skips.","to":"The same opening sentence, with the entries grouped by how much reach each brings.","reason":"The paragraph named the four providers of 2026-09-10 and the door now holds thirteen. The grouping is what the pass found separates them: rules carried into the session, procedures for one task at a time, guidance forked by deployment target, a set that installs its own server, a set over an established command line, the basis plane, and one that needs no system at all."},{"date":"2026-10-15","field":"coverage_by_flavor.standard-abap","from":null,"to":"community-only","reason":"The flavor had no assessment and was derived from the options that state it. Four of the door's providers state standard-abap in their own words — [claude-abap-dev](artifact:coveles-claude-abap-dev), [claude-sap-kit](artifact:silvius1996-claude-sap-kit), [sap-basis-ops](artifact:adam0thman-sap-basis-ops) and [SuperClaude for SAP](artifact:babamba2-superclaude-for-sap) — and all four are independent, so the flavor reads as the door does rather than forking from it."},{"date":"2026-10-15","field":"framing_by_flavor.standard-abap","from":null,"to":"Narrows to classic systems, where the question is often what an agent may touch at all.","reason":"The door's framing groups the entries by the reach they bring; this flavor's own three named entries share something narrower, that the surfaces they care about are the ones a classic system has and a cloud one does not: reports, NAST print output, SmartForms, the operating system beneath the stack, and a landscape of registered systems to guard."},{"date":"2026-10-15","field":"coverage_by_flavor.abap-cloud.where_it_stops","from":"At two independent skill sets built for it specifically: [claude-abap-skills](artifact:matt1as-claude-abap-skills)'s abap-cloud-rap plugin carries rules for the released-API surface, the allowed `@AbapCatalog` annotations and clean-core compliance, and [rap-skills](artifact:weiserman-rap-skills) 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.","to":"At three, with [abap-skills](artifact:likweitan-abap-skills) as the third and the planned RAP branches named.","reason":"[abap-skills](artifact:likweitan-abap-skills) entered on 2026-10-09 stating this flavor, and its abap-cloud skill is the one place in the corpus that writes SAP's clean core levels A to D down in full. Re-reading rap-skills on 2026-10-15 also showed that three of its five deployment-target branches are marked planned, so two targets are covered today, which the old sentence did not say."},{"date":"2026-10-15","field":"framing_by_flavor.abap-cloud","from":"Narrows to what the released-API surface and the RAP object model force onto an agent's rules: [claude-abap-skills](artifact:matt1as-claude-abap-skills) ships a dedicated plugin for allowed `@AbapCatalog` annotations, released APIs and clean-core audits, and [rap-skills](artifact:weiserman-rap-skills) splits its RAP guidance itself by deployment target so a checked-out branch never states a pattern invalid for its target.","to":"The same paragraph with [abap-skills](artifact:likweitan-abap-skills) named for the clean core levels.","reason":"A third provider now states this flavor and what it carries is not what the other two carry: the level concept itself, including that an extension is classified by its lowest-level usage and which authorisation object decides whether Standard ABAP objects may be created at all."},{"date":"2026-10-15","field":"coverage_by_ecosystem.ui5.state","from":"core-only","to":"core-and-community","reason":"The state was read on 2026-09-09, when the door held three providers and all three were SAP's. [scaffold-fiori-ai-bridge](artifact:i562693-vkn-scaffold-fiori-ai-bridge) entered behind this door on 2026-10-09 and is independent, and four independent collections serve the door from the CAP and BTP doors: [secondsky/sap-skills](artifact:secondsky-sap-skills), [skillOverflow](artifact:dankromp-skilloverflow), [SAP Power for Kiro](artifact:mfigueir-sap-power) and [sap-odata-explorer](artifact:kts982-sap-odata-explorer). core-only was a statement about who is present and is no longer true."},{"date":"2026-10-15","field":"coverage_by_ecosystem.ui5.what_core_does","from":null,"to":"Four sets, each about one surface, two of them installed through the Claude and Copilot plugin marketplaces.","reason":"The field was left empty on 2026-09-09 with the note that no page had been checked stating an intent here. Four SAP-published entries now sit behind the door, [sap-fiori-guidelines](artifact:sap-fiori-guidelines) having entered on 2026-09-29, and each README read on 2026-10-15 states what its set is for and how it installs, so the shape is checkable. The old note is replaced, since the sentence it explained is gone."},{"date":"2026-10-15","field":"coverage_by_ecosystem.ui5.where_it_stops","from":"At knowledge. What the agent can then read of your project comes from an MCP server or the editor, not from a skill file.","to":"The same sentence, with the modernisation plugin's own manual server step and the design guidelines' dated baseline added.","reason":"The old sentence was true and general. Two boundaries read on 2026-10-15 are specific and checkable: the UI5 plugins' README says the UI5 MCP server has to be installed by hand when the skills are installed on their own, and sap-fiori-guidelines names the guideline revision it was built from, which makes it one dated reading of a document that keeps moving."},{"date":"2026-10-15","field":"coverage_by_ecosystem.ui5.community_adds","from":null,"to":"One entry behind the door and four collections serving it from elsewhere.","reason":"Required by the new state: the coverage object said nothing about what the independent entries answer, and what the door's own one answers is not a slice of what SAP's four carry."},{"date":"2026-10-15","field":"coverage_by_ecosystem.ui5.note","from":"Every provider behind this door is SAP-published, so core-only is a reading of the corpus rather than a quote from the core. what_core_does is left empty: no page has been checked that states an intent here.","to":"The reading re-checked against five entries behind the door and four serving it, with the lopsided shape named.","reason":"Both halves of the old note are out of date: a provider behind this door is no longer SAP-published, and what_core_does is no longer empty. What the re-read found worth keeping is the shape, four of five entries behind the door being SAP's while the community weight sits in collections whose primary door is CAP or BTP."},{"date":"2026-10-15","field":"framing_by_ecosystem.ui5","from":"Three repositories, published by the UI5 team and split by job rather than bundled. [UI5/plugins-coding-agents](artifact:ui5-plugins-coding-agents) covers everyday development, modernising a legacy project and converting one to TypeScript; [the Web Components skills](artifact:ui5-webcomponents-agent-skills) ship inside the component library itself, so accessibility and styling guidance versions with the components it describes; and [the UI theme designer plugin](artifact:sap-ui-theme-designer-plugins) carries the design system, the Fiori design tokens and which parameters a given control actually reads.","to":"The same three sentences, with [sap-fiori-guidelines](artifact:sap-fiori-guidelines) as the fourth SAP set and the door's one independent entry named for pointing the other way.","reason":"The paragraph counted three repositories and said they were the UI5 team's. Two entries have arrived since: sap-fiori-guidelines on 2026-09-29, which is SAP's but published in the skills library rather than by the UI5 team, and scaffold-fiori-ai-bridge on 2026-10-09, which is independent and is about making a finished application callable rather than about writing one. A count of three and an attribution to one team were both wrong."},{"date":"2026-10-15","field":"facets.installs_into.ecosystems","from":"btp, abap","to":"btp, abap, ui5","reason":"The scope note on this facet says a later pass may widen it where the question separates that door's options. It does here: of the five entries behind the UI5 door, two install as plugins into Claude Code or GitHub Copilot with a command for each, and three name no client at all, while the four collections serving the door name one, three and six between them. The three-state spread is the point, since \"does not say\" is what a reader hits on the two sets SAP ships inside the libraries they describe."},{"date":"2026-10-15","field":"coverage_by_flavor.freestyle","from":null,"to":"core-and-community","reason":"The flavor had no assessment and was derived from the options that state it. Two SAP-published sets state it, [UI5/plugins-coding-agents](artifact:ui5-plugins-coding-agents) and [sap-fiori-guidelines](artifact:sap-fiori-guidelines). No independent entry states it, but [skillOverflow](artifact:dankromp-skilloverflow) serves the door and states no flavor, so it answers in all of them, and its own skill list names UI5 data binding, custom controls, i18n and testing, which is freestyle work by any reading. That is a community presence, so the flavor reads core-and-community rather than following the door's own reading by default."},{"date":"2026-10-15","field":"framing_by_flavor.freestyle","from":null,"to":"Narrows to the hand-written application, where the question is which pattern to follow and which to take out.","reason":"The door's framing groups the entries by the surface each is about. This flavor's own two named entries share something narrower: both are about code a person wrote by hand rather than generated from metadata, which is what makes a deprecated-API pass and a day-to-day skill set the two shapes here."},{"date":"2026-10-15","field":"coverage_by_flavor.fiori-elements","from":null,"to":"core-and-community","reason":"The flavor had no assessment. Two SAP-published sets state it, and this is the one UI5 flavor the independent collections name in their own words: [secondsky/sap-skills](artifact:secondsky-sap-skills), [SAP Power for Kiro](artifact:mfigueir-sap-power) and [sap-odata-explorer](artifact:kts982-sap-odata-explorer) each state it with a sentence of their own, so both halves are present."},{"date":"2026-10-15","field":"framing_by_flavor.fiori-elements","from":null,"to":"Narrows to the annotations and the floorplan, and it is the one UI5 flavor the independent collections name.","reason":"The three independent entries that state this flavor divide differently from the door's own grouping: two generate an application and the third reads the service behind it, which makes the reader's first question whether the annotations can drive a floorplan at all rather than which skill writes the app."},{"date":"2026-10-15","field":"coverage_by_flavor.web-components.what_core_does","from":"[UI5 Web Components agent skills](artifact:ui5-webcomponents-agent-skills) ships two skills inside the components' own repository: accessibility, covering the ARIA roles, keyboard behaviour and screen-reader support the shadow DOM handles automatically plus the `accessibleName`/`accessibleDescription` properties and the `InvisibleMessage` API for the parts it does not; and styling, covering the sanctioned ways to restyle a component from outside its shadow root — CSS shadow parts, custom states, SAP CSS variable overrides and, last, the `addCustomCSS` API — against the piercing selectors and undocumented internals that break on the next release.","to":"The same paragraph, with [sap-fiori-guidelines](artifact:sap-fiori-guidelines) named as the second SAP set that states this flavor.","reason":"The 2026-09-14 reading found one sap-official provider stating the flavor. sap-fiori-guidelines entered on 2026-09-29 and states it in its own frontmatter, naming UI5 Web Components as the framework-agnostic choice for React, Vue and Angular. The state does not change, since both are SAP's, but the sentence that said one was the only one is no longer true."},{"date":"2026-10-15","field":"coverage_by_flavor.web-components.note","from":"[SAP/ui-theme-designer-plugins-for-coding-agents](artifact:sap-ui-theme-designer-plugins), the door's third sap-official provider, states no flavor at all, so it counts for neither reading.","to":"The same sentence, with the one served collection that falls back into this flavor named and read.","reason":"[skillOverflow](artifact:dankromp-skilloverflow) entered on 2026-09-18, after this flavor was assessed, serves the UI5 door and states no flavor, so by the flavor rule it answers in all of them. Its own skill list names SAPUI5 data binding, custom controls, i18n and testing and nothing about the component library, so it is reported as a fallback rather than read as a community presence here. Saying so is what keeps core-only honest beside the options the page lists."},{"date":"2026-10-26","field":"coverage_by_ecosystem.abap.state","from":"community-only","to":"core-and-community","reason":"Reassessed against the graph (check:capabilities): SAP Developers MCP, the sap-official hosted server of developers.sap.com, provides this capability and lists the ABAP door in serves_ecosystems, so an SAP-published provider counts for the door. The earlier reading held when every provider counted for ABAP was independent."},{"date":"2026-10-26","field":"coverage_by_ecosystem.abap.what_core_does","from":null,"to":"SAP Developers MCP hands an agent SAP's tutorials, missions and concept graph over MCP, and Clean ABAP is SAP's published ABAP convention.","reason":"Reassessed against the graph (check:capabilities): the state now has a core half, and the block had no what_core_does to say what it is. Sourced from the server's own MCP quickstart, retrieved 2026-10-26."},{"date":"2026-10-26","field":"coverage_by_ecosystem.abap.community_adds, coverage_by_ecosystem.abap.note","from":"All of it, and the set is the most varied of any door [...]. Four of them package SAP's own Clean ABAP [...] / Every one of the thirteen providers behind this door, and the four that serve it from other doors, is independent. No sap-official skill or rules file for ABAP is in the corpus [...]","to":"Skills and rules for an agent to follow, with three newer shapes named (an extension writing a project's agent files, a plugin of process and domain skills over an in-system MCP server, a desktop workspace with a skill catalogue); the note now says SAP Developers MCP is content to cite and the registry hosts no code.","reason":"Reassessed against the graph (check:capabilities): \"All of it\" and the provider count and absence claims no longer hold with an SAP-published provider counting for the door. Fresh providers abap2ui5-vscode-extension, yannick-thirion-klystron and marianfoo-werkbank change the kinds of answer on offer."},{"date":"2026-10-26","field":"coverage_by_ecosystem.ui5.what_core_does, coverage_by_ecosystem.ui5.community_adds, coverage_by_ecosystem.ui5.note, framing_by_ecosystem.ui5.description","from":"Counts of SAP sets and of entries behind the door (\"four sets\", \"One entry behind the door and four collections\", \"five entries\", \"four of the five entries\").","to":"The same facts stated as kinds, with the independent collections described without a number.","reason":"Reassessed against the graph (check:capabilities): provider counts go stale as providers arrive, and the option list derives them (docs/WRITING.md §3)."},{"date":"2026-10-26","field":"coverage_by_ecosystem.btp.community_adds, framing_by_ecosystem.btp.description","from":"\"Four independent skill sets\", \"two broad collections\", \"with no SAP-published equivalent in the corpus\"; \"One service at a time\", \"four skill sets and an MCP server\".","to":"Counts removed; the absence claim about the corpus removed.","reason":"Reassessed against the graph (check:capabilities): counts of providers and claims that none exist in the corpus are ruled out by docs/WRITING.md §3."},{"date":"2026-10-26","field":"coverage_by_ecosystem.commerce.where_it_stops, coverage_by_ecosystem.commerce.note","from":"\"The door's one provider\"; \"One provider and it is independent [...]. No SAP-published skill or rules file for SAP Commerce is in the corpus [...]\"","to":"sap-commerce-skill named for its baseline; the note names sap-cx-developer-companion beside it and drops the count and the absence claim.","reason":"Reassessed against the graph (check:capabilities): a second provider, abinayaaa-sap-cx-developer-companion, answers this concern for Commerce Cloud, Sales Cloud and Service Cloud APIs. The state stays community-only, since no sap-official provider counts for the door."},{"date":"2026-10-26","field":"coverage_by_flavor.standard-abap.where_it_stops, coverage_by_flavor.standard-abap.note, coverage_by_flavor.abap-cloud.where_it_stops, coverage_by_flavor.abap-cloud.note, coverage_by_flavor.freestyle.community_adds, coverage_by_flavor.freestyle.note, coverage_by_flavor.fiori-elements.note, coverage_by_flavor.web-components.note","from":"Counts (\"four independent sets\", \"three independent skill sets\", \"One collection\", \"three collections\", \"three independent entries\", \"the door's third sap-official provider\") and absence claims (\"No sap-official skill or rules file for ... is in the corpus\").","to":"The same facts without the counts and without the claims that none exist; the states are unchanged.","reason":"Reassessed against the graph (check:capabilities): docs/WRITING.md §3 rules out provider counts and absence claims in every capability field."}],"facets":[{"key":"installs_into","label":"Installs into","kind":"many","values":["Claude Code","Claude Desktop","Cowork","GitHub Copilot","Cursor","Codex","Gemini CLI","OpenCode","Kiro","Pi Coding Agent"],"ecosystems":["btp","abap","ui5"]},{"key":"system_reach","label":"System reach","kind":"one","values":["Supplied with it","You connect it","None needed"],"ecosystems":["abap"]}],"framing_by_ecosystem":{"cap":{"description":"Packaged knowledge that makes an agent write correct CAP without being told each time — [capire/skills](artifact:capire-skills) is SAP's own set, in the open skill standard and installable four ways."},"ui5":{"description":"One surface at a time, and most of what sits behind this door is SAP's. [UI5/plugins-coding-agents](artifact:ui5-plugins-coding-agents) covers everyday development, modernising a legacy project and converting one to TypeScript, as three plugins rather than one bundle; [the Web Components skills](artifact:ui5-webcomponents-agent-skills) ship inside the component library itself, so accessibility and styling guidance versions with the components it describes; [the UI theme designer plugin](artifact:sap-ui-theme-designer-plugins) carries the design system, the Fiori design tokens and which parameters a given control actually reads; and [sap-fiori-guidelines](artifact:sap-fiori-guidelines), published in SAP's skills library rather than by the UI5 team, carries the Fiori design guidelines themselves as reference files dated to one revision. [scaffold-fiori-ai-bridge](artifact:i562693-vkn-scaffold-fiori-ai-bridge) points the other way: it hands an agent the procedure for making a finished application callable by [SAP Joule](artifact:sap-joule), not for writing one."},"btp":{"description":"Service by service. An entry here carries what an agent needs for one BTP service or one surface, from [the AI Core skills](artifact:sap-aicore-skills) and their deployment lifecycle to [the Automation Pilot skills](artifact:sap-automation-pilot-agent-skills) and their Commands, [the Application Frontend migration](artifact:sap-samples-html5-applications-migration-skills-for-sap-btp) and [the Mobile Development Kit's metadata](artifact:logalitech-sap-mdk-apps), 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 server](artifact:etosin-arc-draw) carry the same [SAP visual language](artifact:sap-btp-solution-diagrams) and differ mainly in how its rules reach the agent."},"abap":{"description":"ABAP has the most varied set of any door, because the same language spans very different targets and the entries divide by how much reach each brings with it. [claude-abap-skills](artifact:matt1as-claude-abap-skills) carries [Clean ABAP](artifact:sap-styleguides-clean-abap) into the session and ships no connector at all, routing each operation to the MCP server that should answer it; [claude-abap-dev](artifact:coveles-claude-abap-dev) and [ARC-1 Skills](artifact:arc-mcp-arc-1-skills) are procedures for one task at a time that run on servers you connect yourself; [rap-skills](artifact:weiserman-rap-skills) splits RAP guidance by deployment target across branches; [SuperClaude for SAP](artifact:babamba2-superclaude-for-sap) installs its own server and labels every system it may write to; [sapcli-claude-plugin](artifact:jfilak-sapcli-claude-plugin) layers agents over an established command line; [sap-basis-ops](artifact:adam0thman-sap-basis-ops) covers the OS and database plane everyone else skips; and [abap-offstack-aunit](artifact:alokm3hta-star-abap-offstack-testing) runs the tests with no system at all."}},"coverage_by_ecosystem":{"ui5":{"state":"core-and-community","assessed_at":"2026-10-15","what_core_does":"SAP publishes sets behind this door, each about one surface and none for the framework as a whole. [UI5/plugins-coding-agents](artifact:ui5-plugins-coding-agents) is three plugins split by job, everyday development, replacing deprecated APIs in an existing project, and converting one to TypeScript; [the Web Components skills](artifact:ui5-webcomponents-agent-skills) ship inside the component library's own repository and cover accessibility and styling; [the UI theme designer plugin](artifact:sap-ui-theme-designer-plugins) carries the SAP Design System, the Fiori design tokens and which theming parameters a given component reads; and [sap-fiori-guidelines](artifact:sap-fiori-guidelines), in SAP's skills library, carries the Fiori design guidelines as reference files built from v1.145 of May 2026. The development plugins and the theme designer install as plugins into Claude Code or GitHub Copilot with a command for each, and through the skills command line for an agent that reads neither.","where_it_stops":"At knowledge. What the agent can then read of your project comes from [@ui5/mcp-server](artifact:ui5-mcp-server) or the editor and not from a skill file, and the plugins say so themselves: installed as skills alone, that server has to be put there by hand. In one place it also stops at a dated reading, since the design-guidelines skill names the revision it was built from and the guidelines keep moving.","community_adds":"[scaffold-fiori-ai-bridge](artifact:i562693-vkn-scaffold-fiori-ai-bridge) lives behind the door and answers a question SAP's sets are not about, turning what an application can already do into [SAP Joule](artifact:sap-joule) Frontend Actions or WebMCP tools. Collections serve the door from elsewhere and are broad SAP collections, not UI5 sets: [secondsky/sap-skills](artifact:secondsky-sap-skills), [SAP Power for Kiro](artifact:mfigueir-sap-power) and [sap-odata-explorer](artifact:kts982-sap-odata-explorer) name Fiori elements work in their own words, Kiro's is packaged as a power instead of a skill standard, and [skillOverflow](artifact:dankromp-skilloverflow) states no flavor and carries UI5 data binding, controls, i18n and testing as separate skills.","relationship":"unassessed","note":"The door is lopsided. The sets behind it are mostly SAP's, each about a surface SAP owns, and the community weight sits in collections whose primary door is CAP or BTP and in the entry that answers an outcome of its own. Which half was first here is not established, so the pattern is left unassessed rather than read off the dates the entries happened to enter the atlas.","sources":[{"url":"https://github.com/UI5/plugins-coding-agents","title":"UI5/plugins-coding-agents — README, the three plugins","checked":"2026-10-15","quote":"Autonomous, multi-phase workflow and specialized skills for modernizing UI5 projects by replacing deprecated APIs and eliminating legacy patterns."},{"url":"https://github.com/UI5/plugins-coding-agents/blob/main/plugins/ui5/README.md","title":"UI5/plugins-coding-agents — plugins/ui5/README.md, Installation","checked":"2026-10-15","quote":"claude plugin install ui5@claude-plugins-official"},{"url":"https://github.com/UI5/plugins-coding-agents/blob/main/plugins/ui5/README.md","title":"UI5/plugins-coding-agents — plugins/ui5/README.md, skills-only installation","checked":"2026-10-15","quote":"You need to install the [UI5 MCP server](https://github.com/UI5/mcp-server) manually when installing the skills only."},{"url":"https://github.com/SAP/ui-theme-designer-plugins-for-coding-agents","title":"SAP/ui-theme-designer-plugins-for-coding-agents — README","checked":"2026-10-15","quote":"A collection of plugins for coding agents that provide AI coding assistants with knowledge and tooling for working with UI theme designer and the SAP Design System"},{"url":"https://github.com/UI5/webcomponents/blob/main/skills/accessibility/SKILL.md","title":"UI5/webcomponents — skills/accessibility/SKILL.md","checked":"2026-10-15","quote":"UI5 Web Components have built-in accessibility: ARIA roles, keyboard navigation, screen reader support, and high contrast themes are handled automatically in the shadow DOM."},{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-guidelines/README.md","title":"SAP/ai-skills-library — skills/sap-fiori-guidelines/README.md","checked":"2026-10-15","quote":"Built from SAP Fiori Design Guidelines **v1.145** (May 2026)."},{"url":"https://github.com/I562693-VKN/Skill-Hub/blob/main/skills/Scaffold-fiori-ai-bridge/SKILL.md","title":"I562693-VKN/Skill-Hub — skills/Scaffold-fiori-ai-bridge/SKILL.md, purpose","checked":"2026-10-15","quote":"Make a UI5 or Fiori app / library control AI-callable. Generates the JS bridge and all YAML files needed for Joule Frontend Actions"}]},"btp":{"state":"core-and-community","assessed_at":"2026-10-15","what_core_does":"SAP publishes a skill set per service rather than one for the platform: [AI Core](artifact:sap-aicore-skills), [Automation Pilot](artifact:sap-automation-pilot-agent-skills), [LeanIX](artifact:sap-leanix-ai-plugins), [Joule over A2A](artifact:sap-samples-joule-a2a-agent-toolkit), [the Application Frontend migration](artifact:sap-samples-html5-applications-migration-skills-for-sap-btp), [Fiori for iOS](artifact:sap-fiori-ios) and [the developer tutorial API](artifact:sap-tutorials-content) 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-devs](artifact:sap-samples-sap-devs-cli) is a command line that writes SAP context into whichever AI tool is configured, with a sync command for keeping that content current.","where_it_stops":"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.","community_adds":"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.","relationship":"unassessed","note":"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.","sources":[{"url":"https://github.com/SAP/ai-skills-library","title":"SAP/ai-skills-library — README, About this project","checked":"2026-10-15","quote":"The AI Skills Library uses a **bring-your-own-repo** model — your skill code stays in your own public GitHub repository. You don't submit skill code here."},{"url":"https://github.com/SAP/ai-skills-library","title":"SAP/ai-skills-library — README, Requirements and Setup","checked":"2026-10-15","quote":"Install skills using the [skills CLI](https://github.com/vercel-labs/skills), which supports Claude Code, Codex, Cursor, OpenCode, and many more agents."},{"url":"https://github.com/SAP/ai-skills-library/blob/main/plugins/aicore-skills/README.md","title":"SAP/ai-skills-library — plugins/aicore-skills/README.md, Installation","checked":"2026-10-15","quote":"Supported harnesses: Claude Code, Codex, Cursor, Gemini CLI, and any agent that supports the [agentskills.io](https://agentskills.io) specification."},{"url":"https://github.com/SAP/automation-pilot-agent-skills","title":"SAP/automation-pilot-agent-skills — README, Prerequisites","checked":"2026-10-15","quote":"You'll also need an SAP Automation Pilot tenant with API credentials."},{"url":"https://github.com/SAP/leanix-ai-plugins","title":"SAP/leanix-ai-plugins — README, Requirements and Setup","checked":"2026-10-15","quote":"this marketplace ships the `sap-leanix` plugin that bundles every LeanIX skill in this repo, along with the LeanIX MCP server config"},{"url":"https://github.com/SAP-samples/joule-a2a-agent-toolkit","title":"SAP-samples/joule-a2a-agent-toolkit — README, Getting Started","checked":"2026-10-15","quote":"Start Claude Code with the toolkit plugin, then log in to CF and Joule:"},{"url":"https://github.com/SAP-samples/html5-applications-migration-skills-for-sap-btp","title":"SAP-samples/html5-applications-migration-skills-for-sap-btp — README, Download and Installation","checked":"2026-10-15","quote":"**No MCP servers or network access required.** The plugin operates entirely on local files."},{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-ios/README.md","title":"SAP/ai-skills-library — skills/sap-fiori-ios/README.md, Installation","checked":"2026-10-15","quote":"npx skills add SAP/ai-skills-library --skill sap-fiori-ios"},{"url":"https://github.com/sap-tutorials/tutorials-ims/blob/main/skills/sap-tutorials-content/SKILL.md","title":"sap-tutorials/tutorials-ims — skills/sap-tutorials-content/SKILL.md, frontmatter description","checked":"2026-10-15","quote":"Read SAP developer tutorial content from the public developers.sap.com API — catalog, navigation, tutorial HTML/JSON, and full-text search."},{"url":"https://github.com/SAP-samples/sap-devs-cli","title":"SAP-samples/sap-devs-cli — README, quick start","checked":"2026-10-15","quote":"# Inject SAP context into your AI tools"},{"url":"https://github.com/SAP-samples/sap-devs-cli","title":"SAP-samples/sap-devs-cli — README, quick start","checked":"2026-10-15","quote":"# Keep content current"}]},"abap":{"state":"core-and-community","assessed_at":"2026-10-15","relationship":"unassessed","what_core_does":"SAP's part here is two things that are not skill files. [SAP Developers MCP](artifact:sap-developers-mcp), the hosted server of developers.sap.com, hands an agent SAP's tutorials, missions and concept graph over MCP, for ABAP and the other stacks alike, and [Clean ABAP](artifact:sap-styleguides-clean-abap) is SAP's published ABAP convention, a document with nothing to install.","where_it_stops":"At knowledge. What an agent can then read or change in a system comes from an MCP server or a command line, and a skill says what to write and what to avoid, never what exists. SAP's ABAP conventions are published as [Clean ABAP](artifact:sap-styleguides-clean-abap), a document with nothing to install, and SAP's own skills registry keeps each listed skill in its publisher's repository, so a repository listed there is published by whoever owns it.","community_adds":"The skills and rules an agent follows, and the set is the most varied of any door because the same language spans very different targets. Rules read into the session beside procedures for one task at a time, RAP guidance forked by deployment target, clean core audits against SAP's released-objects information, the operating system and database plane beneath the stack, and a test harness that runs ABAP Unit with no system at all. Several package SAP's own [Clean ABAP](artifact:sap-styleguides-clean-abap) for an agent, and several state which MCP server each kind of operation should be routed to instead of shipping a connector. Three newer shapes sit beside them: [abap2UI5 for VS Code](artifact:abap2ui5-vscode-extension) writes the agent files of an abap2UI5 project into an existing one, [Klystron](artifact:yannick-thirion-klystron) is a plugin of process and domain skills over an MCP server that runs inside the application server, and [Werkbank](artifact:marianfoo-werkbank) is a desktop workspace with a catalogue of ABAP, CAP and UI5 skills.","note":"[SAP Developers MCP](artifact:sap-developers-mcp) serves this door from the umbrella and gives an agent SAP's learning content to cite, not rules to follow. SAP's own skills registry indexes other people's repositories and does not host their code, so an ABAP skill listed at SAP's address is not SAP publishing it.","sources":[{"url":"https://github.com/SAP/ai-skills-library","title":"SAP/ai-skills-library — README, About this project","checked":"2026-10-15","quote":"Your skill code stays in your own public GitHub repository. You don't submit skill code here."},{"url":"https://github.com/SAP/styleguides/blob/main/clean-abap/CleanABAP.md","title":"SAP/styleguides — Clean ABAP","checked":"2026-08-31"},{"url":"https://raw.githubusercontent.com/sap-tutorials/tutorials-ims/b15bbe7ddea4e7a947fb61e4ed34b6951c231a9e/docs/end-users/mcp-quickstart.md","title":"sap-tutorials/tutorials-ims — MCP Quickstart","checked":"2026-10-26","quote":"can search tutorials, read missions, and query the knowledge graph directly"}]},"commerce":{"state":"community-only","assessed_at":"2026-10-09","where_it_stops":"At one stated baseline, and at knowledge. [sap-commerce-skill](artifact:emenowicz-sap-commerce-skill) is written against SAP Commerce Cloud 2211-jdk21.1 or later and marks older releases and the JSP Accelerator as legacy, so a project below that baseline is outside what it states; and what it hands an agent is reference material and templates, with one shipped script the only thing that reaches a running instance.","note":"Community-only is a reading of the corpus and not a statement from SAP. [sap-cx-developer-companion](artifact:abinayaaa-sap-cx-developer-companion) answers a different question beside the Commerce type system, ImpEx and OCC material: finding a Commerce Cloud, Sales Cloud or Service Cloud API, writing CDS for a CX extension and explaining an error."}},"coverage_by_flavor":{"standard-abap":{"state":"community-only","assessed_at":"2026-10-15","where_it_stops":"At the independent sets that state this flavor in their own words. [claude-abap-dev](artifact:coveles-claude-abap-dev) records the system it was tried against, S/4HANA 2023 on premise, and carries five workflows for ATC remediation, a clean core audit, a Clean ABAP review, ABAP Unit and debugging; [claude-sap-kit](artifact:silvius1996-claude-sap-kit) reaches the three things its README says ADT does not cover, running a report, previewing NAST print output and editing SmartForms; [sap-basis-ops](artifact:adam0thman-sap-basis-ops) covers the operating system and database beneath the stack; and [SuperClaude for SAP](artifact:babamba2-superclaude-for-sap) registers a landscape of systems and blocks writes against the ones labelled QA or production.","note":"Community-only is a reading of this door's own providers and not a quote from the core. [rap-skills](artifact:weiserman-rap-skills) declares a branch for S/4HANA on-premise as planned, which would state this flavor when it lands.","sources":[{"url":"https://github.com/CoVeles/claude-abap-dev","title":"CoVeles/claude-abap-dev — README, Tested against","checked":"2026-10-06","quote":"S/4HANA 2023 on premise (SAP_BASIS 758) with mcp-abap-adt 17.1.0, vibing-steampunk 2.60.0, an abaplint MCP server (core 2.120) and mcp-sap-docs 0.3.55"},{"url":"https://raw.githubusercontent.com/silvius1996/claude-sap-kit/main/README.md","title":"silvius1996/claude-sap-kit — README, Requirements","checked":"2026-09-28","quote":"SAP_BASIS 7.50 or later, on-premise or private cloud: **ECC 6.0 EHP8** and **S/4HANA** (all releases)."},{"url":"https://github.com/adam0thman/sap-basis-ops","title":"adam0thman/sap-basis-ops — README","checked":"2026-09-13","quote":"Targets classic on-premise / IaaS NetWeaver and S/4HANA landscapes on"},{"url":"https://raw.githubusercontent.com/weiserman/rap-skills/main/README.md","title":"weiserman/rap-skills — README, branch table","checked":"2026-10-15","quote":"| `s4-onprem/managed` | S/4HANA On-Premise | Managed | 🔜 Planned |"}]},"abap-cloud":{"state":"community-only","assessed_at":"2026-10-15","where_it_stops":"At the independent skill sets built for it specifically. [claude-abap-skills](artifact:matt1as-claude-abap-skills)'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-skills](artifact:weiserman-rap-skills) 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-skills](artifact:likweitan-abap-skills) 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.","sources":[{"url":"https://raw.githubusercontent.com/matt1as/claude-abap-skills/main/README.md","title":"matt1as/claude-abap-skills — README, the abap-cloud-rap plugin","checked":"2026-10-15","quote":"ABAP Cloud / RAP rules plus three skills (rules read on invocation, as above):"},{"url":"https://raw.githubusercontent.com/matt1as/claude-abap-skills/main/README.md","title":"matt1as/claude-abap-skills — README, clean-core-check","checked":"2026-10-15","quote":"- **`/abap-cloud-rap:clean-core-check`** — audit objects for clean core compliance"},{"url":"https://raw.githubusercontent.com/weiserman/rap-skills/main/README.md","title":"weiserman/rap-skills — README","checked":"2026-09-14","quote":"Not all RAP development is the same — the syntax, available APIs, BDEF patterns, and tooling constraints differ significantly between BTP Steampunk, S/4HANA Cloud, and on-premise."},{"url":"https://raw.githubusercontent.com/weiserman/rap-skills/main/README.md","title":"weiserman/rap-skills — README, branch table","checked":"2026-10-15","quote":"| `s4-public/managed` | S/4HANA Cloud Public Ed. | Managed | 🔜 Planned |"},{"url":"https://github.com/likweitan/abap-skills/blob/main/skills/abap-cloud/SKILL.md","title":"likweitan/abap-skills — skills/abap-cloud/SKILL.md, frontmatter description","checked":"2026-10-09","quote":"Help with ABAP Cloud development and the clean core level concept (Levels A, B, C, D)"},{"url":"https://github.com/likweitan/abap-skills/blob/main/skills/abap-cloud/SKILL.md","title":"likweitan/abap-skills — skills/abap-cloud/SKILL.md, clean core levels","checked":"2026-10-09","quote":"Authorization object `S_ABPLNGVS` controls whether a developer may create objects in Standard ABAP or only in ABAP for Cloud Development."}],"note":"[SuperClaude for SAP](artifact:babamba2-superclaude-for-sap) also states this flavor, but for its own MCP server and write governance across system profiles rather than for RAP or released-API rules."},"freestyle":{"state":"core-and-community","assessed_at":"2026-10-15","what_core_does":"Two of the door's SAP-published sets state this flavor. [UI5/plugins-coding-agents](artifact:ui5-plugins-coding-agents) is written for creating UI5 projects, replacing deprecated APIs in an existing one and converting a JavaScript project to TypeScript, and [sap-fiori-guidelines](artifact:sap-fiori-guidelines) names SAPUI5 as what full Fiori applications on BTP and S/4HANA are built with.","where_it_stops":"At the framework rather than the project. Both are instruction sets: the project read, the UI5 linter and the manifest check belong to [@ui5/mcp-server](artifact:ui5-mcp-server), and the plugins state that installing the skills on their own leaves that server to be installed by hand.","community_adds":"[skillOverflow](artifact:dankromp-skilloverflow) serves this door from CAP and states no flavor, so it answers in all of them. Its own skill list names UI5 data binding, custom controls, i18n and testing as separate skills, which is freestyle work by any reading.","relationship":"unassessed","note":"The door's own independent entry, [scaffold-fiori-ai-bridge](artifact:i562693-vkn-scaffold-fiori-ai-bridge), states no flavor, and the collections that do state a UI5 flavor state Fiori elements instead, so the community presence here rests on a collection that states no flavor and whose own skill list is freestyle UI5.","sources":[{"url":"https://github.com/UI5/plugins-coding-agents","title":"UI5/plugins-coding-agents — README, the UI5 plugin","checked":"2026-10-15","quote":"Full-featured SAPUI5/OpenUI5 development plugin that supports project creation, API reference look-up, UI5 linter integration, and a broad set of best-practice skills."},{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-guidelines/SKILL.md","title":"SAP/ai-skills-library — skills/sap-fiori-guidelines/SKILL.md, technology table","checked":"2026-10-15","quote":"SAPUI5 | Full SAP Fiori applications, SAP BTP, S/4HANA"},{"url":"https://github.com/DanKromp/skillOverflow","title":"DanKromp/skillOverflow — README, skill list","checked":"2026-10-15","quote":"ui5-data-binding | OData V4 model, list binding, context binding, $batch, side effects"},{"url":"https://github.com/UI5/plugins-coding-agents/blob/main/plugins/ui5/README.md","title":"UI5/plugins-coding-agents — plugins/ui5/README.md, skills-only installation","checked":"2026-10-15","quote":"You need to install the [UI5 MCP server](https://github.com/UI5/mcp-server) manually when installing the skills only."}]},"fiori-elements":{"state":"core-and-community","assessed_at":"2026-10-15","what_core_does":"[UI5/plugins-coding-agents](artifact:ui5-plugins-coding-agents) states this flavor for its project creation, and [sap-fiori-guidelines](artifact:sap-fiori-guidelines) names Fiori elements as what a metadata-driven application over an OData service is built with, with a reference file of its own for the floorplans beside the one for S/4HANA design.","where_it_stops":"At the floorplan and the page type. Neither set states a skill for writing the `@UI` annotations that drive a list report or an object page against a real service, which is where a generated application either works or does not.","community_adds":"This is the one UI5 flavor the independent collections state in their own words, and three of them do. [secondsky/sap-skills](artifact:secondsky-sap-skills) activates its Fiori tools plugin on a request to set up a Fiori elements application, [SAP Power for Kiro](artifact:mfigueir-sap-power) answers a request for a list report over an OData service, and [sap-odata-explorer](artifact:kts982-sap-odata-explorer) reads the other end, checking a service's annotations against a list-report and object-page checklist before an application is generated at all.","relationship":"unassessed","note":"The independent entries that state this flavor serve the door from BTP and do not live behind it. The one of them that reaches a real service, [sap-odata-explorer](artifact:kts982-sap-odata-explorer), calls itself early-stage in its own README.","sources":[{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-guidelines/SKILL.md","title":"SAP/ai-skills-library — skills/sap-fiori-guidelines/SKILL.md, technology table","checked":"2026-10-15","quote":"SAP Fiori Elements | Metadata-driven apps with OData services"},{"url":"https://github.com/UI5/plugins-coding-agents","title":"UI5/plugins-coding-agents — README","checked":"2026-09-13","quote":"Helps with the creation of new UI5 projects when working with coding agents"},{"url":"https://github.com/secondsky/sap-skills","title":"secondsky/sap-skills — README","checked":"2026-09-13","quote":"**\"Set up Fiori Elements app\"** → `sap-fiori-tools` activates"},{"url":"https://github.com/mfigueir/sap-power","title":"mfigueir/sap-power — README","checked":"2026-09-13","quote":"\"Build a Fiori List Report for my OData service\""},{"url":"https://github.com/kts982/sap-odata-explorer","title":"kts982/sap-odata-explorer — README","checked":"2026-09-13","quote":"evaluates a service's annotations against a Fiori list-report / object-page checklist"},{"url":"https://raw.githubusercontent.com/kts982/sap-odata-explorer/main/README.md","title":"kts982/sap-odata-explorer — README, status","checked":"2026-10-15","quote":"Early-stage project. Core workflows work end-to-end on real SAP systems, but packaging, docs, and polish are still evolving."}]},"web-components":{"state":"core-only","assessed_at":"2026-10-15","what_core_does":"[UI5 Web Components agent skills](artifact:ui5-webcomponents-agent-skills) ships two skills inside the components' own repository: accessibility, covering the ARIA roles, keyboard behaviour and screen-reader support the shadow DOM handles automatically plus the `accessibleName`/`accessibleDescription` properties and the `InvisibleMessage` API for the parts it does not; and styling, covering the sanctioned ways to restyle a component from outside its shadow root — CSS shadow parts, custom states, SAP CSS variable overrides and, last, the `addCustomCSS` API — against the piercing selectors and undocumented internals that break on the next release. Beside them [sap-fiori-guidelines](artifact:sap-fiori-guidelines) states this flavor too, naming UI5 Web Components as the framework-agnostic choice for React, Vue or Angular and carrying the colour, typography and page-type references it shares with the other UI5 flavors.","where_it_stops":"At those concerns. [UI5/plugins-coding-agents](artifact:ui5-plugins-coding-agents), the door's other set of development plugins, states only the freestyle and fiori-elements flavors, so project scaffolding, deprecated-API modernisation and TypeScript conversion have no stated Web Components equivalent in the corpus. It also stops short of saying how the two skills reach an agent: nothing read in the components' repository on 2026-10-15 names a client they install into.","sources":[{"url":"https://raw.githubusercontent.com/UI5/webcomponents/main/skills/accessibility/SKILL.md","title":"UI5/webcomponents — skills/accessibility/SKILL.md","checked":"2026-10-15","quote":"UI5 Web Components have built-in accessibility: ARIA roles, keyboard navigation, screen reader support, and high contrast themes are handled automatically in the shadow DOM."},{"url":"https://raw.githubusercontent.com/UI5/webcomponents/main/skills/styling/SKILL.md","title":"UI5/webcomponents — skills/styling/SKILL.md, frontmatter description","checked":"2026-10-15","quote":"How to customize and style UI5 Web Components. Covers CSS shadow parts, CSS custom states, CSS variables, and tag-level styling."},{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-guidelines/SKILL.md","title":"SAP/ai-skills-library — skills/sap-fiori-guidelines/SKILL.md, technology table","checked":"2026-10-15","quote":"UI5 Web Components | Framework-agnostic, React/Vue/Angular integration"},{"url":"https://github.com/DanKromp/skillOverflow","title":"DanKromp/skillOverflow — README, skill list","checked":"2026-10-15","quote":"ui5-custom-controls | Control.extend(), renderer apiVersion 2, lifecycle hooks"}],"note":"[SAP/ui-theme-designer-plugins-for-coding-agents](artifact:sap-ui-theme-designer-plugins), another sap-official provider behind the door, states no flavor at all, so it counts for neither reading. [skillOverflow](artifact:dankromp-skilloverflow) serves this door and states no flavor either, so it falls back into this flavor, but its own skill list names SAPUI5 data binding, custom controls, i18n and testing and nothing about the component library, so it is reported as a fallback rather than read as a community presence here."}},"framing_by_flavor":{"standard-abap":{"description":"Narrows to classic systems, where the question is often what an agent may touch at all rather than which pattern it should follow. [claude-sap-kit](artifact:silvius1996-claude-sap-kit) reaches the surfaces its README says ADT does not cover, running a report, previewing print output and editing SmartForms; [sap-basis-ops](artifact:adam0thman-sap-basis-ops) writes runbooks for the operating system and database beneath the stack and leaves running them to somebody else; and [SuperClaude for SAP](artifact:babamba2-superclaude-for-sap) labels each registered system so a write against QA or production is blocked in two places rather than one."},"abap-cloud":{"description":"Narrows to what the released-API surface and the RAP object model force onto an agent's rules: [claude-abap-skills](artifact:matt1as-claude-abap-skills) ships a dedicated plugin for allowed `@AbapCatalog` annotations, released APIs and clean core audits, [rap-skills](artifact:weiserman-rap-skills) splits its RAP guidance itself by deployment target so a checked-out branch never states a pattern invalid for its target, and [abap-skills](artifact:likweitan-abap-skills) is the one place in the corpus that writes the clean core levels A to D down in full."},"freestyle":{"description":"Narrows to the application somebody wrote by hand, where the question is which pattern an agent should follow and which it should take out. [UI5/plugins-coding-agents](artifact:ui5-plugins-coding-agents) answers both halves and keeps them apart, with one plugin for creating and developing and a second whose whole job is replacing deprecated APIs in a project that already exists, and [skillOverflow](artifact:dankromp-skilloverflow) answers the day-to-day pieces as separate skills: data binding, custom controls, i18n and testing."},"fiori-elements":{"description":"Narrows to the annotations and the floorplan, and it is the one UI5 flavor the independent collections name. The decision here is less which skill writes the application than whether the service behind it is annotated well enough to drive a floorplan at all, which is why [sap-odata-explorer](artifact:kts982-sap-odata-explorer)'s list-report checklist belongs beside the generators in [secondsky/sap-skills](artifact:secondsky-sap-skills) and [SAP Power for Kiro](artifact:mfigueir-sap-power) rather than after them."},"web-components":{"description":"Narrows to the two concerns the shadow DOM makes an agent get wrong on its own: accessibility and styling. [UI5 Web Components agent skills](artifact:ui5-webcomponents-agent-skills) ships both inside the component library's own repository, so the guidance versions with the components it describes rather than dating separately, and [sap-fiori-guidelines](artifact:sap-fiori-guidelines) states the flavor from the other direction, as the framework-agnostic choice for a React, Vue or Angular application, carrying the design rules the three UI5 flavors share."}},"drafted_with_ai":true},"sap_delivery":{"door":"cap","all":{"built_in":[],"documented_pattern":[],"announced":[],"packages":[{"ref":"artifact:capire-skills","name":"capire/skills","json":"/artifacts/capire-skills.json"}]},"by_flavor":{"node":{"built_in":[],"documented_pattern":[],"announced":[],"packages":[{"ref":"artifact:capire-skills","name":"capire/skills","json":"/artifacts/capire-skills.json"}]},"java":{"built_in":[],"documented_pattern":[],"announced":[],"packages":[{"ref":"artifact:capire-skills","name":"capire/skills","json":"/artifacts/capire-skills.json"}]}}},"edges":{"use_cases":[{"id":"change-a-btp-service-from-an-agent-session","name":"Change a BTP service from an agent session","capability":"capability:agent-guidance","ecosystem":"btp","outcome":"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.","boundary":"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](capability:agent-code-access). Entitlements, logins and authorisations stay the developer's, and nothing here was run.","origin":"Editorial hypothesis, from the split visible across this door's entries: some ship scripts and API calls, and one states in its own scope section that it does not deploy.","contributions":[{"ref":"artifact:sap-automation-pilot-agent-skills","role":"deploys and triggers Commands through the Automation Pilot APIs","state":"conditional","description":"The 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.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/SAP/automation-pilot-agent-skills","title":"SAP/automation-pilot-agent-skills — README, what the API skills do","checked":"2026-10-15","quote":"Deploy, update, list, and delete Commands, Inputs, and MCP servers via API"},{"url":"https://github.com/SAP/automation-pilot-agent-skills","title":"SAP/automation-pilot-agent-skills — README, what the API skills do","checked":"2026-10-15","quote":"Trigger Commands, monitor status, view logs"},{"url":"https://github.com/SAP/automation-pilot-agent-skills","title":"SAP/automation-pilot-agent-skills — README, Prerequisites","checked":"2026-10-15","quote":"You'll also need an SAP Automation Pilot tenant with API credentials."},{"url":"https://github.com/SAP/automation-pilot-agent-skills","title":"SAP/automation-pilot-agent-skills — README, Load environment variables","checked":"2026-10-15","quote":"Before using the API skills, load your credentials:"}]},{"ref":"artifact:sap-aicore-skills","role":"runs the AI Core lifecycle operations as its own scripts","state":"conditional","description":"Its 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.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/SAP/ai-skills-library/blob/main/plugins/aicore-skills/skills/aicore-lifecycle-management/SKILL.md","title":"SAP/ai-skills-library — aicore-lifecycle-management/SKILL.md, frontmatter description","checked":"2026-10-15","quote":"Manage SAP AI Core lifecycle resources: scenarios, executables, configurations, and deployments."},{"url":"https://github.com/SAP/ai-skills-library/blob/main/plugins/aicore-skills/skills/aicore-lifecycle-management/SKILL.md","title":"SAP/ai-skills-library — aicore-lifecycle-management/SKILL.md, how the scripts are run","checked":"2026-10-15","quote":"Run all scripts from the skill root directory with `uv run scripts/<name>.py`."},{"url":"https://github.com/SAP/ai-skills-library/blob/main/plugins/aicore-skills/skills/aicore-lifecycle-management/SKILL.md","title":"SAP/ai-skills-library — aicore-lifecycle-management/SKILL.md, mutating scripts","checked":"2026-10-15","quote":"Scripts that delete or mutate state require `--confirm`. Always pass it explicitly; never bypass it."},{"url":"https://github.com/SAP/ai-skills-library/blob/main/plugins/aicore-skills/README.md","title":"SAP/ai-skills-library — plugins/aicore-skills/README.md, prerequisites","checked":"2026-10-15","quote":"SAP AI Core instance with credentials configured"}]},{"ref":"artifact:sap-samples-joule-a2a-agent-toolkit","role":"generates the commands, and deploys through one of its own","state":"conditional","description":"Its 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.","sources":[{"url":"https://github.com/SAP-samples/joule-a2a-agent-toolkit","title":"SAP-samples/joule-a2a-agent-toolkit — README, the btp-cli skill","checked":"2026-10-15","quote":"Generates correct `btp` commands for managing BTP global accounts, subaccounts, services, and security"},{"url":"https://github.com/SAP-samples/joule-a2a-agent-toolkit","title":"SAP-samples/joule-a2a-agent-toolkit — README, Quick Start","checked":"2026-10-15","quote":"/sap-a2a-agent-toolkit:deploy-agent ./po-assistant"},{"url":"https://github.com/SAP-samples/joule-a2a-agent-toolkit","title":"SAP-samples/joule-a2a-agent-toolkit — README, Getting Started","checked":"2026-10-15","quote":"Start Claude Code with the toolkit plugin, then log in to CF and Joule:"}]},{"ref":"artifact:sap-samples-html5-applications-migration-skills-for-sap-btp","role":"migrates locally, and undeploys through the Cloud Foundry command line","state":"conditional","description":"The 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.","sources":[{"url":"https://github.com/SAP-samples/html5-applications-migration-skills-for-sap-btp","title":"SAP-samples/html5-applications-migration-skills-for-sap-btp — README, Download and Installation","checked":"2026-10-15","quote":"**No MCP servers or network access required.** The plugin operates entirely on local files."},{"url":"https://github.com/SAP-samples/html5-applications-migration-skills-for-sap-btp","title":"SAP-samples/html5-applications-migration-skills-for-sap-btp — README, the cleanup skill","checked":"2026-10-15","quote":"Undeploys a deployed appFront app from Cloud Foundry (optionally deleting service instances and keys) and removes the local output folder."},{"url":"https://github.com/SAP-samples/html5-applications-migration-skills-for-sap-btp","title":"SAP-samples/html5-applications-migration-skills-for-sap-btp — README, Requirements","checked":"2026-10-15","quote":"**CF CLI** — logged in (`cf login`) and targeted (`cf target -o <org> -s <space>`) before deploying"},{"url":"https://github.com/SAP-samples/html5-applications-migration-skills-for-sap-btp","title":"SAP-samples/html5-applications-migration-skills-for-sap-btp — README, Requirements","checked":"2026-10-15","quote":"**SAP BTP subaccount** with Application Frontend service entitlement and Cloud Foundry environment enabled (org and space created)"}]},{"ref":"artifact:cch-engineering-sap-cloud-integration-pipeline-concept-skill","role":"none for this outcome, by its own scope","state":"explicitly-unsupported","description":"Its 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.","sources":[{"url":"https://github.com/cch-engineering/sap-cloud-integration-pipeline-concept-skill","title":"SAP Cloud Integration Pipeline Assistant — README, Scope","checked":"2026-10-15","quote":"The skill provides implementation assistance, Partner Directory guidance, XSLT/Groovy examples, architecture decisions, and troubleshooting. It does not generate or deploy complete iFlow artifacts."}]},{"ref":"artifact:sap-leanix-ai-plugins","role":"not established","state":"unknown","description":"Its 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."}],"unknowns":["Nothing here was run. Every state rests on the maintainer's own documentation, and no source shows a deployment or a trigger succeeding.","SAP-samples/joule-a2a-agent-toolkit documents its four skills as generating commands and a separate user-invoked command as deploying; whether a skill ever runs a command itself is not established.","SAP-samples/html5-applications-migration-skills-for-sap-btp states both that no network access is required and that its cleanup skill undeploys from Cloud Foundry. Both sentences are recorded as they stand rather than reconciled.","Whether an account carries the entitlements any of these act on is a project fact and was not assessed.","Seventeen further options behind this door were not assessed for this outcome, among them the two broad collections, whose per-skill documentation would have to be read one skill at a time."],"assessed_at":"2026-10-15","drafted_with_ai":true,"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"follow-the-fiori-design-guidelines-with-an-agent","name":"Get an agent to follow the SAP Fiori design guidelines","capability":"capability:agent-guidance","ecosystem":"ui5","flavors":["freestyle","fiori-elements","web-components"],"outcome":"A developer wants the controls, colours and messages an agent writes into a Fiori application to follow SAP's design guidelines, without the guidelines being pasted into the prompt each time.","boundary":"About how the design rules reach the agent and which slice of them it gets. The guidelines themselves are SAP's and stay at experience.sap.com; whether a built screen passes a design review is not something any of these records establishes, and checking what an agent produced against a stated expectation is [agent evals](capability:agent-evals).","origin":"Editorial hypothesis, from the four SAP-published entries behind this door, which carry different slices of one design system and were never read side by side.","contributions":[{"ref":"artifact:sap-fiori-guidelines","role":"the guidelines as reference files, with the recurring answers in the skill itself","state":"documented","description":"The one entry whose subject is the guidelines rather than a framework. Its frontmatter names the cases it applies to, from buttons and tables through object pages and list reports to colours, typography and Joule integration, and the skill answers the recurring questions before any reference file is opened: that the emphasized button is the primary action and there is one per page or dialog, what each semantic colour means, and that an error prevents a task while a warning lets the user proceed. It also states which of SAPUI5, UI5 Web Components and Fiori elements each kind of application calls for, so an agent choosing between them has the skill's own answer.","remaining_work":"Install it with the skills command line. The README names the revision it was built from, v1.145 of May 2026, so a rule that has moved since is the reader's to check against SAP's own page; the skill carries one dated reading rather than a live feed.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-guidelines/SKILL.md","title":"SAP/ai-skills-library — skills/sap-fiori-guidelines/SKILL.md, frontmatter description","checked":"2026-10-15","quote":"SAP Fiori design guidelines for building enterprise applications. Use this skill when designing, building, or reviewing SAP Fiori applications, implementing SAPUI5 or UI5 Web Components, working with SAP enterprise UX patterns, or needing guidance on buttons, forms, tables, object pages, list reports, navigation, messaging, colors, typography, accessibility, AI/Joule integration, or any SAP Fiori UI element."},{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-guidelines/SKILL.md","title":"SAP/ai-skills-library — skills/sap-fiori-guidelines/SKILL.md, button types","checked":"2026-10-15","quote":"Emphasized | Primary action - **one per page/dialog**"},{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-guidelines/SKILL.md","title":"SAP/ai-skills-library — skills/sap-fiori-guidelines/SKILL.md, message types","checked":"2026-10-15","quote":"Error | Prevents task completion, requires user action"},{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-guidelines/SKILL.md","title":"SAP/ai-skills-library — skills/sap-fiori-guidelines/SKILL.md, technology table","checked":"2026-10-15","quote":"SAP Fiori Elements | Metadata-driven apps with OData services"},{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-guidelines/README.md","title":"SAP/ai-skills-library — skills/sap-fiori-guidelines/README.md","checked":"2026-10-15","quote":"Built from SAP Fiori Design Guidelines **v1.145** (May 2026)."}]},{"ref":"artifact:sap-ui-theme-designer-plugins","role":"the design tokens, and which theming parameter a given component reads","state":"documented","description":"Two skills in one plugin. One is about using UI theme designer on BTP; the other answers questions about the SAP Design System and the Fiori design tokens, including parameter inheritance and which theming parameters specific UI components use. That last fact is the one a colour change rests on and the one a control's public API does not state, which is why it sits here rather than in the guidelines skill.","remaining_work":"Install it as a plugin in Claude Code or GitHub Copilot, each with its own command, or through the skills command line. Nothing in it compiles or deploys a theme, and it states no UI5 flavor, so whether its parameter mapping reaches the Web Components library as well as SAPUI5 controls was not established.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/SAP/ui-theme-designer-plugins-for-coding-agents","title":"SAP/ui-theme-designer-plugins-for-coding-agents — README","checked":"2026-10-15","quote":"A collection of plugins for coding agents that provide AI coding assistants with knowledge and tooling for working with UI theme designer and the SAP Design System"},{"url":"https://github.com/SAP/ui-theme-designer-plugins-for-coding-agents","title":"SAP/ui-theme-designer-plugins-for-coding-agents — README, the UI theme designer plugin","checked":"2026-10-15","quote":"Provides practical guidance and conceptual support for using UI Theme Designer on BTP. It also answers questions about the SAP Design System and SAP Fiori design tokens, including which theming parameters are used by specific UI components."},{"url":"https://github.com/SAP/ui-theme-designer-plugins-for-coding-agents/blob/main/plugins/ui-theme-designer/README.md","title":"SAP/ui-theme-designer-plugins-for-coding-agents — plugins/ui-theme-designer/README.md, Installation","checked":"2026-10-15","quote":"claude plugin install ui-theme-designer@claude-plugins-official"}]},{"ref":"artifact:ui5-webcomponents-agent-skills","role":"the accessibility and styling slice, inside the library's own repository","state":"documented","flavors":["web-components"],"description":"Two skills under `skills/` in the components' own repository, so they move when the components do. The accessibility one states what the shadow DOM handles on its own, the ARIA roles, keyboard navigation, screen-reader support and high-contrast themes, and then names the properties and the `InvisibleMessage` API that cover what it does not. That is the part of the design system a guidelines document cannot answer, because it depends on what the component already does.","remaining_work":"Get the two skills in front of an agent. Nothing read in the repository on 2026-10-15 names a client they install into, so how they are loaded is the reader's to work out.","remaining_kinds":["configuration"],"sources":[{"url":"https://raw.githubusercontent.com/UI5/webcomponents/main/skills/accessibility/SKILL.md","title":"UI5/webcomponents — skills/accessibility/SKILL.md, frontmatter description","checked":"2026-10-15","quote":"How to make UI5 Web Components applications accessible. Covers accessibility APIs (accessibleName, accessibleNameRef, accessibleDescription, accessibleRole, accessibilityAttributes), label-input relationships, invisible messaging, keyboard handling, high contrast themes, and screen reader support. Use when the user asks about ARIA attributes, screen readers, keyboard navigation, accessibility properties, or making their app accessible."},{"url":"https://raw.githubusercontent.com/UI5/webcomponents/main/skills/accessibility/SKILL.md","title":"UI5/webcomponents — skills/accessibility/SKILL.md, built-in accessibility","checked":"2026-10-15","quote":"UI5 Web Components have built-in accessibility: ARIA roles, keyboard navigation, screen reader support, and high contrast themes are handled automatically in the shadow DOM."},{"url":"https://raw.githubusercontent.com/UI5/webcomponents/main/skills/accessibility/SKILL.md","title":"UI5/webcomponents — skills/accessibility/SKILL.md, invisible messaging","checked":"2026-10-15","quote":"Use `InvisibleMessage` to announce dynamic content changes to screen readers (e.g., search results count, form validation, live updates)."}]},{"ref":"artifact:secondsky-sap-skills","role":"a collection with a SAPUI5 plugin whose content was not read","state":"unknown","description":"Forty plugins for SAP development, among them one the README lists for SAPUI5 framework development and one for Fiori tools. Whether either carries design-guideline rules was not established: only the plugin list and the install section were read, not the plugin's own skill files. It is listed so a reader who already has it installed can see it was looked at rather than ruled out.","remaining_work":"Read the SAPUI5 plugin's own skill files, and the per-plugin verification ledger entry beside it, which records what each claim was checked against.","sources":[{"url":"https://raw.githubusercontent.com/secondsky/sap-skills/main/README.md","title":"secondsky/sap-skills — README, supported agents","checked":"2026-10-15","quote":"Supported agents are controlled by the upstream skills CLI; current examples include Claude Code, OpenCode, Codex, Cursor, Gemini CLI, GitHub Copilot, and other supported clients:"}]}],"readings":[{"ref":"content:from-zero-to-fiori-building-sap-apps-with-ai-agents","relevance":"A worked account of building Fiori applications from hand-written markdown instruction files, which is the rule-file shape of this outcome rather than any packaged set. It explains what handing an agent the rules buys and shows none of the four entries here."},{"ref":"content:github-copilot-vscode-my-own-sap-development-rules","relevance":"One developer's UI5 rule file beside their CAP one, split narrowly enough that an agent cannot read it two ways. The hand-written alternative to an installed skill, and the thing on offer is the shape of the split rather than the rules."}],"unknowns":["No reading in the corpus shows any of these four sets producing a screen that follows the guidelines; each row rests on what its own documentation states it carries.","Only [sap-fiori-guidelines](artifact:sap-fiori-guidelines) names the guideline revision its content was built from, so for the other three whether what the agent is handed matches the current guidelines is not established.","The design guidelines and the design tokens are published as two skills in two repositories, and whether a rule stated in one disagrees with the other was not checked.","Three of the four state no client they install into, so for those the reader's own assistant decides whether the rules arrive at all, and that was not researched per assistant."],"assessed_at":"2026-10-15","drafted_with_ai":true,"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"get-an-agent-to-write-clean-abap","name":"Get an agent to write ABAP that follows Clean ABAP","capability":"capability:agent-guidance","ecosystem":"abap","flavors":["standard-abap","abap-cloud"],"outcome":"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.","boundary":"About how the conventions reach the agent and in what shape. The conventions themselves are [Clean ABAP](artifact:sap-styleguides-clean-abap) and belong to [clean code](capability:abap-clean-code); running a linter or ATC over the result mechanically is [static analysis](capability:abap-static-analysis). Whether the code a reader gets is actually clean is not something any of these records establishes.","origin":"Editorial hypothesis, from four entries behind this door that carry SAP's own style guide to an agent in three different shapes.","contributions":[{"ref":"artifact:matt1as-claude-abap-skills","role":"the rules read into the session, with a review and a refactor command","state":"documented","description":"The 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.","remaining_kinds":["configuration"],"sources":[{"url":"https://raw.githubusercontent.com/matt1as/claude-abap-skills/main/README.md","title":"matt1as/claude-abap-skills — README, the clean-abap plugin","checked":"2026-10-15","quote":"Universal Clean ABAP rules plus two skills (the rules in `CLAUDE.md` are read by each skill on invocation,"},{"url":"https://raw.githubusercontent.com/matt1as/claude-abap-skills/main/README.md","title":"matt1as/claude-abap-skills — README, no connector","checked":"2026-10-15","quote":"This is **not** an MCP server. There is no system connector code here."}]},{"ref":"artifact:attilaberencsi-sapskills","role":"one installable skill that states when it applies","state":"documented","description":"One of the three skills in the repository, applied when an agent creates, refactors, reviews or explains an ABAP artifact, and the README names SAP's own style guide repository as where it comes from. It installs on its own through the skills command line, so the Clean ABAP rules arrive without the other two skills.","remaining_work":"Run the install. The skill states the situations it applies in and the agent decides to read it; the README names no client the skills install into, so which assistant picks them up is the reader's to establish.","remaining_kinds":["configuration"],"sources":[{"url":"https://raw.githubusercontent.com/attilaberencsi/sapskills/main/README.md","title":"attilaberencsi/sapskills — README, Available Skills","checked":"2026-10-15","quote":"`clean-abap`: Apply Clean ABAP guidance when creating, refactoring, reviewing, or explaining ABAP artifacts."},{"url":"https://raw.githubusercontent.com/attilaberencsi/sapskills/main/README.md","title":"attilaberencsi/sapskills — README, Installation","checked":"2026-10-15","quote":"npx skills add attilaberencsi/sapskills --skill clean-abap"},{"url":"https://github.com/attilaberencsi/sapskills","title":"SAP Skills — README, Sources","checked":"2026-10-09","quote":"Clean ABAP originates from SAP's style guide repository"}]},{"ref":"artifact:coveles-claude-abap-dev","role":"a review workflow that cites each rule and runs a linter beside it","state":"conditional","description":"A sequence of tool calls rather than a rule file: abaplint for the mechanical rules beside a reasoned read for what a linter misses, with each rule cited to the Clean ABAP style guide. The skills find their servers by tool name, so the review runs against whichever ABAP MCP server a person already has configured rather than one this ships.","remaining_work":"Connect the servers. Without system access the workflow has no source to read, and without abaplint the mechanical half of the review does not run.","conditions":["At least one of mcp-abap-adt or vibing-steampunk is connected, which is where the source comes from","An abaplint MCP server exposing LintAbap and FixAbap, or the public abaplint command line, for the lint step"],"flavors":["standard-abap"],"sources":[{"url":"https://raw.githubusercontent.com/CoVeles/claude-abap-dev/main/README.md","title":"CoVeles/claude-abap-dev — README, the abap-review skill","checked":"2026-10-15","quote":"abaplint for mechanical rules + a reasoned read for what linters miss, each rule cited from the Clean ABAP style guide"},{"url":"https://raw.githubusercontent.com/CoVeles/claude-abap-dev/main/README.md","title":"CoVeles/claude-abap-dev — README, Built on","checked":"2026-10-15","quote":"The skills detect the servers by their tool names, so server names in your config don't matter."},{"url":"https://github.com/CoVeles/claude-abap-dev","title":"CoVeles/claude-abap-dev — README, Built on","checked":"2026-10-06","quote":"an abaplint MCP server (tools `LintAbap`, `FixAbap`) — or the public [abaplint CLI](https://github.com/abaplint/abaplint) via `npx @abaplint/cli` | lint + fix previews (abap-review) | optional"}]},{"ref":"artifact:marcellourbani-vscode-abap-remote-fs","role":"a knowledge pack inside the extension that already holds the connection","state":"documented","description":"SAP's coding standards distilled for an agent, shipped as one of seven knowledge packs inside a Visual Studio Code extension and loaded by GitHub Copilot on its own when it applies. The guidance travels with the thing that already reaches the system, so it is not a separate install and nothing has to be wired up for it.","remaining_work":"Install the extension and hold a Copilot subscription. The packs are documented as loading in Copilot; the README does not state that another client reads them, and the extension has to stay open as the connection bridge.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/marcellourbani/vscode_abap_remote_fs","title":"marcellourbani/vscode_abap_remote_fs — README, AI Integration & Chat","checked":"2026-10-15","quote":"AI Skills - Specialized knowledge packs that Copilot loads automatically when relevant:"},{"url":"https://github.com/marcellourbani/vscode_abap_remote_fs","title":"marcellourbani/vscode_abap_remote_fs — README, AI Skills","checked":"2026-10-15","quote":"Clean ABAP - SAP's official coding standards, distilled for AI"}]}],"unknowns":["None of the four names the revision of SAP's style guide its rules were written from, so whether what the agent is handed matches the current Clean ABAP is not established.","No source read on 2026-10-15 shows code produced through any of them passing a Clean ABAP review by a person or an ATC run; each entry rests on what its own documentation says it carries.","Rules read at invocation and a cited review workflow are two different shapes, and whether they lead to the same result on the same code was not established. They are reported side by side, not compared.","SAP publishes the conventions as [Clean ABAP](artifact:sap-styleguides-clean-abap), a document with nothing to install. No SAP-published skill or rules file that hands them to an agent was found behind this door."],"assessed_at":"2026-10-15","drafted_with_ai":true,"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"get-rap-patterns-that-match-the-target-system","name":"Get RAP patterns that match the target system","capability":"capability:agent-guidance","ecosystem":"abap","flavors":["abap-cloud"],"outcome":"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.","boundary":"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](capability:agent-code-access). Whether a generated business object works is not something any of these records establishes.","origin":"Editorial hypothesis, from the one entry behind this door that forks its guidance by deployment target and states why, and the three others that carry RAP guidance without doing so.","contributions":[{"ref":"artifact:weiserman-rap-skills","role":"RAP guidance forked by deployment target, one branch per target","state":"conditional","description":"The 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.","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.","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"],"sources":[{"url":"https://raw.githubusercontent.com/weiserman/rap-skills/main/README.md","title":"weiserman/rap-skills — README","checked":"2026-09-14","quote":"Not all RAP development is the same — the syntax, available APIs, BDEF patterns, and tooling constraints differ significantly between BTP Steampunk, S/4HANA Cloud, and on-premise."},{"url":"https://raw.githubusercontent.com/weiserman/rap-skills/main/README.md","title":"weiserman/rap-skills — README, branch table","checked":"2026-10-15","quote":"| `btp/unmanaged` | BTP ABAP Environment | Unmanaged (BAPI wrappers) | ✅ Available |"},{"url":"https://raw.githubusercontent.com/weiserman/rap-skills/main/README.md","title":"weiserman/rap-skills — README, branch table","checked":"2026-10-15","quote":"| `s4-private/managed` | S/4HANA Cloud Private Ed. | Managed | 🔜 Planned |"},{"url":"https://raw.githubusercontent.com/weiserman/rap-skills/main/README.md","title":"weiserman/rap-skills — README, VSP","checked":"2026-10-15","quote":"VSP (Vibing Steampunk) is the bridge that connects Claude Code to your SAP system."}]},{"ref":"artifact:matt1as-claude-abap-skills","role":"one plugin scoped to the ABAP Cloud development model, rules read on invocation","state":"documented","description":"Rather 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.","remaining_kinds":["configuration"],"sources":[{"url":"https://raw.githubusercontent.com/matt1as/claude-abap-skills/main/README.md","title":"matt1as/claude-abap-skills — README, the abap-cloud-rap plugin","checked":"2026-10-15","quote":"ABAP Cloud / RAP rules plus three skills (rules read on invocation, as above):"},{"url":"https://github.com/matt1as/claude-abap-skills","title":"matt1as/claude-abap-skills — README, targets","checked":"2026-09-13","quote":"- **SAP BTP ABAP Environment** (Steampunk)"}]},{"ref":"artifact:arc-mcp-arc-1-skills","role":"generation skills for the service stack and the behaviour pool","state":"conditional","description":"Two of the twenty-two skills answer this outcome from the generation side: one scaffolds a complete RAP OData service stack from a description, with generation aware of the provider contract, and the other implements determinations and validations in a behaviour pool that already exists, reading the class in a structured way and editing it with the version in mind. Neither states a deployment target of its own.","remaining_work":"Connect the server, since every skill that touches ABAP needs it, and check the generated stack against the target: the provider contract is accounted for in the generation, and which contract applies is a fact about the system.","conditions":["[arc-1](artifact:arc-mcp-arc-1) is connected and configured, which its skills README states is required for every skill that touches ABAP"],"sources":[{"url":"https://raw.githubusercontent.com/arc-mcp/arc-1/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md, generate-rap-service","checked":"2026-10-15","quote":"Creates a complete RAP OData service stack (table, CDS views, BDEF, SRVD, SRVB, class) from a natural language description, with provider-contract-aware service generation."},{"url":"https://raw.githubusercontent.com/arc-mcp/arc-1/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md, generate-rap-logic","checked":"2026-10-15","quote":"Implements determination and validation methods in an existing RAP behavior pool using structured class reads, version-aware edits, and quickfix-aware validation"},{"url":"https://github.com/arc-mcp/arc-1/blob/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md","checked":"2026-09-16","quote":"ARC-1 MCP server connected and configured (SAP system access). Required for every skill that touches ABAP."}]},{"ref":"artifact:likweitan-abap-skills","role":"a rap skill among seventeen, not read in this pass","state":"unknown","description":"The 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."}],"unknowns":["Whether the patterns any of these state are valid on a given system was not tested. Every record rests on what its repository documents.","[rap-skills](artifact:weiserman-rap-skills) is the only entry that forks by target, and three of its five branches are marked planned, so two targets are covered today and the other three are a declared intention.","The `rap` skill in [abap-skills](artifact:likweitan-abap-skills) was not read in this pass.","No SAP-published skill or rules file for RAP was found behind this door. SAP's RAP documentation is the source several of these cite and is not itself packaged for an agent."],"assessed_at":"2026-10-15","drafted_with_ai":true,"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"hand-an-agent-the-btp-diagram-rules","name":"Hand an agent SAP's BTP diagram rules","ecosystem":"btp","outcome":"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.","boundary":"About how the rules reach the agent. What the resulting file is, and what checks it afterwards, is [architecture diagrams](capability:architecture-diagrams) and is assessed there. Whether the architecture the diagram shows is a sound one is a different question that nothing here answers.","capability":"capability:agent-guidance","origin":"curated","assessed_at":"2026-10-23","drafted_with_ai":true,"contributions":[{"ref":"artifact:lemaiwo-btp-drawio-skill","role":"the rules as reference files inside a plugin","state":"documented","description":"A 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.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/lemaiwo/btp-drawio-skill","title":"lemaiwo/btp-drawio-skill — README, What's inside the plugin","checked":"2026-10-15","quote":"- 6 reference files covering Horizon colors/styles, area/nesting rules, connector semantics, the icon catalog, the mxGraph XML schema, and diagram levels"},{"url":"https://github.com/lemaiwo/btp-drawio-skill","title":"lemaiwo/btp-drawio-skill — README, What's inside the plugin","checked":"2026-10-15","quote":"- The **full official SAP BTP shape library** (22 XML files × three sizes + generics + annotation helpers) bundled at `assets/libraries/` — no network needed"},{"url":"https://github.com/lemaiwo/btp-drawio-skill","title":"lemaiwo/btp-drawio-skill — README, Install","checked":"2026-10-15","quote":"In Claude Code or Cowork, add this marketplace and install the plugin:"}]},{"ref":"artifact:marianfoo-btp-drawio-skill","role":"the rules as a portable skill with templates","state":"documented","description":"Bundles 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.","sources":[{"url":"https://github.com/marianfoo/btp-drawio-skill","title":"marianfoo/btp-drawio-skill — README, What you need","checked":"2026-10-15","quote":"- **No API keys, no `npm install`, no MCP server, no cloud calls** — every icon, template, and script is bundled and runs locally."},{"url":"https://github.com/marianfoo/btp-drawio-skill","title":"marianfoo/btp-drawio-skill — README, Other AI coding tools","checked":"2026-10-15","quote":"The skill is **portable** — plain Markdown (`SKILL.md`) plus dependency-free Python scripts — so any agent that can read a project instructions file and run shell commands can drive it."},{"url":"https://github.com/marianfoo/btp-drawio-skill","title":"marianfoo/btp-drawio-skill — README, Other AI coding tools, caveats","checked":"2026-10-15","quote":"unlike Claude, these tools won't *auto-load* the skill — the instruction file wires it in per project; and the agent needs shell access plus **Python 3.8+** to run the scripts."}]},{"ref":"artifact:miyasuta-claude-drawio-btp-diagram","role":"two skills with their own triggers, read at named steps","state":"documented","description":"A 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.","remaining_kinds":["configuration"],"sources":[{"url":"https://raw.githubusercontent.com/miyasuta/drawio-btp-diagram-skills/main/skills/drawio-sap-diagrams/SKILL.md","title":"drawio-btp-diagram-skills — skills/drawio-sap-diagrams/SKILL.md, References","checked":"2026-10-23","quote":"| This SKILL.md (Conventions section) | Design conventions (composition patterns, labels, language) | **Steps 2-3** (Mermaid) |"},{"url":"https://raw.githubusercontent.com/miyasuta/drawio-btp-diagram-skills/main/skills/drawio-sap-diagrams/references/coordinate-passes.md","title":"drawio-btp-diagram-skills — references/coordinate-passes.md, Source of Truth for Styling","checked":"2026-10-23","quote":"- **`references/guidelines.md` = the English summary of SAP's official guidelines = source of truth**"},{"url":"https://github.com/miyasuta/drawio-btp-diagram-skills","title":"miyasuta/drawio-btp-diagram-skills — README, The Two Included Skills","checked":"2026-10-23","quote":"`sap-diagram-review` has its own independent triggers (XML generation complete / screenshot shared), so it can also be called on its own from other workflows."},{"url":"https://github.com/miyasuta/drawio-btp-diagram-skills","title":"miyasuta/drawio-btp-diagram-skills — README, Fork This Repository","checked":"2026-10-23","quote":"This repo is meant to be used as your own copy, not pulled directly from the original — as covered in [How the Skill Grows](#how-the-skill-grows) below, Claude will keep editing and committing to it as you use it. Fork it on GitHub first, then clone your fork."}]},{"ref":"artifact:lofond-drawio-skill-sap","role":"the rules as a Copilot skill with a seven-step routine","state":"documented","description":"Written 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.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/lofonD/SAP-BTP-Architecture-Diagram-Generator","title":"lofonD/SAP-BTP-Architecture-Diagram-Generator — README","checked":"2026-10-15","quote":"A GitHub Copilot agent skill that generates production-quality SAP Business Technology Platform (BTP) solution diagrams following the official SAP BTP Solution Diagram Design Guideline (Horizon theme)."},{"url":"https://github.com/lofonD/SAP-BTP-Architecture-Diagram-Generator","title":"lofonD/SAP-BTP-Architecture-Diagram-Generator — README, Quick Start, Clone","checked":"2026-10-15","quote":"Clone this repository and place `skills/drawio-skill-sap` in an Agent Skills location recognized by your Copilot environment, such as `.github/skills/drawio-skill-sap` in the repository where you want to use it."},{"url":"https://github.com/lofonD/SAP-BTP-Architecture-Diagram-Generator/blob/main/skills/drawio-skill-sap/SKILL.md","title":"lofonD/SAP-BTP-Architecture-Diagram-Generator — skills/drawio-skill-sap/SKILL.md, icon rule","checked":"2026-10-09","quote":"Every persona and every SAP system/service/product in a diagram MUST render as a real SAP icon or product logo"}]},{"ref":"artifact:etosin-arc-draw","role":"the rules pushed to the client on connect","state":"documented","description":"The 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.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/etosin/arc-draw","title":"ARC-DRAW — README","checked":"2026-10-15","quote":"The SAP BTP Solution Diagram guideline distilled into a drawing *constitution*, sent to your MCP client the moment it connects"},{"url":"https://github.com/etosin/arc-draw","title":"ARC-DRAW — README, the two tools","checked":"2026-09-28","quote":"Two tools the agent can call by itself: `get-sap-examples` (canonical patterns with ground-truth styles) and `get-sap-guideline` (specific rules by topic: areas, connectors, icons, numbering…)."},{"url":"https://github.com/etosin/arc-draw","title":"ARC-DRAW — README, Roadmap","checked":"2026-10-15","quote":"[ ] Diagram linter: check an existing `.drawio` file against the SAP guideline"}]}],"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"keep-an-agent-inside-clean-core-in-abap","name":"Keep an agent's ABAP inside clean core","ecosystem":"abap","outcome":"A developer wants the agent to stay inside what the system allows — released APIs, and knowing which clean core level an object sits at — whether it is writing new code for a cloud system or auditing custom code that already exists in a classic one.","boundary":"About the rules and the audit procedure an agent is handed. Which objects SAP has actually released is SAP's information and is read at the time of the audit, usually from a documentation server; running the ATC check itself is [static analysis](capability:abap-static-analysis). Whether an extension would pass an SAP review is not something any of these records establishes.","capability":"capability:agent-guidance","origin":"curated","assessed_at":"2026-10-17","drafted_with_ai":true,"contributions":[{"ref":"artifact:matt1as-claude-abap-skills","role":"ABAP Cloud rules read before the code is written, plus an audit command","state":"documented","description":"The abap-cloud-rap plugin carries ABAP Cloud and RAP rules read when a skill is invoked, among them the released-API surface and the allowed `@AbapCatalog` annotations, and ships a command that audits objects for clean core compliance.","remaining_work":"Install the plugin. The rules apply with nothing connected, on source a person pastes in; the audit command needs a server to read the objects it is auditing, and the repository ships no connector of its own.","remaining_kinds":["configuration"],"flavors":["abap-cloud"],"sources":[{"url":"https://raw.githubusercontent.com/matt1as/claude-abap-skills/main/README.md","title":"matt1as/claude-abap-skills — README, the abap-cloud-rap plugin","checked":"2026-10-15","quote":"ABAP Cloud / RAP rules plus three skills (rules read on invocation, as above):"},{"url":"https://raw.githubusercontent.com/matt1as/claude-abap-skills/main/README.md","title":"matt1as/claude-abap-skills — README, clean-core-check","checked":"2026-10-15","quote":"- **`/abap-cloud-rap:clean-core-check`** — audit objects for clean core compliance"}]},{"ref":"artifact:likweitan-abap-skills","role":"the level concept itself, written down","state":"documented","description":"The one place in the corpus that writes SAP's clean core level concept down in full: levels A to D, and which authorisation object decides whether a developer may create Standard ABAP objects at all rather than only ABAP for Cloud Development. It is also the one place the repository states which development model its seventeen skills answer against.","remaining_work":"Install the skill. It states what the levels mean; which level a given object sits at is read from SAP's released-objects information, which this does not carry.","remaining_kinds":["configuration"],"flavors":["abap-cloud"],"sources":[{"url":"https://github.com/likweitan/abap-skills/blob/main/skills/abap-cloud/SKILL.md","title":"likweitan/abap-skills — skills/abap-cloud/SKILL.md, frontmatter description","checked":"2026-10-09","quote":"Help with ABAP Cloud development and the clean core level concept (Levels A, B, C, D)"},{"url":"https://github.com/likweitan/abap-skills/blob/main/skills/abap-cloud/SKILL.md","title":"likweitan/abap-skills — skills/abap-cloud/SKILL.md, clean core levels","checked":"2026-10-09","quote":"Authorization object `S_ABPLNGVS` controls whether a developer may create objects in Standard ABAP or only in ABAP for Cloud Development."}]},{"ref":"artifact:coveles-claude-abap-dev","role":"an audit of code that already exists, against SAP's released-objects list","state":"conditional","description":"The clean-core-check workflow reads existing code and reports which SAP objects it uses, the clean core level of each for the system type, and SAP's named successors. The released-objects list it compares against comes from a documentation server rather than from the skill, and the repository's guardrail is that a finding it cannot read is reported as unknown rather than as fine.","remaining_work":"Connect the two servers, and read the report: the audit names the objects and their levels, and replacing a classic call with its released successor is the developer's work.","conditions":["[mcp-sap-docs](artifact:marianfoo-mcp-sap-docs) is connected, since SAP's released-objects list comes from it","At least one of mcp-abap-adt or vibing-steampunk is connected for access to the code being audited"],"flavors":["standard-abap"],"sources":[{"url":"https://github.com/CoVeles/claude-abap-dev","title":"CoVeles/claude-abap-dev — README, Built on","checked":"2026-10-06","quote":"SAP's released-objects list (clean-core-check), style guide and docs | for clean-core-check"},{"url":"https://raw.githubusercontent.com/CoVeles/claude-abap-dev/main/README.md","title":"CoVeles/claude-abap-dev — README, guardrails","checked":"2026-10-15","quote":"**Nothing invented** — findings, results and release states come from a tool or a document read in the session; SAP facts are cited; \"not found\" is reported as unknown, not as fine."}]},{"ref":"artifact:arc-mcp-arc-1-skills","role":"a package-wide audit that buckets every custom object by level","state":"conditional","description":"One of the twenty-two skills shipped in [arc-1](artifact:arc-mcp-arc-1)'s own skills directory: it takes a package of custom code and sorts every Z or Y object into the clean core levels, using a documentation server for the classification and ATC for the findings. The unit of work is a package rather than an object, which is the shape a cloudification survey takes.","remaining_work":"Connect the servers and work through the buckets. The skill produces the classification; deciding what to do with each object, and the transport that carries the change, stays with the developer.","conditions":["[arc-1](artifact:arc-mcp-arc-1) is connected and configured, which its skills README states is required for every skill that touches ABAP","[mcp-sap-docs](artifact:marianfoo-mcp-sap-docs) is connected, which the audit uses for the level classification"],"sources":[{"url":"https://raw.githubusercontent.com/arc-mcp/arc-1/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md, sap-clean-core-atc","checked":"2026-10-15","quote":"Audits a package of custom code and buckets every Z/Y object into Clean Core Levels A–D using mcp-sap-docs + ATC"},{"url":"https://github.com/arc-mcp/arc-1/blob/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md","checked":"2026-09-16","quote":"ARC-1 MCP server connected and configured (SAP system access). Required for every skill that touches ABAP."}]},{"ref":"artifact:grknylmz-sap-ai-dev-toolkit","role":"one skill of fourteen, on released extensibility and where an extension should sit","state":"documented","description":"A skill installed beside the server the package generates, covering clean core, released extensibility and side-by-side extension design with a risk classification. It answers the design question — whether the extension belongs in the system at all — rather than auditing objects one at a time.","remaining_work":"Run the installer and pick the assistants the skills install into. The skill states the design rules; the server installed beside it is what reads the system, and transport release is deliberately left outside the proxied surface.","remaining_kinds":["configuration"],"sources":[{"url":"https://raw.githubusercontent.com/grknylmz/sap-ai-dev-toolkit/main/README.md","title":"grknylmz/sap-ai-dev-toolkit — README, skills table","checked":"2026-10-06","quote":"| 🧱 | `clean-core-extensibility` | Clean Core, released extensibility, and side-by-side extension design with risk classification |"},{"url":"https://raw.githubusercontent.com/grknylmz/sap-ai-dev-toolkit/main/README.md","title":"grknylmz/sap-ai-dev-toolkit — README, skills","checked":"2026-10-06","quote":"All 14 skills use the portable `SKILL.md` format and are installed verbatim."}]},{"ref":"artifact:sap-abap-atc-cr-cv-s4hc","role":"the released-objects list itself, at its source, in files an agent can fetch","state":"documented","description":"The information the records above read, from SAP rather than from a mirror: the list of released APIs of SAP Cloud ERP, and the successors specified for the objects that are not released, as one JSON file per target product. A pilot publishes the same content in the TOON format under the README's own 'LLM Support for SAP APIs' heading, which takes the released-API file for SAP Cloud ERP Private from 3,659,440 to 2,989,644 tokens.","remaining_work":"Narrow the file before it reaches a prompt: it carries the whole catalogue, and nothing in the repository picks out the objects a task is about. [ROSA](artifact:clementringot-rosa) serves this repository over MCP and over REST, and the audits above read the list through a documentation server.","flavors":["standard-abap","abap-cloud"],"sources":[{"url":"https://github.com/sap/abap-atc-cr-cv-s4hc","title":"SAP/abap-atc-cr-cv-s4hc — README","checked":"2026-10-17","quote":"The repository contains the list of released APIs of SAP Cloud ERP. In addition also the objects that are not released are contained with the specification of successor objects."},{"url":"https://github.com/sap/abap-atc-cr-cv-s4hc","title":"SAP/abap-atc-cr-cv-s4hc — README, LLM Support for SAP APIs","checked":"2026-10-17","quote":"Released API in [objectReleaseInfo_PCELatest.toon](https://github.com/SAP/abap-atc-cr-cv-s4hc/blob/main/src/objectReleaseInfo_PCELatest.toon) going down from 3659440 to 2989644 tokens."}]}],"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"keep-the-sap-knowledge-an-agent-follows-current","name":"Keep the SAP knowledge an agent follows current","capability":"capability:agent-guidance","ecosystem":"btp","outcome":"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.","boundary":"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](capability:agent-evals).","origin":"Editorial hypothesis, from the two entries behind this door that state a currency mechanism and the bundled reference sets sitting beside them.","contributions":[{"ref":"artifact:sap-samples-sap-devs-cli","role":"writes current SAP context into the configured tool, with a sync command","state":"documented","description":"A 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.","sources":[{"url":"https://github.com/SAP-samples/sap-devs-cli","title":"SAP-samples/sap-devs-cli — README, quick start","checked":"2026-10-15","quote":"# Inject SAP context into your AI tools"},{"url":"https://github.com/SAP-samples/sap-devs-cli","title":"SAP-samples/sap-devs-cli — README, quick start","checked":"2026-10-15","quote":"# Keep content current"},{"url":"https://github.com/SAP-samples/sap-devs-cli","title":"SAP-samples/sap-devs-cli — README","checked":"2026-09-13","quote":"`sap-devs` injects up-to-date SAP developer knowledge into your AI coding tools, wires SAP MCP servers, and keeps content current automatically."}]},{"ref":"artifact:sap-tutorials-content","role":"an endpoint map, so the content is read at the time of the call","state":"documented","description":"The 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.","sources":[{"url":"https://github.com/sap-tutorials/tutorials-ims/blob/main/skills/sap-tutorials-content/SKILL.md","title":"sap-tutorials/tutorials-ims — skills/sap-tutorials-content/SKILL.md, frontmatter description","checked":"2026-10-15","quote":"Read SAP developer tutorial content from the public developers.sap.com API — catalog, navigation, tutorial HTML/JSON, and full-text search."},{"url":"https://github.com/sap-tutorials/tutorials-ims/blob/main/skills/sap-tutorials-content/SKILL.md","title":"sap-tutorials/tutorials-ims — skills/sap-tutorials-content/SKILL.md, read-only access","checked":"2026-10-15","quote":"Everything here is **anonymous and read-only** — no login, no token, no API key."},{"url":"https://github.com/sap-tutorials/tutorials-ims/blob/main/skills/sap-tutorials-content/SKILL.md","title":"sap-tutorials/tutorials-ims — skills/sap-tutorials-content/SKILL.md, read-only access","checked":"2026-10-15","quote":"Endpoints verified reachable and anonymous as of 2026-08-18."},{"url":"https://github.com/sap-tutorials/tutorials-ims/blob/main/skills/sap-tutorials-content/SKILL.md","title":"sap-tutorials/tutorials-ims — skills/sap-tutorials-content/SKILL.md, caching","checked":"2026-10-15","quote":"Responses set `ETag` / `Cache-Control`; honor them and avoid hammering — this is a shared public service."}]},{"ref":"artifact:marianfoo-btp-drawio-skill","role":"the bundled kind, where the question is open","state":"unknown","description":"Stands 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.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/marianfoo/btp-drawio-skill","title":"marianfoo/btp-drawio-skill — README, What you need","checked":"2026-10-15","quote":"- **No API keys, no `npm install`, no MCP server, no cloud calls** — every icon, template, and script is bundled and runs locally."}]}],"unknowns":["The sync command's cadence is not documented in what was read, so \"current\" is as current as the last run.","What the knowledge packs sap-devs injects contain, and which SAP pages they are built from, was not established: the README describes the mechanism and not the corpus.","The same open question as the bundled contribution applies to the other bundled sets behind this door, which were not assessed here: none read in this pass dates the SAP material it carries.","A skill that hands an agent the paths to SAP's content is a different thing from one that hands it the content, and whether a reader wants the first is a judgement this record does not make for them."],"assessed_at":"2026-10-15","drafted_with_ai":true,"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"make-a-fiori-application-callable-by-joule","name":"Make a Fiori application's own actions callable by Joule","capability":"capability:agent-guidance","ecosystem":"ui5","outcome":"A developer wants the things their UI5 or Fiori application can already do, such as reading what is displayed, applying a filter, navigating or pressing a button, exposed as actions an assistant may call, without working out the bridge and the descriptor shapes from scratch.","boundary":"About the packaged procedure and the files it writes. Deploying the capability descriptor to a [SAP Joule](artifact:sap-joule) tenant and confirming the actions are reachable are outside it and the skill says so; what the application does once an assistant calls in is the application's own behaviour.","origin":"Editorial hypothesis, from the one entry behind this door that answers it, which is also the door's only independent provider and the reason its coverage state changed on 2026-10-15.","contributions":[{"ref":"artifact:i562693-vkn-scaffold-fiori-ai-bridge","role":"the four-step procedure, and the bridge and descriptors it generates","state":"documented","description":"It asks three questions before it reads any code, whether the target is an application or a library control, which consumer is wanted, and whether tools should be semantic or one per control. Then it reads the manifest, Component.js, the controllers, the views and the models, puts the grouped candidates back for confirmation, and writes the files only after the developer signs off on the list. It carries the runtime limits as rules rather than as notes: a `{ status, content }` return with the content always a string, fifteen seconds an action, ten kilobytes of response, a thousand characters of scenario description, and a `com.sap.<namespace>.<ActionName>.v1` name matching in the JavaScript and the YAML.","remaining_work":"Deploy the capability descriptor to the Joule tenant through the command line, which the skill states is not its step, and verify the actions are reachable from there. The repository read on 2026-10-15 names no client the skill installs into, so loading it is the reader's to work out.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/I562693-VKN/Skill-Hub/blob/main/skills/Scaffold-fiori-ai-bridge/SKILL.md","title":"I562693-VKN/Skill-Hub — skills/Scaffold-fiori-ai-bridge/SKILL.md, purpose","checked":"2026-10-15","quote":"Make a UI5 or Fiori app / library control AI-callable. Generates the JS bridge and all YAML files needed for Joule Frontend Actions"},{"url":"https://github.com/I562693-VKN/Skill-Hub/blob/main/skills/Scaffold-fiori-ai-bridge/SKILL.md","title":"I562693-VKN/Skill-Hub — skills/Scaffold-fiori-ai-bridge/SKILL.md, naming constraint","checked":"2026-10-15","quote":"com.sap.<namespace>.<ActionName>.v1"},{"url":"https://github.com/I562693-VKN/Skill-Hub/blob/main/skills/Scaffold-fiori-ai-bridge/SKILL.md","title":"I562693-VKN/Skill-Hub — skills/Scaffold-fiori-ai-bridge/SKILL.md, what is left to the developer","checked":"2026-10-15","quote":"the capability YAML must be deployed to the Joule tenant via the CLI."},{"url":"https://github.com/I562693-VKN/Skill-Hub","title":"I562693-VKN/Skill-Hub — repository description","checked":"2026-10-15","quote":"Collection of dev , productivity skills for claude, joule, Ui5"}]}],"unknowns":["One entry answers this outcome and no SAP-published equivalent is in the corpus, which may be absence of evidence rather than evidence of absence.","No reading in the corpus shows a generated bridge answering a call from Joule or from a browser.","WebMCP is named as the second consumer and a second bridge file is generated for it; whether that half works in a browser that exposes tools was not established.","Where the runtime limits the skill states come from was not traced to SAP's own documentation in this pass, so they are reported as the skill's statement of them.","The repository names no client the skill installs into, so which assistants read it is not established."],"assessed_at":"2026-10-15","drafted_with_ai":true,"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"modernise-a-legacy-ui5-application-with-an-agent","name":"Modernise a legacy UI5 application with an agent","capability":"capability:agent-guidance","ecosystem":"ui5","flavors":["freestyle","fiori-elements"],"outcome":"A developer wants an agent to take an existing UI5 application off deprecated APIs and legacy patterns, following a written procedure rather than whatever the model remembers about the framework.","boundary":"About the packaged procedure the agent follows. Reading the project, running the UI5 linter and validating the manifest are [agent access to your code](capability:agent-code-access) and come from a server beside the skills; whether the modernised application still works is the developer's to verify, and neither route here claims otherwise.","origin":"Editorial hypothesis, from the one SAP-published plugin behind this door written for the job and an independent skill set that answers the same outcome from the ABAP door.","paths":[{"key":"ui5-plugin","name":"The UI5 team's modernization plugin with the UI5 MCP server beside it","sources":[{"url":"https://github.com/UI5/plugins-coding-agents/blob/main/plugins/ui5-modernization/README.md","title":"UI5/plugins-coding-agents — plugins/ui5-modernization/README.md, skills-only installation","checked":"2026-10-15","quote":"You need to install the UI5 MCP server manually when installing the skills only."}]},{"key":"arc-1","name":"ARC-1's UI5 skills over the UI5 server and a browser","sources":[{"url":"https://github.com/arc-mcp/arc-1/blob/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md, prerequisites","checked":"2026-10-15","quote":"3. **SAPUI5 MCP server** (`@ui5/mcp-server`). Required for `modernize-ui5-app` and `convert-ui5-to-fiori-elements` — provides the authoritative TypeScript conversion guidelines, project scaffolding, ui5-linter, and manifest validation."}]}],"contributions":[{"ref":"artifact:ui5-plugins-coding-agents","role":"the modernisation procedure, as one of three plugins","state":"conditional","paths":["ui5-plugin"],"description":"UI5 Modernization is one of three plugins in the repository, published beside the general development plugin and the TypeScript conversion one, so a project being modernised does not load the other two. The repository's own line for it is an autonomous multi-phase workflow that replaces deprecated APIs and removes legacy patterns, and its own README calls it a toolkit for modernising SAPUI5 and OpenUI5 applications. It installs as a plugin into Claude Code or GitHub Copilot, with a command for each.","remaining_work":"Point it at a branch rather than at main, since the workflow is described as autonomous and multi-phase. What it reads of the project, the linter it runs and the manifest check come from [@ui5/mcp-server](artifact:ui5-mcp-server), and reviewing the result is a person's step.","conditions":["[@ui5/mcp-server](artifact:ui5-mcp-server) is present; the plugin's README states it has to be installed by hand when the skills are installed on their own"],"sources":[{"url":"https://github.com/UI5/plugins-coding-agents","title":"UI5/plugins-coding-agents — README, the UI5 Modernization plugin","checked":"2026-10-15","quote":"Autonomous, multi-phase workflow and specialized skills for modernizing UI5 projects by replacing deprecated APIs and eliminating legacy patterns."},{"url":"https://github.com/UI5/plugins-coding-agents/blob/main/plugins/ui5-modernization/README.md","title":"UI5/plugins-coding-agents — plugins/ui5-modernization/README.md","checked":"2026-10-15","quote":"A comprehensive plugin providing a complete toolkit for modernizing SAPUI5/OpenUI5 applications."},{"url":"https://github.com/UI5/plugins-coding-agents/blob/main/plugins/ui5-modernization/README.md","title":"UI5/plugins-coding-agents — plugins/ui5-modernization/README.md, Installation","checked":"2026-10-15","quote":"claude plugin install ui5-modernization@claude-plugins-official"},{"url":"https://github.com/UI5/plugins-coding-agents/blob/main/plugins/ui5-modernization/README.md","title":"UI5/plugins-coding-agents — plugins/ui5-modernization/README.md, skills-only installation","checked":"2026-10-15","quote":"You need to install the UI5 MCP server manually when installing the skills only."}]},{"ref":"artifact:ui5-mcp-server","role":"the project read, the conversion guidelines and the linter both routes send the mechanical half to","state":"documented","paths":["ui5-plugin","arc-1"],"description":"SAP's own MCP server for UI5 development, and the part of this outcome that is not packaged knowledge. Its tool list names the TypeScript conversion guidelines, the UI5 best practices, the `@ui5/linter` integration and the read of a project's own metadata and configuration, which is what tells an agent what the application in front of it targets. Both routes name it, which is why it appears here rather than only on its own capability.","remaining_work":"Run it beside the agent. It reads a UI5 project and the framework's own documentation and not the backend behind the application, so a question about the service is answered somewhere else.","sources":[{"url":"https://github.com/UI5/mcp-server","title":"UI5/mcp-server — README","checked":"2026-10-15","quote":"A [Model Context Protocol](https://modelcontextprotocol.io/) server for UI5 application development."},{"url":"https://github.com/UI5/mcp-server","title":"UI5/mcp-server — README, get_typescript_conversion_guidelines","checked":"2026-10-15","quote":"Provides guidelines for converting UI5 applications and controls from JavaScript to TypeScript."},{"url":"https://github.com/UI5/mcp-server","title":"UI5/mcp-server — README, run_ui5_linter","checked":"2026-10-15","quote":"Integrates with [`@ui5/linter`](https://github.com/UI5/linter) to analyze and report issues in the UI5 code."},{"url":"https://github.com/UI5/mcp-server","title":"UI5/mcp-server — README, get_project_info","checked":"2026-10-15","quote":"Extracts metadata and configuration from a UI5 project."}]},{"ref":"artifact:arc-mcp-arc-1-skills","role":"the same outcome answered from the ABAP door, with a named target version","state":"conditional","paths":["arc-1"],"flavors":["freestyle"],"description":"One of twenty-two skills shipped in [arc-1](artifact:arc-mcp-arc-1)'s own skills directory. Where the UI5 plugin states the kind of change it makes, this states the end state: a legacy freestyle JavaScript application with a synchronous bootstrap and `jQuery.sap.*` calls becomes a UI5 TypeScript application on 1.147 using `sap.f.FlexibleColumnLayout`, typed event handlers, ES modules and the Horizon theme, with five traps written down in front. A second skill in the same set generates a Fiori elements V4 list report and object page instead.","remaining_work":"Connect the servers the set names. It sits behind the ABAP door and states no claim to serve this one, so a reader standing at the UI5 door does not meet it among the options at all.","conditions":["[@ui5/mcp-server](artifact:ui5-mcp-server) is connected, which the skills README states is required for this skill","A browser MCP is connected for the final render check, which the README states an HTTP 200 does not cover"],"sources":[{"url":"https://github.com/arc-mcp/arc-1/blob/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md, modernize-ui5-app","checked":"2026-10-15","quote":"Converts a legacy UI5 freestyle JavaScript app (sync bootstrap, jQuery.sap.*, ES5, sap_belize) into a modern UI5 TypeScript app on UI5 1.147 with `sap.f.FlexibleColumnLayout`, typed event handlers, ES modules, `BaseController`, sap_horizon"},{"url":"https://github.com/arc-mcp/arc-1/blob/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md, prerequisites","checked":"2026-10-15","quote":"3. **SAPUI5 MCP server** (`@ui5/mcp-server`). Required for `modernize-ui5-app` and `convert-ui5-to-fiori-elements` — provides the authoritative TypeScript conversion guidelines, project scaffolding, ui5-linter, and manifest validation."},{"url":"https://github.com/arc-mcp/arc-1/blob/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md, prerequisites","checked":"2026-10-15","quote":"5. **A browser MCP** — `Claude_in_Chrome` or `Claude_Preview`. Used by `modernize-ui5-app` for the final render verification step (HTTP 200 alone is not a sufficient acceptance gate — see the \"blank page\" traps in the skill)."},{"url":"https://github.com/arc-mcp/arc-1/blob/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md, convert-ui5-to-fiori-elements","checked":"2026-10-15","quote":"4. **Fiori MCP server** (`@sap-ux/fiori-mcp-server`). Required for `convert-ui5-to-fiori-elements` only — provides the LROP scaffold + annotation-aware page-template configuration."}]}],"unknowns":["No reading in the corpus shows either route modernising a real application; both rows rest on what their own documentation states.","Neither route states which framework versions it modernises from. The arc-1 skill names 1.147 as its target, and the modernization plugin's README states framework-version requirements per step that were not read in full here.","Whether the two routes produce the same result on the same project was not established. They are reported side by side, not compared.","[ARC-1 Skills](artifact:arc-mcp-arc-1-skills) states no claim to serve the UI5 door, so whether it should appear among this door's options is a placement question this record does not settle.","The modernization plugin is described as autonomous across a codebase, and nothing read states what it does when a phase fails part-way."],"assessed_at":"2026-10-15","drafted_with_ai":true,"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"restyle-a-ui5-web-component-without-breaking-on-upgrade","name":"Restyle a UI5 Web Component without breaking on the next release","capability":"capability:agent-guidance","ecosystem":"ui5","flavors":["web-components"],"outcome":"A developer wants an agent to restyle a UI5 Web Component through the surfaces the library documents, rather than reaching into its shadow DOM in a way that stops working when the component changes.","boundary":"About the styling rules the agent is handed. Building and publishing a theme is UI theme designer's own job, and whether a particular override survives a given release is between the developer and the component's changelog. Nothing here checks a stylesheet.","origin":"Editorial hypothesis, from the one skill the component library ships for this and the theming plugin that answers the parameter half from the other side of the door.","contributions":[{"ref":"artifact:ui5-webcomponents-agent-skills","role":"the sanctioned techniques, and the selectors that do not work at all","state":"documented","description":"The styling skill, one of two shipped under `skills/` in the components' own repository. It names four ways in, CSS shadow parts, CSS custom states, CSS variables and tag-level styling, says to use documented shadow parts only, and names the deprecated piercing selectors as not working rather than as discouraged. Living in the library's repository is what ties the guidance to the version of the components it describes.","remaining_work":"Get the skill in front of the agent. Nothing read in the components' repository on 2026-10-15 names a client the two skills install into, so how they are loaded is the reader's to establish.","remaining_kinds":["configuration"],"sources":[{"url":"https://raw.githubusercontent.com/UI5/webcomponents/main/skills/styling/SKILL.md","title":"UI5/webcomponents — skills/styling/SKILL.md, frontmatter description","checked":"2026-10-15","quote":"How to customize and style UI5 Web Components. Covers CSS shadow parts, CSS custom states, CSS variables, and tag-level styling."},{"url":"https://raw.githubusercontent.com/UI5/webcomponents/main/skills/styling/SKILL.md","title":"UI5/webcomponents — skills/styling/SKILL.md, piercing selectors","checked":"2026-10-15","quote":"Don't pierce shadow DOM with deprecated `>>>` or `/deep/` selectors — they don't work."},{"url":"https://raw.githubusercontent.com/UI5/webcomponents/main/skills/styling/SKILL.md","title":"UI5/webcomponents — skills/styling/SKILL.md, documented parts","checked":"2026-10-15","quote":"Only use documented shadow parts."}]},{"ref":"artifact:sap-ui-theme-designer-plugins","role":"which theming parameter a given component actually reads","state":"documented","description":"Its design-tokens skill carries the SAP Design System and the Fiori design tokens, including parameter inheritance and which theming parameters specific UI components use. A CSS variable override is only as good as knowing which variable the component consumes, and that is the fact this plugin states and a component's public API does not.","remaining_work":"Install it as a plugin in Claude Code or GitHub Copilot, each with its own command, or through the skills command line. It states no UI5 flavor of its own, so whether its parameter mapping covers the Web Components library as well as SAPUI5 controls was not established.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/SAP/ui-theme-designer-plugins-for-coding-agents","title":"SAP/ui-theme-designer-plugins-for-coding-agents — README, the UI theme designer plugin","checked":"2026-10-15","quote":"Provides practical guidance and conceptual support for using UI Theme Designer on BTP. It also answers questions about the SAP Design System and SAP Fiori design tokens, including which theming parameters are used by specific UI components."},{"url":"https://github.com/SAP/ui-theme-designer-plugins-for-coding-agents/blob/main/plugins/ui-theme-designer/README.md","title":"SAP/ui-theme-designer-plugins-for-coding-agents — plugins/ui-theme-designer/README.md, the design-tokens skill","checked":"2026-10-15","quote":"Provides information about the SAP Design System and SAP Fiori design tokens, including theme details, parameter inheritance, component consumption, and CSS optimization recommendations"},{"url":"https://github.com/SAP/ui-theme-designer-plugins-for-coding-agents/blob/main/plugins/ui-theme-designer/README.md","title":"SAP/ui-theme-designer-plugins-for-coding-agents — plugins/ui-theme-designer/README.md, Installation","checked":"2026-10-15","quote":"copilot plugin install ui-theme-designer@awesome-copilot"}]},{"ref":"artifact:sap-fiori-guidelines","role":"the colour and typography rules, with its reach into the shadow DOM not established","state":"unknown","description":"It states the Web Components flavor in its own frontmatter and its reference files cover colours and typography, so a reader who has it installed has design rules in the session. What was not established is whether it says anything about applying them from outside a shadow root, which is the part of this outcome that goes wrong. Listed so the entry reads as looked at and not established, rather than as ruled out.","remaining_work":"Read the colours-and-typography reference file and the Web Components passages beside it.","sources":[{"url":"https://github.com/SAP/ai-skills-library/blob/main/skills/sap-fiori-guidelines/SKILL.md","title":"SAP/ai-skills-library — skills/sap-fiori-guidelines/SKILL.md, technology table","checked":"2026-10-15","quote":"UI5 Web Components | Framework-agnostic, React/Vue/Angular integration"}]}],"unknowns":["No reading in the corpus shows a component restyled through these surfaces surviving an upgrade; the record rests on what the library's own skill states about which surfaces are documented.","Whether [the UI theme designer plugin](artifact:sap-ui-theme-designer-plugins)'s parameter mapping covers UI5 Web Components or SAPUI5 controls alone was not established, and it states no flavor either way.","The styling skill names `addCustomCSS` as the last resort for reaching into the shadow root; what the library says about the risk of that route specifically was not read in this pass.","Neither of the two skills in the components' repository names a client it installs into, so whether a given assistant picks them up at all is the reader's to find out."],"assessed_at":"2026-10-15","drafted_with_ai":true,"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"},{"id":"work-on-abap-with-an-agent-and-no-system-connection","name":"Work on ABAP with an agent and no system connection","capability":"capability:agent-guidance","ecosystem":"abap","flavors":["standard-abap","abap-cloud"],"outcome":"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.","boundary":"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](capability:agent-code-access), 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.","origin":"Editorial hypothesis, from the one entry behind this door that states no system is needed, the one that names a fallback for when nothing is connected, and the one whose README makes the server a requirement for every skill that touches ABAP.","needs":[{"key":"system_reach","value":"None needed"}],"contributions":[{"ref":"artifact:alokm3hta-star-abap-offstack-testing","role":"a test harness that runs the existing ABAP Unit tests off the system","state":"documented","description":"The skill sets up a harness and then gets out of the way: the abaplint transpiler and open-abap-core turn serialised ABAP into JavaScript and the repository's own ABAP Unit tests run on Node, locally and in a CI job the scaffold installs. Its README states that nothing requires a provisioned SAP system, which is the plainest answer to this outcome in the corpus.","remaining_work":"The ABAP has to be abapGit-serialised into a Git repository, Node 22 or later available locally and in CI, and the CI has to be GitHub Actions. The agent also makes three judgement calls the README names, and puts them to the developer where it cannot infer them.","sources":[{"url":"https://raw.githubusercontent.com/alokm3hta-star/abap-offstack-testing/main/README.md","title":"abap-offstack-aunit — README","checked":"2026-10-15","quote":"Nothing requires a provisioned SAP system."},{"url":"https://raw.githubusercontent.com/alokm3hta-star/abap-offstack-testing/main/README.md","title":"abap-offstack-aunit — README, scope","checked":"2026-10-15","quote":"Any class calling the database, classic BAPIs, or HTTP is shimmed out and stays an on-stack ATC + ABAP Unit concern."},{"url":"https://github.com/alokm3hta-star/abap-offstack-testing","title":"abap-offstack-aunit — README, Requirements","checked":"2026-10-09","quote":"**Node.js 22+** and **npm** available locally and in CI."}]},{"ref":"artifact:matt1as-claude-abap-skills","role":"rules that fall back to pasted source when nothing is connected","state":"conditional","description":"The 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.","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.","conditions":["The source is pasted into the session, since there is no connector and no server is connected"],"sources":[{"url":"https://raw.githubusercontent.com/matt1as/claude-abap-skills/main/README.md","title":"matt1as/claude-abap-skills — README, with nothing connected","checked":"2026-10-15","quote":"With nothing connected, all five skills still work on pasted source."},{"url":"https://raw.githubusercontent.com/matt1as/claude-abap-skills/main/README.md","title":"matt1as/claude-abap-skills — README, no connector","checked":"2026-10-15","quote":"This is **not** an MCP server. There is no system connector code here."}]},{"ref":"artifact:adam0thman-sap-basis-ops","role":"runbooks that stop at the command sequence on purpose","state":"documented","description":"The guidance is complete without any reach of its own: each skill produces the command sequence for a given system, database and operating system, cited to its source and with the checks to run before and after, and running it is a separate decision that goes through an SSH or shell server the person supplies. The skills bundle no credentials and the repository states they never auto-run a destructive command.","remaining_work":"Read the sequence and run it yourself, or connect the shell server and approve each step. The commands it writes stop systems and delete data, which is why execution is deliberately somebody else's decision.","flavors":["standard-abap"],"sources":[{"url":"https://raw.githubusercontent.com/adam0thman/sap-basis-ops/main/README.md","title":"adam0thman/sap-basis-ops — README, execution","checked":"2026-10-15","quote":"Execution is **opt-in** and happens through an SSH/shell MCP **you** supply at runtime — the skills bundle **no credentials** and never auto-run destructive commands."},{"url":"https://github.com/adam0thman/sap-basis-ops","title":"adam0thman/sap-basis-ops — README","checked":"2026-09-10","quote":"the sysadmin plane that existing SAP skill sets ... don't cover"}]},{"ref":"artifact:arc-mcp-arc-1-skills","role":"skills that state the server is required","state":"explicitly-unsupported","description":"Its own prerequisites rule this outcome out: the server, connected and configured with SAP system access, is listed as required for every skill that touches ABAP. The skill files alone have nothing to act on, and the entry's own warning says the same.","remaining_work":"Nothing short of connecting the server. This is recorded as a stated no rather than a gap: the README answers the question directly.","sources":[{"url":"https://github.com/arc-mcp/arc-1/blob/main/skills/README.md","title":"arc-mcp/arc-1 — skills/README.md, prerequisites","checked":"2026-09-16","quote":"ARC-1 MCP server connected and configured (SAP system access). Required for every skill that touches ABAP."}]},{"ref":"artifact:attilaberencsi-sapskills","role":"three instruction files with nothing that connects","state":"unknown","description":"Three skills that read as instruction files rather than procedures over tools, so nothing in them obviously needs a system. The README states no system prerequisite either way, and one of the three is about working with ADT in Visual Studio Code against a Private Cloud Edition, which does assume a reachable system. Whether the set as a whole is useful with nothing connected is therefore not established.","remaining_work":"Read the three SKILL.md files and record which of them assume a reachable system. Absence of a stated prerequisite is not a statement that none is needed."},{"ref":"artifact:abap2ui5-app-template","role":"a project where the agent setup and the checks it is told to run are both in the repository","state":"documented","description":"`AGENTS.md`, `CLAUDE.md` and the framework's four skills under `.claude/skills/` are the guidance a project made from this template already carries; a permission allowlist lets an autonomous session run the gates without a prompt, and `.mcp.json` registers [the framework's MCP server](artifact:abap2ui5-mcp-server) for Claude Code. The gates themselves need no system: [abaplint](artifact:abaplint-abaplint) resolves [abap2UI5](artifact:abap2ui5-abap2ui5) as a dependency, and `npm run test:unit` runs the starter app's ABAP Unit test in the transpiled abap2UI5 backend, through that server's `abap2ui5-unit`. `--agent-setup` puts the same files into an abap2UI5 project that did not start from the template.","remaining_work":"Starting the app is still a system's job: the framework and the repository are installed with [abapGit](artifact:abapgit-abapgit) and the HTTP handler needs an ICF endpoint. The static checks run offline, while the view render gate needs a Chromium that Playwright installs, and `npm run check:abap2ui5:fast` is the half that runs without one.","remaining_kinds":["configuration"],"sources":[{"url":"https://github.com/abap2ui5/app-template","title":"abap2UI5/app-template — README, What you get","checked":"2026-10-17","quote":"**abaplint** — syntax/style checks with the abap2UI5 framework resolved as\n  a dependency, no SAP system needed"},{"url":"https://github.com/abap2ui5/app-template","title":"abap2UI5/app-template — README, Build with AI","checked":"2026-10-17","quote":"A project made from this template is ready for an AI agent as it stands,\nwith nothing to install for it:"},{"url":"https://github.com/abap2ui5/app-template","title":"abap2UI5/app-template — README, Build with AI, the registered server","checked":"2026-10-17","quote":"**`.mcp.json`** — the abap2UI5 MCP server, registered for Claude Code"},{"url":"https://github.com/abap2ui5/app-template","title":"abap2UI5/app-template — README, Testing an app","checked":"2026-10-17","quote":"or without one: `npm run test:unit` and the `unit` job in\n`check.yml` run it in the transpiled abap2UI5 backend, through the\n[mcp-server](https://github.com/abap2UI5/mcp-server)'s `abap2ui5-unit`"},{"url":"https://github.com/abap2ui5/app-template","title":"abap2UI5/app-template — README, Quick start","checked":"2026-10-17","quote":"Create an ICF endpoint for the framework's HTTP handler (see the"}]},{"ref":"artifact:abap2ui5-mcp-server","role":"the framework's whole development loop as tools, stated to need no system","state":"documented","description":"The framework's own MCP server carries the loop as tools: `validate_view` and `screenshot_view` rebuild the view the ABAP builds and photograph it, `deploy_app` writes the class into a gitignored sandbox and runs [abaplint](artifact:abaplint-abaplint) over it against the framework sources, `build_backend` transpiles the deployed apps to Node, `run_app` boots one headless and answers with the page errors, and `run_unit_tests` runs the app's ABAP Unit tests in the open-abap runtime. Its documentation states that all of that happens on the machine with no SAP system involved, and the same runner is what [the app template](artifact:abap2ui5-app-template)'s offline test job calls. Beside the gates, the knowledge tools read the guide, the client API and the pitfall catalogues out of the repositories' committed files, so for [abap2UI5](artifact:abap2ui5-abap2ui5) the knowledge this record is otherwise about arrives as a tool answer. Nothing else recorded here boots an app.","remaining_work":"The loop is the abap2UI5 one: what `deploy_app` writes is a framework app class, so other ABAP has nothing here to deploy into. A browser is needed for the picture and the headless run, and without a framework checkout the knowledge tools read their files from [GitHub](external:github), so the machine needs a network connection even where it needs no system. The runner names its own limit: a test that passes here passes on the system short of what the open-abap runtime cannot model, and a `PARTIALLY IMPLEMENTED` test double has to implement every method the code under test calls. With `A2UI5_MCP_SYSTEM_URL` set the server's app tools run against a configured system instead, which is the half this record does not assess.","sources":[{"url":"https://github.com/abap2ui5/mcp-server","title":"abap2UI5/mcp-server — repository description","checked":"2026-10-17","quote":"The abap2UI5 MCP server — an agent writes an app, runs it and sees the screenshot, without an SAP system"},{"url":"https://abap2ui5.github.io/docs/advanced/mcp_server.html","title":"abap2UI5 documentation — MCP Server","checked":"2026-10-17","quote":"all on your machine, with no SAP system involved"},{"url":"https://github.com/abap2ui5/mcp-server","title":"abap2UI5/mcp-server — README, system mode","checked":"2026-10-17","quote":"Everything above runs without a system."},{"url":"https://github.com/abap2ui5/mcp-server","title":"abap2UI5/mcp-server — README, Level 0","checked":"2026-10-17","quote":"**Level 0 — no checkout at all.** The knowledge tools (`app_guide`,\n`api_reference`, `pitfalls`, `capabilities`, `examples`, `read_example`,\n`docs_search`, `scaffold_app`, `generation_rules`) read committed files"},{"url":"https://abap2ui5.github.io/docs/advanced/mcp_server.html","title":"abap2UI5 documentation — MCP Server, Level 0","checked":"2026-10-17","quote":"With no checkout there, they read the same files from GitHub, kept for a day in a per-user cache."},{"url":"https://github.com/abap2ui5/mcp-server","title":"abap2UI5/mcp-server — README, the tool table","checked":"2026-10-17","quote":"Write the class + abapGit sidecar (+ test include) into the dev sandbox, then abaplint it"},{"url":"https://abap2ui5.github.io/docs/advanced/mcp_server.html","title":"abap2UI5 documentation — MCP Server, the render gate","checked":"2026-10-17","quote":"screenshot_view additionally needs the linter's render runtime and a browser"},{"url":"https://github.com/abap2ui5/mcp-server","title":"abap2UI5/mcp-server — README, unit tests in CI","checked":"2026-10-17","quote":"What\nthe runner cannot see is what the open-abap runtime cannot model (see\n`pitfalls`, area `abap`); a test that passes here passes on the system short of\nthat, and a `PARTIALLY IMPLEMENTED` test double has to implement every method\nthe code under test calls, because the runtime generates no empty stubs."}]}],"unknowns":["What a review or a test tells you without a system is narrower than with one, and only [abap-offstack-aunit](artifact:alokm3hta-star-abap-offstack-testing) says where the line falls, in the classes it shims out. The others state nothing comparable.","Pasted source is a path [claude-abap-skills](artifact:matt1as-claude-abap-skills) names explicitly; whether the other rule sets behave the same way with nothing connected was not read.","The entries that install a server of their own, [SuperClaude for SAP](artifact:babamba2-superclaude-for-sap) and [sap-ai-dev-toolkit](artifact:grknylmz-sap-ai-dev-toolkit), were not assessed for this outcome. Bringing a server is not the same claim as needing none, and neither was read for what it does with nothing reachable.","How far a green gate off the system carries is stated once, and only for the tests: [the abap2UI5 MCP server](artifact:abap2ui5-mcp-server) says a test that passes in the open-abap runtime passes on the system short of what that runtime cannot model. Nothing comparable is stated for the view gates, and neither abap2UI5 entry was run for this record."],"assessed_at":"2026-10-17","history":[{"date":"2026-10-17","field":"boundary","from":"About whether packaged knowledge is useful with no reach into a system.","to":"the same question, widened to the tooling that stands in for a system, with the off-system half named as what an entry is assessed for here","reason":"[The abap2UI5 app template](artifact:abap2ui5-app-template) and [its MCP server](artifact:abap2ui5-mcp-server) answer this outcome with gates and tools rather than with files, and the server also offers a system mode that belongs to [agent access to your code](capability:agent-code-access). The old sentence would have excluded both, and the record would have said nothing about the entries behind this door that state the outcome most directly."},{"date":"2026-10-17","field":"contributions","from":"five entries, each of them a skill or a rule set","to":"seven, with the abap2UI5 app template and the abap2UI5 MCP server","reason":"Two intake requests reached this record. The template carries the agent setup and gates that run offline; the server carries the loop as tools and states that none of it needs a system. The template's own offline unit job runs through the server's `abap2ui5-unit`, so the two are recorded with that link named rather than as unrelated answers."}],"drafted_with_ai":true,"readings":[],"omitted_contributions":0,"assessment_kind":"documented-contributions"}],"shared_tasks":[],"related_tasks":[],"options":[{"ref":"artifact:patimweb-pi-cap-bestpractices","name":"@patimweb/pi-cap-bestpractices","json":"/artifacts/patimweb-pi-cap-bestpractices.json","ecosystem":"cap","origin_ring":"independent"},{"ref":"artifact:marcellourbani-vscode-abap-remote-fs","name":"ABAP remote filesystem","json":"/artifacts/marcellourbani-vscode-abap-remote-fs.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:alokm3hta-star-abap-offstack-testing","name":"abap-offstack-aunit","json":"/artifacts/alokm3hta-star-abap-offstack-testing.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:likweitan-abap-skills","name":"abap-skills","json":"/artifacts/likweitan-abap-skills.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:abap2ui5-vscode-extension","name":"abap2UI5 for VS Code","json":"/artifacts/abap2ui5-vscode-extension.json","ecosystem":"abap","origin_ring":"community-org"},{"ref":"artifact:sap-aicore-skills","name":"aicore-skills","json":"/artifacts/sap-aicore-skills.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:arc-mcp-arc-1-skills","name":"ARC-1 Skills","json":"/artifacts/arc-mcp-arc-1-skills.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:etosin-arc-draw","name":"ARC-DRAW","json":"/artifacts/etosin-arc-draw.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:lemaiwo-btp-drawio-skill","name":"btp-solution-diagram-generator","json":"/artifacts/lemaiwo-btp-drawio-skill.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:kallolchakraborty-cap-guardian","name":"CAP Guardian","json":"/artifacts/kallolchakraborty-cap-guardian.json","ecosystem":"cap","origin_ring":"independent"},{"ref":"artifact:fermeregali-cap-mtx-scaffold","name":"cap-mtx-scaffold","json":"/artifacts/fermeregali-cap-mtx-scaffold.json","ecosystem":"cap","origin_ring":"independent"},{"ref":"artifact:capire-skills","name":"capire/skills","json":"/artifacts/capire-skills.json","ecosystem":"cap","origin_ring":"sap-official"},{"ref":"artifact:coveles-claude-abap-dev","name":"claude-abap-dev","json":"/artifacts/coveles-claude-abap-dev.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:matt1as-claude-abap-skills","name":"claude-abap-skills","json":"/artifacts/matt1as-claude-abap-skills.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:silvius1996-claude-sap-kit","name":"claude-sap-kit","json":"/artifacts/silvius1996-claude-sap-kit.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:dankromp-skilloverflow","name":"DanKromp/skillOverflow","json":"/artifacts/dankromp-skilloverflow.json","ecosystem":"cap","origin_ring":"independent"},{"ref":"artifact:miyasuta-claude-drawio-btp-diagram","name":"drawio-btp-diagram-skills","json":"/artifacts/miyasuta-claude-drawio-btp-diagram.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:lofond-drawio-skill-sap","name":"drawio-skill-sap","json":"/artifacts/lofond-drawio-skill-sap.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:yannick-thirion-klystron","name":"Klystron","json":"/artifacts/yannick-thirion-klystron.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:robertriedel-pod2-config-skill","name":"pod2-config","json":"/artifacts/robertriedel-pod2-config-skill.json","ecosystem":"digital-manufacturing","origin_ring":"independent"},{"ref":"artifact:weiserman-rap-skills","name":"rap-skills","json":"/artifacts/weiserman-rap-skills.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:mariodefelipe-datasphere-plugin","name":"SAP Datasphere Plugin for Claude","json":"/artifacts/mariodefelipe-datasphere-plugin.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:sap-developers-mcp","name":"SAP Developers MCP","json":"/artifacts/sap-developers-mcp.json","ecosystem":"umbrella","origin_ring":"sap-official"},{"ref":"artifact:mfigueir-sap-power","name":"SAP Power for Kiro","json":"/artifacts/mfigueir-sap-power.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:grknylmz-sap-ai-dev-toolkit","name":"sap-ai-dev-toolkit","json":"/artifacts/grknylmz-sap-ai-dev-toolkit.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:marianfoo-btp-drawio-skill","name":"sap-architecture","json":"/artifacts/marianfoo-btp-drawio-skill.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:adam0thman-sap-basis-ops","name":"sap-basis-ops","json":"/artifacts/adam0thman-sap-basis-ops.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:cch-engineering-sap-cloud-integration-pipeline-concept-skill","name":"sap-cloud-integration-pipeline-assistant","json":"/artifacts/cch-engineering-sap-cloud-integration-pipeline-concept-skill.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:emenowicz-sap-commerce-skill","name":"sap-commerce-skill","json":"/artifacts/emenowicz-sap-commerce-skill.json","ecosystem":"commerce","origin_ring":"independent"},{"ref":"artifact:abinayaaa-sap-cx-developer-companion","name":"sap-cx-developer-companion","json":"/artifacts/abinayaaa-sap-cx-developer-companion.json","ecosystem":"commerce","origin_ring":"independent"},{"ref":"artifact:blumenkuebel-sap-dm-pod2-mcp-server","name":"sap-dm-pod2-mcp-server","json":"/artifacts/blumenkuebel-sap-dm-pod2-mcp-server.json","ecosystem":"digital-manufacturing","origin_ring":"independent"},{"ref":"artifact:sap-fiori-guidelines","name":"sap-fiori-guidelines","json":"/artifacts/sap-fiori-guidelines.json","ecosystem":"ui5","origin_ring":"sap-official"},{"ref":"artifact:sap-fiori-ios","name":"sap-fiori-ios","json":"/artifacts/sap-fiori-ios.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:logalitech-sap-mdk-apps","name":"sap-mdk-apps","json":"/artifacts/logalitech-sap-mdk-apps.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:kts982-sap-odata-explorer","name":"sap-odata-explorer","json":"/artifacts/kts982-sap-odata-explorer.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:sap-samples-html5-applications-migration-skills-for-sap-btp","name":"SAP-samples/html5-applications-migration-skills-for-sap-btp","json":"/artifacts/sap-samples-html5-applications-migration-skills-for-sap-btp.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:sap-samples-joule-a2a-agent-toolkit","name":"SAP-samples/joule-a2a-agent-toolkit","json":"/artifacts/sap-samples-joule-a2a-agent-toolkit.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:sap-samples-sap-devs-cli","name":"SAP-samples/sap-devs-cli","json":"/artifacts/sap-samples-sap-devs-cli.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:sap-tutorials-content","name":"sap-tutorials-content","json":"/artifacts/sap-tutorials-content.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:sap-automation-pilot-agent-skills","name":"SAP/automation-pilot-agent-skills","json":"/artifacts/sap-automation-pilot-agent-skills.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:sap-leanix-ai-plugins","name":"SAP/leanix-ai-plugins","json":"/artifacts/sap-leanix-ai-plugins.json","ecosystem":"btp","origin_ring":"sap-official"},{"ref":"artifact:sap-ui-theme-designer-plugins","name":"SAP/ui-theme-designer-plugins-for-coding-agents","json":"/artifacts/sap-ui-theme-designer-plugins.json","ecosystem":"ui5","origin_ring":"sap-official"},{"ref":"artifact:jfilak-sapcli-claude-plugin","name":"sapcli Claude Code Plugin","json":"/artifacts/jfilak-sapcli-claude-plugin.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:attilaberencsi-sapskills","name":"sapskills","json":"/artifacts/attilaberencsi-sapskills.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:i562693-vkn-scaffold-fiori-ai-bridge","name":"scaffold-fiori-ai-bridge","json":"/artifacts/i562693-vkn-scaffold-fiori-ai-bridge.json","ecosystem":"ui5","origin_ring":"independent"},{"ref":"artifact:secondsky-sap-skills","name":"secondsky/sap-skills","json":"/artifacts/secondsky-sap-skills.json","ecosystem":"btp","origin_ring":"independent"},{"ref":"artifact:babamba2-superclaude-for-sap","name":"SuperClaude for SAP","json":"/artifacts/babamba2-superclaude-for-sap.json","ecosystem":"abap","origin_ring":"independent"},{"ref":"artifact:ui5-webcomponents-agent-skills","name":"UI5 Web Components agent skills","json":"/artifacts/ui5-webcomponents-agent-skills.json","ecosystem":"ui5","origin_ring":"sap-official"},{"ref":"artifact:ui5-plugins-coding-agents","name":"UI5/plugins-coding-agents","json":"/artifacts/ui5-plugins-coding-agents.json","ecosystem":"ui5","origin_ring":"sap-official"},{"ref":"artifact:marianfoo-werkbank","name":"Werkbank","json":"/artifacts/marianfoo-werkbank.json","ecosystem":"umbrella","origin_ring":"independent"}],"samples":[{"ref":"artifact:abap2ui5-app-template","name":"app-template","json":"/artifacts/abap2ui5-app-template.json"},{"ref":"artifact:sap-samples-cap-agentic-engineered","name":"SAP-samples/cap-agentic-engineered","json":"/artifacts/sap-samples-cap-agentic-engineered.json"}],"explained_by":[{"ref":"content:devtoberfest-2026-ai-assisted-cap-development","name":"AI Assisted CAP Development","json":"/content/devtoberfest-2026-ai-assisted-cap-development.json"},{"ref":"content:devtoberfest-2026-fiori-elements-adt-vscode-ui-33","name":"Intelligent App Development at Scale: SAP Fiori Elements + ABAP Development Tools for VS Code","json":"/content/devtoberfest-2026-fiori-elements-adt-vscode-ui-33.json"},{"ref":"content:devtoberfest-2026-token-efficiency","name":"Token Efficiency – Your Guide To Smart AI Development","json":"/content/devtoberfest-2026-token-efficiency.json"},{"ref":"content:devtoberfest-2026-daniel-hutzel-brain","name":"What's in Daniel Hutzel's brain?","json":"/content/devtoberfest-2026-daniel-hutzel-brain.json"},{"ref":"content:devtoberfest-2026-real-pro-code-joule-studio","name":"Real Pro-Code Development with Joule Studio","json":"/content/devtoberfest-2026-real-pro-code-joule-studio.json"},{"ref":"content:devtoberfest-2026-agentic-development-with-sapui5","name":"Beyond copilots: Agentic development with SAPUI5","json":"/content/devtoberfest-2026-agentic-development-with-sapui5.json"},{"ref":"content:devtoberfest-2026-sap-themes-with-coding-agents","name":"Bringing SAP themes to any web app with coding agents","json":"/content/devtoberfest-2026-sap-themes-with-coding-agents.json"},{"ref":"content:what-s-new-in-sap-cloud-application-programming-model-september-2026","name":"What's new in SAP Cloud Application Programming Model – September 2026","json":"/content/what-s-new-in-sap-cloud-application-programming-model-september-2026.json"},{"ref":"content:from-strategy-doc-to-runtime-rule-embedding-sap-ai-standards","name":"From Strategy Doc to Runtime Rule: Embedding SAP AI Standards into Claude Code","json":"/content/from-strategy-doc-to-runtime-rule-embedding-sap-ai-standards.json"},{"ref":"content:ui5-plugins-for-coding-agents-now-supporting-github-copilot","name":"UI5 Plugins for Coding Agents: Now Supporting GitHub Copilot","json":"/content/ui5-plugins-for-coding-agents-now-supporting-github-copilot.json"},{"ref":"content:abap-development-tools-for-visual-studio-code-patch-1-0-1-released","name":"ABAP development tools for Visual Studio Code: Patch 1.0.1 released","json":"/content/abap-development-tools-for-visual-studio-code-patch-1-0-1-released.json"},{"ref":"content:teaching-ai-agents-best-practices-a-skills-workspace-for-cap","name":"Teaching AI Agents Best Practices: A Skills Workspace for CAP Development","json":"/content/teaching-ai-agents-best-practices-a-skills-workspace-for-cap.json"},{"ref":"content:abap-development-tools-for-visual-studio-code-is-now-available-on-the-vs-code-ma","name":"ABAP development tools for Visual Studio Code is now available on the VS Code marketplace!","json":"/content/abap-development-tools-for-visual-studio-code-is-now-available-on-the-vs-code-ma.json"},{"ref":"content:a-major-hana-cli-version-built-with-the-help-of-ai","name":"Major New Version of the hana-cli: How It Was Built with the Help of AI (and a Lot of Human Review)","json":"/content/a-major-hana-cli-version-built-with-the-help-of-ai.json"},{"ref":"content:claude-code-via-mcp-poor-man-s-joule-or-a-practical-tool","name":"Claude Code via MCP: Poor man's Joule, or a practical tool?","json":"/content/claude-code-via-mcp-poor-man-s-joule-or-a-practical-tool.json"},{"ref":"content:setting-the-right-expectations-around-ai-for-code-generation","name":"Setting the right expectations around AI for code generation and getting past the inherent limits","json":"/content/setting-the-right-expectations-around-ai-for-code-generation.json"},{"ref":"content:github-copilot-vscode-my-own-sap-development-rules","name":"Github Copilot VSCode - My Own SAP Development Rules","json":"/content/github-copilot-vscode-my-own-sap-development-rules.json"},{"ref":"content:from-zero-to-fiori-building-sap-apps-with-ai-agents","name":"From Zero to Fiori: Building SAP Apps with AI Agents (And Why I Use Markdown Files Instead of MCP)","json":"/content/from-zero-to-fiori-building-sap-apps-with-ai-agents.json"},{"ref":"content:building-a-cap-service-with-cds-mcp-and-cline","name":"Building a CAP service with cds‑mcp and Cline — HANDS‑ON SUPER BASIC GUIDE [ with screenshots ] 🍌","json":"/content/building-a-cap-service-with-cds-mcp-and-cline.json"},{"ref":"content:enhancing-unit-testing-in-cap-java-with-github-copilot","name":"Enhancing Unit Testing in SAP CAP Java Applications with GitHub Copilot","json":"/content/enhancing-unit-testing-in-cap-java-with-github-copilot.json"},{"ref":"content:unlocking-the-power-of-llms-in-cap-llms-txt","name":"⚡Unlocking the Power of LLMs in CAP: Understanding llms.txt and llms-full.txt","json":"/content/unlocking-the-power-of-llms-in-cap-llms-txt.json"},{"ref":"content:ac-agentic-engineering-for-sap-btp-extensions","name":"Agentic Engineering for SAP BTP Extensions","json":"/content/ac-agentic-engineering-for-sap-btp-extensions.json"}],"normative_context":[]}}