SAP Skills for AI Coding Assistants

37 SAP development plugins with evidence-tracked verification

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 marketplace, but the SAP skill content is written to be portable. In clients such as Codex, 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 — Install for supported AI coding assistants
• How It Works — Auto-activation examples
• Available Plugins — 37 plugins by category
• Repository Structure — Architecture overview
• Building New Plugins — Contribution workflow
• Documentation — Guides and references
• Contributing — Open source participation

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

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 (37)

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

🔧 Tooling & Development (3)

☁️ SAP BTP Platform (15)

🎨 UI Development (4)

📊 Data & Analytics (6)

⚙️ Core Technologies (9)

Repository Structure

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

Key features: 37 plugins include commands (64 total), 14 with agents (31 total), 8 with hooks, 6 with MCP integration, and 1 with LSP support. 15 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 before opening a PR

5. Submit:

   git add plugins/your-plugin .claude-plugin/marketplace.json
   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.

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