SkillSkilltypeA procedure an agent follows. Indexed here, never written here.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

sap-architecture

A Claude Code plugin and portable agent skill that turns a plain-English description into a BTP diagram in SAP Architecture Center style, checked by a validator before it is handed over.

The skill carries the style rules a generic draw.io skill lacks, without which the output comes out with the wrong palette, bent arrows and clipped labels. It bundles 100 BTP service icons in the variant the SAP BTP Solution Diagram Guidelines mandate, and 71 reference templates from those guidelines, the SAP Architecture Center and other SAP references, which keep SAP's Apache-2.0 licence. A validator checks each diagram and an autofixer repairs what it finds. The rest is Markdown and dependency-free Python under MIT, so agents other than Claude can run it: the README names the instruction file to point at the skill for Codex, GitHub Copilot, Cursor and the tools that read AGENTS.md, and states that on those the skill is wired in per project rather than loaded automatically.

Facts

Last pushLicenceMIT

Where it sits

Lives in
Provides
Agent guidanceBTPAgent guidancecapabilityPackaged 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.Architecture diagramsBTPArchitecture diagramscapabilityDrawing the architecture and components of a solution so another person can understand their responsibilities and connections. Shared notation makes diagrams readable across teams.
Requires
draw.iodraw.iooutside the atlasViewing and editing the result only; the skill writes the .drawio file without it.

Who is behind it

Marian ZeisMarian ZeisPersonMaintains this
In the atlas: maintains 35, contributes to 86, wrote 25
@marianfoo
maintainer

Before choosing this

Conditions

PracticalFunctional boundary

A diagram of anything other than an SAP, BTP or on-premise landscape: the skill is tuned to the Horizon style and its 71 templates. It drafts rather than finishes, and its README budgets 15 to 30 minutes of edits in draw.io per diagram. Without Python the validator does not run.

What it declares

Every artifact

Type
Skill
Origin
Independently maintained

As a skill

Distributed through
Agent plugin marketplaceCopied into the project

For agent guidance

Installs into
Claude CodeClaude DesktopCodexGitHub CopilotCursorGemini CLI

For architecture diagrams

Checking
Checks the fileChecks the pictureRepairs findings
Diagram format
drawio
property statedstated nonot said

Tasks this contributes to3Beta

Check a BTP solution diagram against the guidelineA BTP solution diagram exists, and before it goes into a document or a review someone wants to know whether it follows SAP's visual language rather than only looking about right.Covers, under conditionsa validator and an autofixer inside the drawing skill
What it does

validate.py reads the file for bent arrows, clipped labels, off-palette colours, off-grid coordinates, wrong stroke widths and non-Helvetica fonts, autofix.py repairs what it finds, and a second loop renders the diagram and scores the picture against the SAP corpus.

Conditions

Python 3.8 or later on the PATH: without it the validator and the scorer do not run, and the diagram is drafted without the checks

Remaining work

Install the skill and drive it from an agent; the checks run as part of the skill's pipeline rather than against a file someone brings to it.

All options on the Architecture diagrams page →
Hand an agent SAP's BTP diagram rulesSomeone 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.Coversthe rules as a portable skill with templates
What it does

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.

All options on the Agent guidance page →
Keep the SAP knowledge an agent follows currentA 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.Assessed, not knownthe bundled kind, where the question is open
What it does

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.

All options on the Agent guidance page →

Connections5

Learn more1

Readings
  1. Creating an ARC-1 BTP Diagram with Codex and a draw.io SkillMarian Zeis, blog.zeis.de — Marian Zeis

README

quoted from marianfoo/btp-drawio-skill under MIT, read
marianfoo/btp-drawio-skill/README.mdOn GitHub

btp-drawio-skill

A Claude Code plugin (and Agent-Skill-compatible standalone skill) that turns a plain-English description into a polished SAP Architecture Center / BTP solution diagram as an editable .drawio file — following the official SAP BTP Solution Diagram Guidelines.

Why a dedicated skill? Reproducing SAP Architecture Center style by hand or via a generic drawio skill consistently produces off-style output — wrong palette, bent arrows, clipped labels, text bleeding into BTP fills, blank icon stencils. This plugin bakes in the rules that matter and gates every output behind a validator.

Under the hood it bundles 100 SAP BTP service icons, 71 reference templates, 448 indexed draw.io assets, a validator, and an autofixer — all local, all traceable to SAP's guidelines.

Table of contents


Install

Recommendation: install it as a skill — that's all you need. It works the same way everywhere Claude Code runs — terminal, IDE extension, or the Claude desktop/web apps: install once, then describe the diagram in plain English and Claude auto-loads the skill. You do not need to build an .mcpb bundle or publish to npm — those are optional extras for non-Claude tools, documented in internals.

Claude Code (CLI)
/plugin marketplace add marianfoo/btp-drawio-skill
/plugin install sap-architecture

Update or remove later:

/plugin update sap-architecture
/plugin uninstall sap-architecture
/plugin marketplace remove btp-drawio-skill
Other AI coding tools (VS Code Copilot, OpenAI Codex, Cursor, …)

You don't need Claude for this. 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. Wire it in once, then ask for a diagram.

First, get the skill files where your agent can reach them:

git clone https://github.com/marianfoo/btp-drawio-skill.git

Then point your tool's instruction file at the skill:

ToolAdd / use this fileOfficial docs
OpenAI Codex (CLI & IDE)AGENTS.md in your repo rootAGENTS.md · Codex guide
GitHub Copilot (VS Code, agent mode).github/copilot-instructions.mdVS Code custom instructions
Cursorbundled cursor-rules/sap-architecture.mdc → .cursor/rules/Cursor Rules
Gemini CLI · Jules · Amp · FactoryAGENTS.md (same open standard)AGENTS.md
Windsurf · Cline · Continue · Aiderthat tool's rules / context file → point it at the skill foldertheir own docs
Anything elsepaste the skill's instructions into the system promptready-made prompt

And tell the agent to use it — put something like this in that file (full version in internals):

For any SAP / BTP / on-prem architecture diagram, use the sap-architecture skill at
<path>/plugins/sap-architecture/skills/sap-architecture/. Follow its SKILL.md 6-step
workflow and run its scripts (Python 3.8+, no third-party deps): scaffold_diagram.py →
extract_icon.py → relabel.py → autofix.py → validate.py → score_corpus.py --min-score 90,
then iterate.py to render, re-score, and fix the worst issue until it matches the SAP reference.
Never write .drawio XML from scratch — always scaffold from a SAP template first.

Two caveats: 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. Use a strong model (see Recommended models) — e.g. Codex with GPT-5.5; small models skip the scaffold/validate discipline.

Want the skill in VS Code or JetBrains with Claude instead? The official Claude Code extension runs it just like the CLI — install the extension, then /plugins.

Claude Desktop / Claude.ai

These apps load skills from your skills folder. Since this repo follows the Agent Skills open standard, drop the skill tree straight in:

macOS / Linux:

git clone https://github.com/marianfoo/btp-drawio-skill.git
mkdir -p ~/.claude/skills
cp -R btp-drawio-skill/plugins/sap-architecture/skills/sap-architecture ~/.claude/skills/

Windows (PowerShell):

git clone https://github.com/marianfoo/btp-drawio-skill.git
New-Item -ItemType Directory -Force "$HOME\.claude\skills"
Copy-Item -Recurse `
  btp-drawio-skill\plugins\sap-architecture\skills\sap-architecture `
  "$HOME\.claude\skills\"

Restart Claude — the skill shows up in the Skills panel and auto-invokes when you describe an SAP architecture.

What you need
  • Claude Code or Claude Desktop / Claude.ai — any recent version with skills support.
  • Python 3.8+ on your PATH — the diagram engine (template selection, icon extraction, autofix, validation, scoring) is plain Python with zero third-party dependencies. Check with python3 --version.
  • draw.io to open the result — the desktop app or app.diagrams.net. Only needed to view/edit; the skill writes the .drawio without it.
  • Optional: the draw.io desktop CLI — only if you want the skill to export PNG/SVG/PDF for you. Without it you still get the editable .drawio and export by hand.
  • No API keys, no npm install, no MCP server, no cloud calls — every icon, template, and script is bundled and runs locally.

This is not an easy task. A good diagram needs multi-step reasoning — parse the scenario, pick the right SAP template, place icons, make surgical XML edits without breaking layout, then run the validate/score loop and react to the results. Use a strong frontier reasoning model:

TierModelsNotes
BestClaude Opus 4.x (e.g. Opus 4.8)Top results; follows the scaffold-then-validate discipline reliably. In Claude Code, select it with /model.
Also strongGPT-5.5 / latest GPT-5-series, Google Gemini 2.5 ProGood choices in non-Claude runtimes (Cursor, Windsurf, …).
Budget but capableClaude Sonnet 4.xFaster/cheaper; usually fine for straightforward template-based diagrams.
Avoid for authoringHaiku-class, *-mini / *-nano, small local models (<~30B)They tend to skip the template scaffold and write XML from scratch, ignore the validate/score gate, and produce off-style output.

The local Ollama loop in internals is a separate batch-testing path — it deliberately uses small local models to stress-test the corpus, not to author your real diagrams.


Use it

Install the skill, then just describe the architecture you want. Claude auto-loads the skill (its trigger phrases are tuned for SAP / BTP / architecture / drawio keywords), picks the closest reference template, drops the right icons, composes the XML, runs autofix + validate + score, and hands you back a ready-to-open .drawio plus a numbered flow narration.

A good first prompt:

Create an SAP architecture diagram showing a Copilot Studio MCP client calling an ARC-1 BTP Cloud Foundry app. ARC-1 authenticates via XSUAA OAuth, uses Destination Service + Cloud Connector with Principal Propagation to reach an on-prem S/4HANA system.

Example prompts
  • "Draw my BTP deployment — CAP app with XSUAA, HANA Cloud, Destination Service to on-prem ECC."
  • "Diagram the XSUAA OAuth flow between Claude Desktop, our MCP server, and on-prem ABAP."
  • "Show how a user on VS Code Copilot reaches SAP BW/4HANA through Cloud Connector with Principal Propagation."
  • "Make an L1 conceptual diagram of a Joule integration with Task Center pulling from S/4, SuccessFactors, and Ariba."
  • "Generate an L2 ref-arch for SAP Build Apps fronting a CAP service bound to SAP Event Mesh."

For sharper results, see Write better prompts.

Good to know (limits)
  • It's an authoring assistant, not a one-shot generator. Budget ~15–30 min per diagram: roughly ⅓ of prompts pass the quality gate clean, the rest need a few surgical edits in draw.io desktop.
  • No Python → no quality gates. Claude can still draft a diagram, but the validator/scorer won't run, so you lose the off-palette / bent-arrow / clipped-label checks.
  • PNG/SVG/PDF export needs the draw.io CLI. No CLI → export manually from draw.io.
  • SAP / BTP / on-prem diagrams only. It's tuned to the SAP Horizon style and a 71-template corpus, not a general-purpose diagram generator.
  • npx btp-drawio-skill is not the skill and isn't published to npm yet — it's the raw CLI/MCP wrapper for non-Claude tools. Skip it for Claude.
Nudge it to a good diagram

Expect the first draft to be ~80% there, then nudge it. The skill ships a feedback loop that closes the gap — when you ask Claude to keep improving, it renders the diagram to an image, scores it against the SAP corpus, looks at the picture, fixes one thing, and re-checks. So you can review the result and reply in plain English; you don't need to touch XML.

Give specific, visual feedback. Vague ("make it better") gives weak results; concrete observations map directly to fixes:

  • "The icons are too large and overlap the card text — shrink them to SAP's 32×32."
  • "Two arrows cross straight through the BTP box — re-route them around it."
  • "Joule should be its own purple zone next to BTP, not nested inside it."
  • "The title band and SAP footer are missing — add them back from the template."
  • "Use the canonical SAP flow pills (TRUST, Authenticate, OAuth, OData/REST), not invented labels."

Under the hood the agent runs iterate.py (render + score + the worst-first fix list) and render_compare.py (a side-by-side / overlay / swipe / difference HTML review you can open in a browser). You don't run these yourself — just describe what looks off and let it loop until the diagram matches the SAP reference. See internals for the loop details.


Write better prompts

The skill works best when the prompt describes an architecture, not just a product list. Give the agent enough context to choose the right SAP reference template and preserve its structure.

Use this shape for high-quality prompts:

Create an L2 SAP Architecture Center-style draw.io diagram for <scenario>.

Audience and level: <business overview | solution architecture | implementation flow>.
Main zones: <User/Client>, <SAP BTP subaccount/runtime>, <SAP Cloud Solutions>, <On-Premise>, <Third-party/Hyperscaler>, <Network divider if relevant>.
Actors and entry points: <who starts the flow and from where>.
SAP BTP services: <exact service names>.
Backends/systems: <SAP S/4HANA, ECC, BW/4HANA, SuccessFactors, Datasphere, Databricks, etc.>.
Identity/security: <IAS, XSUAA, OAuth, SAML, Principal Propagation, trust, authorization>.
Flow steps: 1. <protocol/action>, 2. <protocol/action>, 3. <protocol/action>.
Constraints: <must show Cloud Connector | use Joule as separate zone | prefer template RA0029 | avoid implementation internals>.
Output: editable .drawio plus numbered flow narration below the diagram.

Helpful context to attach or paste:

  • Existing architecture notes, but trimmed to the services, actors, systems, and flows that should appear.
  • A numbered flow, even if rough. Protocol words such as HTTPS, OData/REST, OAuth, SAML, A2A, MCP, ORD, and Principal Propagation help the skill pick canonical pills and edge colors.
  • The intended abstraction level: L0 for business overview, L1 for solution components, L2 for default technical flow. Avoid mixing all three in one diagram.
  • The deployment boundary: which systems are inside SAP BTP, which are SAP cloud apps, which are on-premise, and which are third party or hyperscaler.
  • Any preferred SAP reference/template name if you know it, for example ac_RA0029_AgenticAI_root.drawio for Agentic AI with Joule.
  • A short list of exclusions, such as "do not show CI/CD" or "do not include database internals".

Avoid prompts like "make a BTP diagram for our app" unless you want the agent to ask a clarifying question. Also avoid dumping long unfiltered design docs: they usually contain several diagrams' worth of scope. If you paste a long document, add a short "diagram scope" paragraph that says exactly which flow to draw.

Strong prompt:

Create an L2 SAP Architecture Center-style draw.io diagram. A developer in VS Code uses ARC-1 running on SAP BTP Cloud Foundry. ARC-1 authenticates with XSUAA, reads a Destination, uses SAP Connectivity service and SAP Cloud Connector, and calls on-premise SAP S/4HANA via OData/REST with Principal Propagation. Show zones for Developer Workstation, SAP BTP Cloud Foundry, and Customer On-Premise Network. Output editable .drawio and a numbered flow narration.

Weak prompt:

Draw ARC-1 with BTP and S/4HANA.


What's bundled

  • 100 SAP BTP service icons (inline SVG data URIs, grey-background-circle variant — the one SAP mandates for diagrams)
  • 448 indexed SAP draw.io starter-kit assets across 10 bundled libraries: BTP service icons, generic icons, connector presets, area/default shapes, essential shapes, number markers, SAP brand-name text, text elements, and annotation/interface pills
  • 71 pristine reference templates (Apache-2.0): canonical examples from SAP/btp-solution-diagrams, curated reference architectures from SAP/architecture-center, and selected external SAP references — covering IAM, Joule, MCP / Agentic AI, multitenant SaaS, DevOps, Private Link, Cloud Connector, Event-Driven Architecture, resiliency, Business Data Cloud, integration, SIEM/SOAR, and SuccessFactors
  • 10 reference sheets with the exact Horizon hex values, typography hierarchy, shape/edge style strings, layout, and do-and-don't rules — every value cited from the SAP BTP Solution Diagram Guidelines or observed in SAP's public corpus
  • A validator + autofixer (validate.py, autofix.py) that catch and mechanically repair bent arrows, clipped labels, off-palette colors, off-grid coordinates, wrong stroke widths, non-Helvetica fonts, and more
  • A template selector + scoring harness (select_reference.py, compare.py, score_corpus.py) that picks the nearest SAP template and reports how close a diagram is to the corpus

Full palette/style rules and the scoring methodology live in internals.


How it works

The skill is an authoring assistant, not a one-shot generator. When triggered it runs a short pipeline: parse your description into a plan → scaffold from the closest SAP reference template (never write XML from scratch) → place official service icons → make surgical label edits → run autofix + validate + score → narrate the flow. The scaffold-then-validate discipline is what keeps the output on-style. From there it can iterate: render the diagram to an image, compare it to the SAP reference, and fix the worst issue first — repeat until it matches (see Nudge it to a good diagram).

See the full 6-step pipeline, the design-rule table, and the validator internals in docs/internals.md.


Documentation & deep dive

  • docs/internals.md — how it works (full pipeline), the SAP design rules it enforces, running the Python scripts yourself, npx / MCP / MCPB, other Agent-Skills runtimes, the Ollama evaluation loop, repo layout, and development.
  • SKILL.md — the skill instructions Claude loads.
  • references/ — the cited reference sheets (palette, typography, shapes/edges, levels, layout, methodology).
  • plugins/sap-architecture/README.md — plugin-level deep dive.

License & attribution

  • Plugin code (Python scripts, markdown references, plugin manifests, this README): MIT — see LICENSE.
  • Bundled SAP assets under plugins/sap-architecture/skills/sap-architecture/assets/ (icon library + reference templates): Apache-2.0, © SAP SE or an SAP affiliate company — sourced from SAP/btp-solution-diagrams and SAP/architecture-center. See plugins/sap-architecture/skills/sap-architecture/assets/NOTICE.md for full attribution.
Credits & research sources

SAP upstream — the canonical rules:

Prior art — community skills that informed this one:

  • miyasuta/claude-drawio-btp-diagram — the center-alignment rule for straight orthogonal edges; the docs/rules + docs/styles + docs/GUIDELINES.md layering pattern
  • lemaiwo/btp-drawio-skill — the marketplace + single-plugin repo layout used here; the approach of bundling SAP icon XML libraries directly

Claude Code plugin + skills docs:

MIT, read

History

Latest

v0.2.0

Others providing50

Agent guidance
  1. abap2UI5 for VS CodeVS Code extension to preview, activate and lint abap2UI5 appsfrom ABAP
  2. sap-cx-developer-companionAgent skill for SAP Customer Experience APIs, CDS and errorsfrom SAP Commerce
  3. sap-basis-opsRunbook skills for Basis operations at the OS and database layerfrom ABAP
  4. abap-offstack-aunitAgent skill for off-stack ABAP Unit tests and an abaplint gatefrom ABAP
  5. ARC-1 SkillsTwenty-two agent skills shipped with arc-1from ABAP
  6. sapskillsAgent skills for Clean ABAP, ADT in VS Code and guardrailsfrom ABAP
  7. SuperClaude for SAPClaude Code plugin with an ABAP MCP server and write guardsfrom ABAP
  8. sap-dm-pod2-mcp-serverMCP server for SAP Digital Manufacturing POD 2.0 extensionsfrom SAP Digital Manufacturing
  9. capire/skillsAgent skills for CAP development, each a SKILL.md with referencesfrom CAP
  10. sap-cloud-integration-pipeline-assistantAgent skill for the Pipeline Concept in SAP Cloud Integrationfrom BTP/BAIP
  11. claude-abap-devFive ABAP workflows for Claude Code on existing MCP serversfrom ABAP
  12. DanKromp/skillOverflowCollection of 41 agent skills, 37 for SAP development tasksfrom CAP
  13. sap-commerce-skillAgent skill for SAP Commerce Cloud 2211-jdk21.1 and laterfrom SAP Commerce
  14. ARC-DRAWMCP server drawing BTP solution diagrams on a draw.io canvasfrom BTP/BAIP
  15. cap-mtx-scaffoldAgent skill for CAP multitenancy scaffoldingfrom CAP
  16. sap-ai-dev-toolkitMCP proxy pinning an agent's ABAP tools to one SAP systemfrom ABAP
  17. scaffold-fiori-ai-bridgeAgent skill generating a Joule Frontend Actions bridge for UI5 appsfrom UI5
  18. sapcli Claude Code PluginAgents and skills that drive sapcli instead of ADTfrom ABAP
  19. CAP GuardianCAP review skill for coding agents with gates and prohibitionsfrom CAP
  20. sap-odata-explorerRust CLI and desktop app for exploring SAP OData servicesfrom BTP/BAIP
  21. btp-solution-diagram-generatorClaude plugin writing BTP solution diagrams as .drawio filesfrom BTP/BAIP
  22. abap-skillsSeventeen agent skills for ABAP developmentfrom ABAP
  23. drawio-skill-sapGitHub Copilot skill writing BTP solution diagrams as draw.io XMLfrom BTP/BAIP
  24. sap-mdk-appsAgent skill for Mobile Development Kit projectsfrom BTP/BAIP
  25. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystemfrom ABAP
  26. WerkbankLocal desktop workspace for AI conversations with SAP connectorsfrom Across stacks
  27. SAP Datasphere Plugin for ClaudeEighteen Datasphere skills over a bundled MCP serverfrom BTP/BAIP
  28. claude-abap-skillsClaude Code plugins with Clean ABAP rules and templatesfrom ABAP
  29. SAP Power for KiroSAP skills for the Kiro IDEfrom BTP/BAIP
  30. drawio-btp-diagram-skillsClaude Code skills for BTP architecture diagrams in draw.iofrom BTP/BAIP
  31. @patimweb/pi-cap-bestpracticesSAP's capire/skills packaged for the pi coding agentfrom CAP
  32. pod2-configAn agent skill that turns a described POD change into an importable [SAP Digital Manufacturing](external:sap-digital-manufacturing) POD 2.0 export, built from standard plugins and actions only.from SAP Digital Manufacturing
  33. aicore-skillsFour agent skills for SAP AI Core in SAP's AI Skills Libraryfrom BTP/BAIP
  34. SAP/automation-pilot-agent-skillsEight skills for writing and operating SAP Automation Pilot contentfrom BTP/BAIP
  35. SAP Developers MCPHosted MCP server of developers.sap.com tutorials and missionsfrom Across stacks
  36. sap-fiori-guidelinesAgent skill built from the Fiori Design Guidelinesfrom UI5
  37. sap-fiori-iosAgent skill mapping Fiori iOS UI Kit nodes in Figma to SwiftUIfrom BTP/BAIP
  38. SAP/leanix-ai-pluginsClaude Code plugin with two skills for SAP LeanIX scriptingfrom BTP/BAIP
  39. SAP-samples/html5-applications-migration-skills-for-sap-btpClaude Code plugin with skills migrating HTML5 apps to appFrontfrom BTP/BAIP
  40. SAP-samples/joule-a2a-agent-toolkitSkills for building an A2A agent for Joule and deploying it to CFfrom BTP/BAIP
  41. SAP-samples/sap-devs-cliCLI adding SAP developer knowledge and MCP servers to AI coding toolsfrom BTP/BAIP
  42. sap-tutorials-contentAgent skill mapping the developers.sap.com content APIfrom BTP/BAIP
  43. SAP/ui-theme-designer-plugins-for-coding-agentsAgent plugin on the SAP Design System and theming parametersfrom UI5
  44. secondsky/sap-skillsForty SAP development plugins for coding agentsfrom BTP/BAIP
  45. claude-sap-kitClaude Code plugin adding Custom_* tools to arc-1from ABAP
  46. UI5/plugins-coding-agentsUI5 plugins for coding agentsfrom UI5
  47. UI5 Web Components agent skillsTwo agent skills for accessibility and styling of web componentsfrom UI5
  48. rap-skillsRAP skills delivered branch-per-target for each deploymentfrom ABAP
  49. KlystronMCP server in ABAP inside the application server, with agent skillsfrom ABAP
Architecture diagrams
  1. ARC-DRAWMCP server drawing BTP solution diagrams on a draw.io canvasfrom BTP/BAIP
  2. btp-solution-diagram-generatorClaude plugin writing BTP solution diagrams as .drawio filesfrom BTP/BAIP
  3. abap-skillsSeventeen agent skills for ABAP developmentfrom ABAP
  4. drawio-skill-sapGitHub Copilot skill writing BTP solution diagrams as draw.io XMLfrom BTP/BAIP
  5. drawio-btp-diagram-skillsClaude Code skills for BTP architecture diagrams in draw.iofrom BTP/BAIP
  6. SAP BTP Solution Diagram GuidelinesSAP's visual language and templates for BTP solution diagramsfrom BTP/BAIP

Details

Sources3
Added by handdiscovered herechecked
github.com/marianfoo/btp-drawio-skilltree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, developer-experience
History in the atlas3
  1. Claude Code, Claude Desktop, Codex, GitHub Copilot, Cursor, Gemini CLI
  2. The same, with the instruction file the README names per tool and its statement that on those tools the skill is wired in per project rather than loaded automatically.
  3. First seen.
For your agent
Ref
artifact:marianfoo-btp-drawio-skill
JSON
/artifacts/marianfoo-btp-drawio-skill.json
MCP
Connecting an agent