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 →

secondsky/sap-skills

Forty SAP development plugins installed through the skills command line or the Claude Code and Codex marketplaces, with a record per plugin of what its claims were checked against.

Forty plugins across SAP development, each with a record of what its claims were checked against. Public-source and package-registry verification is tracked where it is available, and docs/project/source-verification-ledger.json tracks live tenant and system validation per plugin, recorded only where evidence of that validation exists, so a reader can see which plugins were checked how instead of taking forty at once on trust. The content is written to be portable: npx skills add secondsky/sap-skills loads it into whichever clients the upstream skills command line supports, Claude Code and Codex each have a native marketplace command, and in OpenCode, Cursor or Gemini CLI the README says to treat the Claude-specific agents, hooks, slash commands and MCP configs as role guidance, optional validators, prompt templates and connection recipes.

Facts

Last pushLicenceGPL-3.0

Where it sits

Lives in
Provides
Agent guidanceABAPCAPUI5BTPAgent 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.
Optional
@cap-js/mcp-server@cap-js/mcp-serverartifactWhat plugins/sap-cap-capire/.mcp.json registers for that one plugin, pinned to version 0.0.5.@ui5/mcp-server@ui5/mcp-serverartifactWhat plugins/sapui5/.mcp.json registers for that one plugin, pinned to version 0.2.17.@sap-ux/fiori-mcp-server@sap-ux/fiori-mcp-serverartifactWhat plugins/sap-fiori-tools/.mcp.json registers for that one plugin, pinned to version 1.11.7.hana-mcp-serverhana-mcp-serverartifactWhat plugins/sap-hana-cli/.mcp.json registers for that one plugin, pinned to version 0.3.4, with the HANA connection parameters taken from environment variables.@mariodefe/sap-datasphere-mcp@mariodefe/sap-datasphere-mcpartifactWhat plugins/sap-datasphere/.mcp.json registers for that one plugin, pinned to version 1.7.0, with the Datasphere URL and OAuth client credentials taken from environment variables.

Who is behind it

EddieEddiePersonMaintains this
In the atlas: maintains 1, contributes to 1
@secondsky
maintainerAnupam MedirattaPersonContributes to this
In the atlas: contributes to 1
@anupamme
Geert-Jan KlapsPersonContributes to this
In the atlas: maintains 4, contributes to 11, wrote 4
@geert-janklaps
Max StreifenederPersonContributes to this
In the atlas: contributes to 2, wrote 1
@maxstreifeneder
Tuan DinhPersonContributes to this
In the atlas: contributes to 1
@tuandinh0801
4 contributors

Before choosing this

Conditions

PolicySAP API Policy 4.2026a§ 1.1, 1.2, 2.2.2Its sap-api-policy skill is used to assess an SAP API or interface usage scenario.
  • § 1.1 Published APIs. Published APIs are made available for the documented purposes identified by SAP, including integration, extensions and data exchange.
  • § 1.2 Non-Published APIs. Customer and third-party applications must not access non-published APIs except where documentation permits it or SAP otherwise authorizes it.
  • § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.

This collection includes an evidence-based SAP API Policy assessment skill. Its result is contextual guidance rather than an atlas or maintainer compliance verdict; verify the applicable SAP documentation and agreement.

SAP API Policy 4.2026a →
PracticalFunctional boundary

GPL-3.0, which is a licence to read before vendoring any of it into something you ship. Forty plugins is also a lot of always-available surface — the ledger is there because breadth and verification pull in opposite directions, and it does not resolve that so much as report it.

What it declares

Every artifact

Type
Skill
Origin
Independently maintained

As a skill

Distributed through
npmAgent plugin marketplace

For agent guidance

Installs into
Claude CodeGitHub CopilotCursorCodexGemini CLIOpenCode

Connections6

secondsky/sap-skills connectionssecondsky/sap-skillsPROVIDES→ provides1provides stated Forty plugins across SAP development, with the basis for each recorded in the repository: public-source and package-registry verification where it is available, and live tenant or system validation tracked per plugin in a ledger file, recorded only where evidence of that validation exists. SAP Skills for AI Coding Assistants — README: https://github.com/secondsky/sap-skills secondsky/sap-skills — README, verification: https://github.com/secondsky/sap-skills secondsky/sap-skills — README, the ledger file: https://raw.githubusercontent.com/secondsky/sap-skills/main/README.mdAgent guidanceNEEDS→ optionally needs5optionally needs stated If: the sap-cap-capire plugin is used in a client that activates the MCP server its .mcp.json registers; in a client that does not, the README says that file is a connection recipe to configure by hand What plugins/sap-cap-capire/.mcp.json registers for that one plugin, pinned to version 0.0.5. secondsky/sap-skills — plugins/sap-cap-capire/.mcp.json: https://raw.githubusercontent.com/secondsky/sap-skills/main/plugins/sap-cap-capire/.mcp.json secondsky/sap-skills — README, portability note: https://github.com/secondsky/sap-skills@cap-js/mcp-serverifoptionally needs stated If: the sap-datasphere plugin is used in a client that activates the MCP server its .mcp.json registers; in a client that does not, the README says that file is a connection recipe to configure by hand What plugins/sap-datasphere/.mcp.json registers for that one plugin, pinned to version 1.7.0, with the Datasphere URL and OAuth client credentials taken from environment variables. secondsky/sap-skills — plugins/sap-datasphere/.mcp.json: https://raw.githubusercontent.com/secondsky/sap-skills/main/plugins/sap-datasphere/.mcp.json secondsky/sap-skills — README, portability note: https://github.com/secondsky/sap-skills@mariodefe/sap-datasphere-mcpifoptionally needs stated If: the sap-fiori-tools plugin is used in a client that activates the MCP server its .mcp.json registers; in a client that does not, the README says that file is a connection recipe to configure by hand What plugins/sap-fiori-tools/.mcp.json registers for that one plugin, pinned to version 1.11.7. secondsky/sap-skills — plugins/sap-fiori-tools/.mcp.json: https://raw.githubusercontent.com/secondsky/sap-skills/main/plugins/sap-fiori-tools/.mcp.json secondsky/sap-skills — README, portability note: https://github.com/secondsky/sap-skills@sap-ux/fiori-mcp-serverifoptionally needs stated If: the sapui5 plugin is used in a client that activates the MCP server its .mcp.json registers; in a client that does not, the README says that file is a connection recipe to configure by hand What plugins/sapui5/.mcp.json registers for that one plugin, pinned to version 0.2.17. secondsky/sap-skills — plugins/sapui5/.mcp.json: https://raw.githubusercontent.com/secondsky/sap-skills/main/plugins/sapui5/.mcp.json secondsky/sap-skills — README, portability note: https://github.com/secondsky/sap-skills@ui5/mcp-serverifoptionally needs stated If: the sap-hana-cli plugin is used in a client that activates the MCP server its .mcp.json registers; in a client that does not, the README says that file is a connection recipe to configure by hand What plugins/sap-hana-cli/.mcp.json registers for that one plugin, pinned to version 0.3.4, with the HANA connection parameters taken from environment variables. secondsky/sap-skills — plugins/sap-hana-cli/.mcp.json: https://raw.githubusercontent.com/secondsky/sap-skills/main/plugins/sap-hana-cli/.mcp.json secondsky/sap-skills — README, portability note: https://github.com/secondsky/sap-skillshana-mcp-serverif

README

quoted from secondsky/sap-skills under GPL-3.0, read
secondsky/sap-skills/README.mdOn GitHub

SAP Skills for AI Coding Assistants

40 SAP development plugins with evidence-tracked verification

License: GPL-3.0 Plugins Version

SAP development plugins for AI coding assistants, with public-source or package-registry verification tracked where available. Live tenant and system validation is tracked per plugin in docs/project/source-verification-ledger.json.

The repository is packaged for the Claude and Codex marketplaces, and the SAP skill content is written to be portable. In clients such as OpenCode, Cursor, or Gemini CLI, Claude-specific agents, hooks, slash commands, and MCP configs should be treated as role guidance, optional validators, prompt templates, and connection recipes unless that client supports them natively.

Contents


Quick Start

Supported agents via npx skills

Install via vercel-labs/skills. 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:

npx skills add secondsky/sap-skills
Codex CLI (native marketplace)

Codex reads the repository marketplace from .agents/plugins/marketplace.json and uses the shared SKILL.md content. From a local checkout:

codex plugin marketplace add .
codex plugin add sap-abap@sap-skills

From GitHub, use sparse checkout to include the Codex registry and plugin payloads:

codex plugin marketplace add https://github.com/secondsky/sap-skills.git --sparse .agents/plugins --sparse plugins

The native Codex layer is skills-first. Claude commands, agents, hooks, LSP configuration, and MCP recipes remain available as optional Claude or manual fallback resources. See the manual MCP connection guide before configuring any server. The generic npx skills add command above remains a portable installation option.

Claude Code (native marketplace)
# Add the marketplace
/plugin marketplace add secondsky/sap-skills

# Install individual plugins
/plugin install sap-cap-capire@sap-skills

# Or install multiple at once
/plugin install sap-cap-capire@sap-skills sap-fiori-tools@sap-skills

Team setup — add at project scope:

claude plugin marketplace add secondsky/sap-skills --scope project

Or configure .claude/settings.json directly:

{
  "extraKnownMarketplaces": {
    "sap-skills": {
      "source": {
        "source": "github",
        "repo": "secondsky/sap-skills"
      }
    }
  }
}
Clone repository
git clone https://github.com/secondsky/sap-skills.git

How It Works

Once installed, plugins provide skills that automatically activate based on your project context:

  • "Create a new CAP service" → sap-cap-capire activates
  • "Set up Fiori Elements app" → sap-fiori-tools activates
  • "Deploy to BTP" → sap-btp-cloud-platform activates
  • "Write ABAP CDS view" → sap-abap-cds activates
  • "Create SAC planning model" → sap-sac-planning activates

No manual invocation needed — the AI assistant loads relevant skills when you need them.

Claude-compatible clients may also activate bundled commands, agents, hooks, and MCP servers. Other harnesses can still use the same files as Markdown guidance: run hook validators manually when desired, follow command output contracts as prompt templates, and configure MCP servers using the documented command, arguments, environment variables, and safety notes.


Available Plugins (40)

Feature icons: ⌘ = commands · 🤖 = agents · 🛡 = hooks · 🔌 = MCP · LSP = language server

🔧 Tooling & Development (5)
PluginFeaturesDescription
sap-api-policy—Evidence-based assessment of SAP API/interface usage against the SAP API Policy (v.4.2026a)
sap-api-style⌘1 · 🤖1API documentation standards following SAP guidelines
sap-browser-automation—Shared authenticated SAP browser automation, Edge/CDP, profile reuse, and recovery
sap-dependency-security⌘1 · 🛡SAP dependency security, MCP executable trust, cooldown policies, lockfile hardening, supply-chain safeguards
sap-hana-cli⌘2 · 🤖1 · 🔌MCPSAP HANA Developer CLI for database operations
☁️ SAP BTP Platform (15)
PluginFeaturesDescription
sap-btp-best-practices⌘1SAP BTP development best practices and patterns
sap-btp-build-work-zone-advanced⌘1SAP Build Work Zone (Advanced Edition) development
sap-btp-business-application-studio⌘1SAP Business Application Studio (BAS) development
sap-btp-cias⌘1Cloud Integration Automation Service (CIAS) integration
sap-btp-cloud-logging⌘1SAP BTP Cloud Logging service
sap-btp-cloud-identity-services⌘1 · 🤖1SAP Cloud Identity Services: IAS, IPS, AMS, XSUAA migration
sap-btp-cloud-platform⌘1 · 🤖1SAP Business Technology Platform core services
sap-btp-cloud-transport-management⌘1Cloud Transport Management (CTM) service
sap-btp-connectivity⌘1SAP BTP Connectivity service
sap-btp-developer-guide⌘1Comprehensive SAP BTP developer guide
sap-btp-integration-suite⌘1 · 🤖1SAP Integration Suite development
sap-btp-intelligent-situation-automation⌘1Deprecated Intelligent Situation Automation data export, unsubscription, and legacy reference
sap-btp-job-scheduling⌘1SAP BTP Job Scheduling service
sap-btp-master-data-integration⌘1Master Data Integration service
sap-btp-service-manager⌘1SAP BTP Service Manager operations
🎨 UI Development (4)
PluginFeaturesDescription
sap-fiori-tools⌘2 · 🤖1 · 🔌MCPSAP Fiori Tools development and deployment
sapui5⌘5 · 🤖4 · 🛡 · 🔌MCPSAPUI5 framework development
sapui5-cli⌘2SAPUI5 CLI tools and commands
sapui5-linter⌘2SAPUI5 code quality and linting
📊 Data & Analytics (7)
PluginFeaturesDescription
sap-bw-query⌘3 · 🔌MCPPassword-safe portable Eclipse/BWMT query inspection, specification review, and unsaved local drafts
sap-datasphere⌘5 · 🤖3 · 🛡 · 🔌MCPSAP Datasphere data modeling and management
sap-hana-cloud-data-intelligence⌘1SAP HANA Cloud Data Intelligence
sap-sac-custom-widget⌘3 · 🤖3 · 🛡SAP Analytics Cloud custom widget development
sap-sac-planning⌘3 · 🤖3 · 🛡SAP Analytics Cloud planning applications
sap-sac-scripting⌘4 · 🤖4 · 🛡 · 🔌MCPSAP Analytics Cloud scripting API
sap-sac-test-automation⌘1 · 🤖1SAP Analytics Cloud capability-gated browser and Playwright test automation
⚙️ Core Technologies (9)
PluginFeaturesDescription
sap-abap⌘1ABAP development patterns and best practices
sap-abap-cds⌘1ABAP Core Data Services (CDS) views
sap-ai-core⌘1SAP AI Core machine learning development
sap-cap-capire⌘5 · 🤖4 · 🛡 · 🔌MCP · LSPSAP Cloud Application Programming Model (CAP)
sap-cloud-sdk-ai⌘1SAP Cloud SDK for AI development
sap-cloud-sdk-ai-python⌘1SAP Cloud SDK for AI for Python (generative AI hub SDK)
sap-hana-ml⌘1SAP HANA Machine Learning (ML) library
sap-rpt1⌘2SAP-RPT-1-OSS FI/CO local tabular prediction workflow guidance
sap-sqlscript⌘4 · 🤖3 · 🛡SAP HANA SQLScript development

Repository Structure

sap-skills/
├── .agents/
│   └── plugins/
│       └── marketplace.json      # Codex marketplace catalog
│
├── .claude-plugin/
│   └── marketplace.json          # Marketplace catalog
│
└── plugins/                       # All plugins (40)
    └── [plugin-name]/
        ├── .codex-plugin/
        │   └── plugin.json       # Codex plugin manifest
        ├── agents/
        │   └── openai.yaml       # Codex plugin UI metadata
        ├── .claude-plugin/
        │   └── plugin.json       # Plugin manifest
        │
        ├── skills/
        │   └── [skill-name]/
        │       ├── SKILL.md      # Main skill content
        │       ├── agents/
        │       │   └── openai.yaml # Codex skill UI metadata
        │       ├── README.md     # Keywords for auto-discovery
        │       └── references/   # Documentation files
        │
        ├── agents/               # Optional: Specialized agents
        ├── commands/             # Optional: Slash commands
        └── hooks/                # Optional: Event hooks

Key features: 40 plugins include commands (67 total), 14 with agents (31 total), 8 with hooks, 7 with MCP integration, and 1 with LSP support. 17 plugins cross-reference related plugins.


Building New Plugins

  1. Use plugin-dev for basics (FIRST):

    • Run: /use plugin-dev:skill-development
    • Covers: YAML frontmatter, plugin structure, directory layout
  2. Add SAP-specific elements:

    • Read Contributor Guide for SDK version tracking, production testing, and marketplace cross-references
  3. Generate plugin manifests:

    ./scripts/sync-plugins.sh
  4. Test and verify:

    • Check Workflow Checklist
    • Run npm run audit:skills for capability inventory and stale verification reporting
    • Run npm run audit:effectiveness for README drift, routing, command-contract, and skill-effectiveness reporting
    • Run npm run validate:codex for Codex manifest, marketplace, and UI metadata checks
    • Run npm run validate before opening a PR

The sync script regenerates both manifest layers and the Codex UI metadata: .claude-plugin/marketplace.json and Claude manifests remain the Claude contract, while .agents/plugins/marketplace.json, .codex-plugin/plugin.json, and agents/openai.yaml provide the parallel Codex contract.

  1. Submit:
    git add plugins/your-plugin .claude-plugin/marketplace.json .agents/plugins
    git commit -m "Add your-plugin for [use case]"

Documentation

General plugin development: Use official plugin-dev skills — /use plugin-dev:skill-development, plugin-dev:plugin-structure, etc.

ResourcePurpose
Getting StartedInstallation and quick reference
Contributor GuideComprehensive development guide
Workflow ChecklistQuality verification checklist
CLAUDE.mdProject context and critical directives
CHANGELOG.mdVersion history

Contributing

Open source under GPL-3.0. Contributions welcome:

  • Report issues or suggest features via GitHub Issues
  • Submit new plugins (use plugin-dev + Contributor Guide)
  • Improve existing plugins with updated docs or references

Quality standards: Public-source and package-registry evidence is tracked per plugin. Live tenant/system validation is recorded only when evidence exists. Package versions are reviewed quarterly, and known issues are documented with sources.

Support

Maintained by: Eduard Jiglau · Email: hello@sap-ai-skills.com · Website: sap-ai-skills.com · Repository: github.com/secondsky/sap-skills · Last Updated: 2026-07-21 (v2.4.0)

GPL-3.0, read

History

Latest

v2.4.1

Features 1, Changed 2, Fixes 1

Notes
Changed
  • Bumped the coordinated repository, marketplace, plugin manifest, and skill metadata versions to 2.4.1.
  • Updated 4 drifted MCP packages to their latest versions: @ui5/mcp-server 0.2.11 → 0.2.17, hana-mcp-server 0.3.1 → 0.3.4, @sap-ux/fiori-mcp-server 1.4.0 → 1.11.7, and @mariodefe/sap-datasphere-mcp 1.2.1 → 1.5.2 (targets the first non-deprecated release since 1.3.0, lean tool profile default documented). Refreshed sap-mcp-inventory.json and sap-mcp-security.md evidence so all 5 MCP packages now report status=current.
Added
  • Wired CI audit jobs for audit-mcp-freshness.mjs (--enforce flag) and smoke-local-fixtures.mjs as PR/push-triggered workflows (mcp-freshness.yml, local-fixture-smoke.yml), and restored the CodeQL weekly schedule.
Fixed
  • Removed dead scripts that were strict subsets of other tooling: report-plugin-inventory.sh, skills-lock.json, and audit-skills.mjs (covered by audit-effectiveness.mjs).
  1. v2.4.0

    Features 10, Changed 6, Fixes 2

    Notes
    Added
    • sap-bw-query: read-only InfoProvider metadata read (bw_describe_provider now returns characteristics with dimension groups, key figures, and dimensions) through capability-gated BWMT 1.27.36 connectivity services, with a javap-verified API map reference (references/bwmt-api-map.md).
    • sap-bw-query: metadata-verified specification validation — bw_resolve_and_validate_spec accepts a connection alias, verifies every referenced characteristic/key figure against the provider, and reports blocking gaps plus readyForDraft/metadataChecked.
    • sap-bw-query: QuerySpec v1 revision 1.1 with concrete schemas for restricted/calculated/formula key figures, structures, hierarchies, conditions, exceptions, display settings (zero suppression, sign presentation, result position), and enriched variables, including cross-reference validation.
    • sap-bw-query: bw_populate_query_editor builds the confirmed draft inside the wizard-created, still-unsaved query editor (axes, key-figure structures, restricted/formula members, filters, variable bindings, conditions, exceptions, zero suppression) as one undoable editing-domain command with a per-element apply report; saving stays a human action.
    • sap-bw-query: deep query model read — bw_read_query_model (capability-gated readQueryModel bridge call plus QueryModelReader) serializes an open query's complete EMF model to a stable read-only JSON contract with a serializationIssues list, and bw_populate_query_editor now runs it automatically after a successful population to merge a non-fatal verification summary (VERIFIED/DIVERGED/UNAVAILABLE with per-element checks) that compares the confirmed spec against the live model; the human-save boundary is unchanged (saved: false).
    • sap-bw-query: shared best-practices rule engine (mcp/src/query-rules.mjs, catalog BWQ001–BWQ012) that reviews both draft specs and open queries against BW query-design rules — exposed as the read-only bw_review_query tool (reusing the readQueryModel deep read), an additive bestPractices array on bw_resolve_and_validate_spec, the references/query-design-rules.md catalog, and the /bw-query-review and /bw-query-explain commands; everything read-only with the safety contract unchanged.
    • sap-bw-query: metadata-aware optimization proposals (VARIABLE_REUSE, RESTRICTED_MEASURE_CONSOLIDATION, HIERARCHY_DISPLAY_LEVEL, AGGREGATION_CONFIRMATION, FREE_AXIS_CANDIDATE) tagged as semantics-preserving or semantics-changing.
    • sap-bw-query: live-validation runbook (docs/project/sap-bw-query-live-validation-runbook.md); execution remains pending and the verification ledger keeps live BW validation marked pending.
    • sap-bw-query: round-trip smoke that builds an in-memory query with QueryModelBuilder, reads it back with QueryModelReader, and asserts model round-trip integrity fully offline (no workbench, no save). It runs as plain Java (StandaloneSmoke) against a curated BWMT model classpath in CI after every bundle build — reliable and fast, unlike launching the full Eclipse product headless; an in-OSGi SmokeApplication variant also exists. Plus a QuerySpec template library (references/query-templates/ — plan/actual variance, YTD comparison, top-N, reconciliation totals — with references/query-templates.md) whose starting-point specs validate with no warning-severity design-rule finding.
    • sap-bw-query: the bundle builder (bundle/Build-BwStudio.ps1) now publishes the finished release ZIP and manifest (plus signature files when signed) to the local user Desktop (%USERPROFILE%\Desktop) by default after a successful build, then opens File Explorer on the output directory with the artifact selected; it refuses to auto-publish into a OneDrive-managed Desktop (warning and leaving the artifacts in the output directory), an explicit -PublishDirectory always wins, -SkipPublish disables publishing, -SkipExplorer (and automatic CI/non-interactive detection) disables the Explorer launch, and any publish or Explorer failure only warns without failing the build.
    Changed
    • Bumped the coordinated repository, marketplace, plugin manifest, and skill metadata versions to 2.4.0.
    • sap-bw-query internal bundle/plugin/MCP version 0.1.0 → 0.3.0 (0.2.0 carried the metadata read and editor population; 0.3.0 adds the deep query model read, review surfaces, and the headless smoke application; a rebuild and redeploy is required to pick up each new Eclipse plug-in and MCP server).
    • sap-bw-query: editor scans now run on the SWT display thread, fixing open-editor inspection (bw_list_queries, bw_read_query, bw_describe_provider openQueries) that previously always returned empty results from the bridge thread.
    • sap-bw-query: a successful deploy now writes two launch shortcuts to the user's visible desktop (which follows OneDrive/Known-Folder-Move redirection) so the studio — installed under the per-user, no-admin %LOCALAPPDATA%\BWAutomationStudio — is discoverable: SAP BW Automation Studio (kein Passwortspeicher).lnk (eclipse.exe -noPwdStore, recommended) and SAP BW Automation Studio (mit Passwortspeicher).lnk (no flag, so Eclipse's own secure store may remember credentials — manual login only; the automation/MCP surface still never handles passwords). Created via COM WScript.Shell (no admin, no deletion), refreshed each deploy, best-effort, and skipped in CI / when BW_STUDIO_NO_SHORTCUT is set.
    • sap-bw-query: the builder additionally drops a small .lnk to the (local) published bundle ZIP on the visible desktop, so the finished ~1 GB build is visible and one-click accessible while only a few KB sync to OneDrive instead of the whole archive.
    • sap-bw-query: the deployer (scripts/BwStudio.ps1) now handles a same-version redeploy with changed content instead of silently no-op'ing. It records the physical install folder as installDir on the activation record and resolves the runtime from it; an unchanged artifact is reused idempotently, while a same-version build with different content installs into a content-addressed sibling folder (versions/<version>+<sha>) and is activated, leaving every prior folder untouched (still strictly append-only, no deletion). Start-BwMcp.ps1, launch, status (activeInstallDir), and rollback all resolve via installDir with a fallback for older records.
    Fixed
    • sap-bw-query: QueryModelBuilder resolved BWMT EEnums via getByName(javaConstantName), but the model enums expose CamelCase names/literals (e.g. EQUAL→Equal, TOP_N→TopN, BAD1→Bad1, FOR_ALL_VALUES→forAllValues), so every lookup returned null — comparison/condition/exception operators, alert levels, sign presentation, and zero-suppression mode would all have failed to apply on a live populate. Replaced all six sites with a normalization-based resolver that matches the Java constant name, EMF name, or literal; verified end-to-end by the round-trip smoke on real EMF objects (found via the live smoke; offline JS tests never exercised the real enums).
    • sap-bw-query: the Activator no longer starts the interactive named-pipe bridge (and no longer subclasses AbstractUIPlugin) when -Dbw.automation.headless=true, so headless entry points do not drag in the workbench/bridge machinery.
  2. v2.3.2

    Changed 1, Fixes 1

    Notes
    Changed
    • Bumped the coordinated repository, marketplace, plugin manifest, and skill metadata versions to 2.3.2.
    Fixed
    • Removed redundant manifest-level hook path declarations and switched hook activation to Node-based validator entrypoints to avoid Claude Code hook loader crashes while keeping hook sidecars portable across supported operating systems.
  3. v2.3.1

    Features 6, Changed 4, Fixes 2

    Notes
    Added
    • Added sap-sac-test-automation for SAP Analytics Cloud browser and Playwright automation, including dashboard profile/scenario guidance, governance and testability notes, failure-triage artifacts, Edge/CDP patterns, Chrome DevTools MCP coverage, and /sac-test-onboard.
    • Added sap-rpt1 for SAP-RPT-1-OSS FI/CO local tabular prediction workflows, including prepare/predict commands, sample FI/CO datasets, leakage checks, governance guidance, enterprise portability notes, and source-review evidence.
    • Added CAP CDS LSP launcher support and exposed the CAP LSP configuration through generated plugin and marketplace metadata.
    • Added SAC custom widget design/runtime guidance, AI-assisted composite generation notes, CSS/styling compliance coverage, browser runtime references, and design-runtime templates.
    • Added an SAP Integration Suite HTTPS-to-SFTP iFlow package authoring reference and reusable template package.
    • Added Oracle shared review tooling and multi-harness portability documentation for using the same SAP skills across supported AI coding assistants.
    Changed
    • Bumped the coordinated repository, marketplace, plugin manifest, and skill metadata versions to 2.3.1.
    • Updated README and current-state marketplace documentation for the 37-plugin inventory: 64 commands, 31 agents, 8 hook-enabled plugins, 6 MCP-enabled plugins, and 1 LSP-enabled plugin.
    • Strengthened validation coverage for manifest drift, MCP security and environment contracts, packaging hygiene, public claims, Oracle browser safety, reference provenance, templates, command/agent contracts, hook contracts, and skill quality.
    • Improved multi-harness wording and evidence language so Claude-specific sidecars are described as portable guidance where clients do not support them natively.
    Fixed
    • Removed outdated website planning documents and stale marketplace backup artifacts from the packaged repository state.
    • Addressed SAP-RPT-1 follow-up review items, including third-party attribution cleanup.
  4. v2.3.0

    Features 8, Changed 10, Fixes 4

    Notes
    Added
    • Added 18 targeted slash commands for ABAP Cloud review, ABAP CDS model checks, AI Core deployment checks, Cloud SDK AI chat templates, BTP destination/logging/service-manager/transport diagnostics, dependency upgrade planning, Fiori generation/preview checks, HANA connection/object inspection, UI5 CLI build/troubleshooting, and UI5 Linter check/fix planning.
    • Added 2 specialist agents: fiori-app-advisor and hana-database-advisor.
    • Added 14 third-pass slash commands for API style, BTP architecture/readiness, Work Zone, BAS, CIAS, Cloud Identity Services, Integration Suite, ISA export, Job Scheduling, MDI, Data Intelligence, and HANA ML planning checks.
    • Added 4 third-pass advisory agents: api-style-reviewer, btp-platform-advisor, identity-security-advisor, and integration-flow-advisor.
    • Added the sap-dependency-security hook profile to flag unpinned executable package specs, @latest, and credential-like literals in dependency and MCP configuration files.
    • Added npm run audit:skills as a read-only per-plugin capability and verification-status report.
    • Added npm run audit:effectiveness as a read-only report for trigger quality, README drift, oversized references, command contracts, capability inventory, and next recommended artifacts.
    • Added docs/project/plugin-skills-third-pass-audit-2026-06-14.md documenting per-plugin findings, docs-only evidence, and unresolved production-only checks.
    Changed
    • Renamed dependency-upgrade to sap-dependency-security as the canonical SAP dependency security and MCP executable trust policy plugin.
    • Added SAP/MCP dependency policy coverage for MCP server pins, SAP Node tooling, Java/Maven, Gradle, Python, containers, BTP/CF/mbt, and ABAP/gCTS review workflows.
    • Exposed plugin sidecar capabilities in generated public interfaces: plugin manifests and marketplace entries now carry hooks and mcpServers when present.
    • Standardized command and agent metadata, including explicit tool scopes, input hints, trigger-rich descriptions, MCP fallback guidance, and tenant/write safety constraints.
    • Standardized all slash commands with an Output Contract and read-only/non-mutating defaults unless explicitly generation or fix-planning commands.
    • Added compact capability indexes to all plugin-local README files and routed oversized references through SKILL.md search guidance.
    • Strengthened validation for packaged artifacts, hook/MCP manifest consistency, command/agent quality, nested manifests, dependency-security hook cases, README capability drift, oversized-reference routing, command output contracts, and mutating-default safeguards.
    • Bumped the marketplace and all generated plugin manifests to version 2.3.0.
    • Documented final third-pass inventory: 35 plugins, 61 commands, 30 agents, 8 hook-enabled plugins, 6 MCP configs, and 1 LSP config.
    • Removed the local .agents mirror check from active validation; .agents/skills/dependency-upgrade remains a local mirror only.
    Fixed
    • Addressed PR #82 review findings by pinning the Trivy action template to aquasecurity/trivy-action@v0.36.0 and making its checklist valid YAML comments.
    • Updated the Python security template so uv projects use uv audit and only run pip-audit after exporting requirements.txt.
    • Corrected stale SAPUI5 and Datasphere MCP version references to match the approved exact pins.
    • Removed generated hook bytecode artifacts from packaged plugins and made validation fail on future __pycache__/, *.pyc, backup/temp, and .DS_Store artifacts.
  5. v2.2.3

    Features 7, Changed 4

    Notes
    Added
    • sap-cloud-sdk-ai-python: New plugin at plugins/sap-cloud-sdk-ai-python with comprehensive guides and orchestration support
      • 5 reference docs: getting-started-auth, langchain-guide, native-clients-guide, orchestration-guide, troubleshooting
      • 385-line SKILL.md covering SAP Cloud SDK for AI Python client
    • sap-btp-cloud-identity-services: New plugin at plugins/sap-btp-cloud-identity-services with core documentation references
      • 4 reference docs: app-integration-patterns, authorization-management, cloud-foundry-security, xsuaa-integration-guide
      • 165-line SKILL.md covering authentication, authorization, and identity patterns on BTP
    • sap-ai-core: Expanded AI Launchpad guide, generative AI hub, model providers, and orchestration modules references
    • sap-btp-best-practices: Added ai-development-best-practices.md reference (155 lines)
    • sap-cap-capire: Added comprehensive patterns for CAP integration with SAP Cloud SDK for AI including asynchronous processing guidelines
    • sap-cloud-sdk-ai: Added 59 lines of new patterns for AI integration
    • sap-btp-developer-guide: Added AI development best practices references
    Changed
    • sap-sac-scripting: Refreshed to QRC2 2026 (SAC 2026.8, OSE API v2025.20)
      • Skill version bumped 3.0.1 → 3.1.0
      • New references/whats-new-qrc2-2026.md covering Q2 2026 scripting changes
      • All 8 OSE API reference files updated from v2025.14 to v2025.20
      • Added 13 missing OSE API classes (DataUpload*, Variance*, Compass, Math, DataLabelType)
      • Reference count: 63 → 65
    • sap-sac-custom-widget: Refreshed to QRC2 2026
      • Documented missing schema properties in json-schema-reference.md
      • Expanded advanced-topics.md with 49 new lines
      • Updated README and SKILL.md
    • sap-sac-planning: Refreshed to QRC2 2026 (SAC 2026.8)
    • README.md: Restructured with universal installation via vercel-labs/skills, compacted plugin tables, added table of contents

  6. v2.2.2

    Features 5

    Notes
    Added
    • Added dependency-upgrade plugin at plugins/dependency-upgrade and hooked it into .claude-plugin/marketplace.json generation.
    • Added dependency hardening references to high-confidence dependency-using SKILLs in:
      • sap-cloud-sdk-ai
      • sap-hana-cli
      • sap-fiori-tools
      • sap-cap-capire
      • sap-datasphere
      • sap-btp-job-scheduling
      • sapui5-linter
      • sapui5
      • sap-hana-ml
      • sap-sac-scripting
      • sapui5-cli
    • Added dependency security workflow:
      • .github/workflows/dependency-security-checks.yml
      • deterministic policy enforcement for dependency-manageable skill and lockfile/PM changes
    • Replaced plugins/dependency-upgrade generator placeholder implementation with functional script:
      • .agents/dependency-upgrade/scripts/generate-dependency-upgrades.sh
    • Added dependency hardening reference notes in .agents workflow/automation docs
  7. v2.2.1

    Fixes 1

    Notes
    Fixed
    • Issue #74: Removed blocking UserPromptSubmit hooks from sap-sqlscript and sap-sac-custom-widget that were stopping unrelated prompts (e.g., "hello"). Both skills now rely on non-blocking, command-based validation hooks only.
  8. v2.1.8

    Features 1, Fixes 5

    Notes
    Added
    • Frontmatter validation infrastructure ported from claude-skills
      • scripts/validate-frontmatter.sh: comprehensive SKILL.md YAML frontmatter checker
      • .github/workflows/validate-frontmatter.yml: CI workflow (diff on PR, full scan on push)
      • .github/workflows/validate-json-schemas.yml: CI workflow with artifact upload on failure
      • .githooks/pre-push: validates changed SKILL.md files before push
      • Enhanced .githooks/pre-commit with --spec=draft7 consistency
      • Split quality-checks.yml into focused workflows
    Fixed
    • sapui5, sapui5-linter: Fixed YAML frontmatter parsing errors preventing skill installation (#63)
    • sap-abap-cds, sap-btp-cloud-platform: Fixed description overflow preventing skill installation (#65)
    • sap-btp-connectivity, sap-btp-integration-suite, sap-datasphere, sap-sac-custom-widget: Fixed description overflow (>1024 chars)
    • sapui5-linter: Fixed unclosed quote on ui5_linter_version metadata field
    • All 32 skills now pass frontmatter validation

  9. v2.1.7

    Changed 1

    Notes
    Changed
    • Hook validators hardening (sap-cap-capire, sap-datasphere, sap-sac-custom-widget, sap-sac-planning, sap-sac-scripting, sap-sqlscript, sapui5): Four CodeRabbit-identified fixes applied to all 14 validator files (validator.mjs + validator.py per plugin):
      • Added stdin error event handler in readStdin() to prevent Promise hang on I/O errors
      • Security risk messages now enumerate all detected risks with explanations, not just the first
      • Function constructor check upgraded to whitespace-tolerant regex (new\s+function\s*\()
      • WHERE clause detection upgraded to word-boundary regex (\bwhere\b) to catch newline-separated SQL

  10. v2.1.6

    Features 1, Changed 1

    Notes
    Added
    • sap-sqlscript: Added /sqlscript-setup command for automated development environment setup
      • New scripts/setup-vscode.sh detects VS Code, installs @sap/hana-sqlscript-lsp VSIX, checks HANA env vars
      • Command parses structured script output, writes/merges .vscode/settings.json, prints summary table
      • Hybrid approach: shell for deterministic steps, LLM for environment summary and settings authoring
    Changed
    • Hooks hardening: Replaced broad prompt-based Write|Edit hooks with deterministic command hooks in 7 plugins
      • Plugins: sap-cap-capire, sapui5, sap-datasphere, sap-sac-planning, sap-sac-scripting, sap-sac-custom-widget, sap-sqlscript
      • Added runtime fallback per plugin hook: Node.js primary, Python fallback, fail-open allow mode
      • Enforced structured JSON hook output and security-focused blocking (PreToolUse only); PostToolUse remains advisory
      • Goal: prevent unrelated file edits from stopping continuation in mixed-plugin workflows (issue #60)

  11. v2.1.5

    Features 1

    Notes
    Added
    • sap-sac-scripting: Added MCP integration via community sap_analytics_cloud_mcp
      • New .mcp.json connecting to SAP Analytics Cloud REST API MCP server
      • 90 tools across 11 service areas: Content, Data Export, Data Import, Multi Actions, Calendar, Content Transport, User Management, Monitoring, Schedule & Publication, Translation, Smart Query
      • OAuth 2.0 Client Credentials authentication
      • Requires local clone and build from https://github.com/secondsky/sap_analytics_cloud_mcp
      • Set SAC_MCP_PATH, SAC_BASE_URL, SAC_TOKEN_URL, SAC_CLIENT_ID, SAC_CLIENT_SECRET

  12. v2.1.4

    Features 1

    Notes
    Added
    • sap-fiori-tools: Added MCP integration via @sap-ux/fiori-mcp-server
      • New .mcp.json connecting to SAP's official Fiori MCP server
      • 5 tools: search_docs, list_fiori_apps, list_functionalities, get_functionality_details, execute_functionality
      • Semantic search across Fiori Elements, Annotations, UI5, and Fiori tools documentation
      • AI-assisted programmatic Fiori app generation and modification
      • No authentication required; requires Node.js 20+

  13. v2.1.3

    Features 2, Changed 1, Fixes 1

    Notes
    Fixed
    • Reserved words validation: Removed blocked words (official, anthropic, claude) from marketplace and plugin descriptions (fixes #56)
      • marketplace.json: Updated description to avoid CLI installation errors
      • sap-ai-core: Removed model name from description
      • sap-api-style: Changed "official SAP API Style Guide" to "the SAP API Style Guide"
      • sap-cloud-sdk-ai: Removed model name from description
    Added
    • validate-reserved-words.sh: New validation script to prevent blocked words in name/description fields
    • GitHub Actions: Added reserved words check to quality-checks.yml
    Changed
    • CLAUDE.md: Added Reserved Words Policy documentation

  14. v2.1.2

    Docs 3, Other 6

    Notes
    Changed
    Documentation Clarity
    • README.md: Updated terminology to clarify distinction between plugins (installable units) and skills (AI capabilities)

      • Changed badge from "Skills" to "Plugins" to reflect what users install
      • Added subtitle: "32 Claude Code plugins for SAP development"
      • Updated installation instructions to use "plugins" terminology
      • Clarified that "plugins provide skills that auto-activate"
    • Plugin Tables: Enhanced all 5 category tables with component visibility

      • Added Component Legend explaining Commands, Agents, and MCP features
      • Added 3 new columns (Commands | Agents | MCP) to show what each plugin offers
      • Component counts: 7 plugins with commands (28 total), 7 with agents (24 total), 4 with MCP integration
      • Clear indicators: Numbers for commands/agents, checkmark (✓) for MCP, em-dash (—) for none
    • Content Updates Throughout:

      • "Building New Skills" → "Building New Plugins" section title
      • Repository Structure: Updated to accurate component counts
      • Contributing section: Clarified plugin vs. skill terminology
      • Success Metrics: Updated "skill creation/testing" to "plugin" terminology
      • 15+ terminology updates across all sections for consistency
    Why This Update

    This release clarifies the conceptual model for users:

    • Plugins are what you install via /plugin install
    • Skills are the AI capabilities that activate automatically when you work
    • Both terms are correct in their respective contexts

    Component visibility helps users:

    • Quickly identify which plugins offer advanced features (commands, agents, MCP)
    • Understand the scope of each plugin's capabilities before installation
    • Make informed decisions based on needs (basic skills vs. advanced automation)
  15. v2.1.1

    Removed 3, Changed 6

    Notes
    Changed
    • Updated author field from "SAP Skills Maintainers" to "E.J." across all 64 plugin.json files
    • Added Claude Code-specific clarification to README.md explaining that skills follow Claude Code plugin patterns
    • Updated contributor guide to reflect manual review process
    • Removed skill-review automation references from all documentation
    • Added deprecation notices to quality-assurance.md and skills-review-progress.md
    • Updated workflow-checklist.md with manual quality review guidelines
    Removed
    • skill-review plugin - Automated quality assurance plugin removed (transitioned to manual review process)
    • Reduced total skills: 33 → 32
    • Removed from Tooling & Development category (4 → 3 skills)
  16. v2.1.0

    Breaking 5, Features 8, Changed 4, Fixes 5, Docs 8

    Notes
    Major Changes
    Plugin Structure Migration
    • BREAKING: Migrated from flat skills/ directory to plugin-based architecture
    • Repository structure changed from skills/[name]/ to plugins/[name]/skills/[name]/
    • All 33 skills successfully migrated and validated
    • Generated 91 JSON manifest files (plugin.json at plugin and skill levels)
    • Dual-level plugin architecture: plugin-level and skill-level manifests
    Added
    Advanced Plugin Features
    • Agent Support: 5 plugins now include specialized agents for autonomous task execution

      • sap-datasphere: 3 agents (datasphere-admin-helper, datasphere-integration-advisor, datasphere-modeler)
      • sap-sac-custom-widget: Custom widget development agents
      • sap-sac-planning: Planning application agents
      • sap-sac-scripting: Scripting automation agents
      • sap-sqlscript: SQL optimization and performance agents
    • Command Support: 5 plugins with slash commands for quick access

      • sap-datasphere: /datasphere-cli, /datasphere-connection-guide, /datasphere-space-template, /datasphere-view-template
      • Additional command support for SAC and SQLScript plugins
      • Instant templates and guides via command invocation
    • Hook Support: 5 plugins with validation and automation hooks

      • Pre-tool-use validation hooks
      • Post-tool-use automation hooks
      • Quality gate enforcement
      • Session lifecycle management
    • MCP Server Integration: 3 plugins with Model Context Protocol support

      • sap-cap-capire: CAP MCP server (@cap-js/mcp-server)

        • Live access to compiled CDS models
        • Semantic search for entities, services, actions, relationships
        • CAP documentation query capabilities
        • Zero configuration required
      • sap-datasphere: Datasphere MCP server (@mariodefe/sap-datasphere-mcp)

        • Direct integration with SAP Datasphere API
        • Requires authentication via environment variables
        • Access to spaces, views, models, and connections
      • sapui5: UI5 Tooling MCP server (@ui5/mcp-server)

        • UI5 project tooling integration
        • Version-aware assistance (UI5 1.120.0+)
        • Project structure awareness
    Enhanced Documentation
    • 22 new reference files across plugins providing deep-dive documentation
      • sap-datasphere (5 files):

        • best-practices-patterns.md - Design patterns and architectural guidance
        • catalog-governance.md - Data catalog and governance practices
        • cli-commands.md - Complete CLI reference
        • data-products-marketplace.md - Data product management
        • whats-new-2025.md - Latest features and updates
      • sap-sac-planning (4 files):

        • bpc-live-connection.md - BPC integration patterns
        • data-action-tracing.md - Debugging and tracing
        • seamless-planning-datasphere.md - Datasphere integration
        • value-driver-trees.md - Advanced planning scenarios
      • sap-sac-scripting (4 files):

        • chart-variance-apis.md - Chart customization APIs
        • compass-seamless-planning.md - Compass planning integration
        • data-actions-enhancements.md - Data action best practices
        • whats-new-q4-2025.md - Latest scripting features
      • sap-sqlscript (2 files):

        • glossary.md - SQLScript terminology reference
        • skill-reference-guide.md - Complete skill documentation
      • Additional template directories for rapid scaffolding

    Marketplace Enhancements
    • Cross-references: 13 plugins with comprehensive cross-skill references

      • sap-abap ↔ sap-abap-cds, sap-cap-capire, sap-fiori-tools, sap-btp-cloud-platform, sap-api-style
      • sap-abap-cds ↔ sap-abap, sap-btp-cloud-platform, sap-fiori-tools, sap-cap-capire, sap-api-style
      • sap-btp-cloud-platform ↔ sap-btp-best-practices, sap-cap-capire, sap-fiori-tools, sap-ai-core, sap-abap
      • sap-btp-best-practices ↔ sap-btp-cloud-platform, sap-btp-connectivity, sap-btp-service-manager
      • sap-fiori-tools ↔ sapui5, sap-cap-capire, sap-abap-cds, sap-btp-cloud-platform
      • sapui5 ↔ sap-fiori-tools, sap-cap-capire, sap-btp-cloud-platform
      • sap-cap-capire ↔ sap-fiori-tools, sapui5, sap-btp-cloud-platform, sap-hana-cli, sap-abap
      • sap-hana-cli ↔ sap-cap-capire, sap-btp-cloud-platform, sap-abap-cds, sap-datasphere
      • sap-ai-core ↔ sap-btp-cloud-platform, sap-cap-capire, sap-cloud-sdk-ai
      • sap-api-style ↔ sap-cap-capire, sap-fiori-tools, sap-abap, sapui5
      • sap-btp-connectivity ↔ sap-btp-cloud-platform, sap-btp-best-practices, sap-cap-capire
      • sap-btp-service-manager ↔ sap-btp-cloud-platform, sap-btp-best-practices, sap-btp-connectivity
      • sap-btp-developer-guide ↔ sap-btp-cloud-platform, sap-btp-best-practices, sap-cap-capire
      • Full cross-reference network documented in CLAUDE.md
    • Enhanced Metadata: All skills include comprehensive keywords for improved discovery

    • Category Organization: Skills organized into 5 categories (Tooling, BTP, UI, Data, Core)

    Changed
    Infrastructure Updates
    • Scripts: Updated generation and synchronization scripts

      • generate-plugin-manifests.sh: Generates plugin.json from SKILL.md YAML frontmatter
      • sync-plugins.sh: Unified version sync, manifest generation, and marketplace update
      • generate-marketplace.sh: Creates marketplace.json from all plugin.json files
      • All scripts support dry-run mode for safety
    • Version Alignment: All 33 skills synchronized to version 2.1.0 or higher

    • Directory Structure: Standardized plugin structure across all skills

    • Manifest Generation: Automated dual-level manifest creation

    Documentation Structure
    • Plugin Paths: All documentation updated to reflect plugins/[name]/skills/[name]/ structure
    • README Updates: Skill-level README files enhanced with auto-discovery keywords
    • SKILL.md Updates: Aligned with latest Anthropic skills specification
    • Cross-Linking: Improved internal documentation cross-references
    Fixed
    • Quality Checks: Removed failing quality checks workflow
    • Path References: Fixed QUICK_WORKFLOW.md link paths in documentation
    • Backup Cleanup: Removed SKILL.md.backup files after migration
    • Manifest Consistency: Ensured all plugin.json files have consistent structure
    • Marketplace Paths: Updated all source paths in marketplace.json
    Documentation
    • CLAUDE.md: Comprehensive project guidelines with critical review instructions

      • Manual review requirement (no automation scripts for refactoring)
      • Skill-review skill usage for quality audits
      • Current status documentation (33 production-ready skills)
      • Marketplace cross-references documentation
      • Quality standards and verification checklist
    • migra.md: Complete migration guide for plugin structure

      • Problem diagnosis and solution
      • Correct plugin structure examples
      • Migration steps and validation
    • README.md: Updated to reflect new plugin architecture

      • Installation instructions
      • Skill auto-trigger examples
      • 33 skills organized by category
      • Plugin structure diagram
      • Building new skills guide
      • Documentation links
    • CHANGELOG.md: Introduced this changelog following Keep-a-Changelog format


  17. v2.0.0

    Other 6

    Notes

    Earlier versions used a flat skills/ directory structure. Migration to plugin architecture completed in v2.1.0.

    Historical Structure:

    • Skills located at skills/[name]/
    • Single-level manifest files
    • Basic marketplace integration

    Migration Notes:

    • All v2.0.0 skills successfully migrated to v2.1.0 plugin structure
    • No feature regressions during migration
    • Enhanced capabilities added (agents, commands, hooks)

Agent guidance
  1. abap2UI5 for VS CodeVS Code extension to preview, activate and lint abap2UI5 apps
  2. sap-basis-opsRunbook skills for Basis operations at the OS and database layer
  3. abap-offstack-aunitAgent skill for off-stack ABAP Unit tests and an abaplint gate
  4. ARC-1 SkillsTwenty-two agent skills shipped with arc-1
  5. sapskillsAgent skills for Clean ABAP, ADT in VS Code and guardrails
  6. SuperClaude for SAPClaude Code plugin with an ABAP MCP server and write guards
  7. claude-abap-devFive ABAP workflows for Claude Code on existing MCP servers
  8. DanKromp/skillOverflowCollection of 41 agent skills, 37 for SAP development tasks
  9. sap-ai-dev-toolkitMCP proxy pinning an agent's ABAP tools to one SAP system
  10. sapcli Claude Code PluginAgents and skills that drive sapcli instead of ADT
  11. sap-odata-explorerRust CLI and desktop app for exploring SAP OData services
  12. abap-skillsSeventeen agent skills for ABAP development
  13. ABAP remote filesystemVS Code extension editing ABAP systems over ADT as a filesystem
  14. WerkbankLocal desktop workspace for AI conversations with SAP connectors
  15. claude-abap-skillsClaude Code plugins with Clean ABAP rules and templates
  16. SAP Power for KiroSAP skills for the Kiro IDE
  17. SAP Developers MCPHosted MCP server of developers.sap.com tutorials and missions
  18. claude-sap-kitClaude Code plugin adding Custom_* tools to arc-1
  19. rap-skillsRAP skills delivered branch-per-target for each deployment
  20. KlystronMCP server in ABAP inside the application server, with agent skills

Details

Sources3
sap-ai-mcp-serversdiscovered herechecked
github.com/secondsky/sap-skillstree, 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 viasap-ai-mcp-servers
first seen in the atlas
ecosystem and domainbtp, ai-and-agents
Flavors6
CAP / Node.js
“Covers CDL/CQL/CSN syntax, Node.js and Java runtimes, event handlers, OData services, and CAP plugins.” — secondsky/sap-skills — plugins/sap-cap-capire/skills/sap-cap-capire/SKILL.md, frontmatter descriptionchecked
CAP / Java
“Covers CDL/CQL/CSN syntax, Node.js and Java runtimes, event handlers, OData services, and CAP plugins.” — secondsky/sap-skills — plugins/sap-cap-capire/skills/sap-cap-capire/SKILL.md, frontmatter descriptionchecked
UI5 / Freestyle
“This skill should be used when developing SAP UI5 applications, including creating freestyle apps, Fiori Elements apps, custom controls, testing, data binding, OData integration, routing, and troubleshooting.” — secondsky/sap-skills — plugins/sapui5/skills/sapui5/SKILL.md, frontmatter descriptionchecked
UI5 / Fiori elements
“This skill should be used when developing SAP UI5 applications, including creating freestyle apps, Fiori Elements apps, custom controls, testing, data binding, OData integration, routing, and troubleshooting.” — secondsky/sap-skills — plugins/sapui5/skills/sapui5/SKILL.md, frontmatter descriptionchecked
ABAP / Standard ABAP
“Covers both classic ABAP and modern ABAP for Cloud Development patterns.” — secondsky/sap-skills — plugins/sap-abap/skills/sap-abap/SKILL.md, frontmatter descriptionchecked
Contributors4

From the repository’s contributor list, .

History in the atlas11
  1. npm, agent-plugin
  2. node, java, freestyle, fiori-elements, standard-abap, abap-cloud
  3. The maintainer publishes the plugins on their own site too: the repository's About sidebar names it as the website, and the sap-abap-cds skill carries the same address in its own frontmatter metadata. Proposed on 2026-09-14 and still unaccepted; re-read on 2026-10-15 and unchanged.
  4. fiori-elements, standard-abap, abap-cloud
  5. artifact:cap-js-mcp-server, artifact:ui5-mcp-server, artifact:sap-ux-fiori-mcp-server, artifact:hatrigt-hana-mcp-server, artifact:mariodefelipe-sap-datasphere-mcp, all conditional
  6. Claude Code, GitHub Copilot, Cursor, Codex, Gemini CLI, OpenCode
  7. Names the skills command line first, the two marketplaces beside it.
  8. Splits the evidence as the README splits it, and opens on the forty plugins.
  9. Describes the two kinds tracked where available and the live validation recorded where evidence of it exists.
  10. Triaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.
  11. First seen.
For your agent
Ref
artifact:secondsky-sap-skills
JSON
/artifacts/secondsky-sap-skills.json
MCP
Connecting an agent