Meeting scribe. Use this skill whenever the user wants to turn a recorded meeting into follow-ups — fetch the meeting transcript, extract per-person action items, optionally find related emails, then deliver them either as 1-1 direct messages or a single summary posted to a group chat. Triggers on "meeting notes", "action items", "meeting follow-ups", "who owes what after the call", "summarize the meeting and assign tasks".

A single parameterized presales demo for SAP CX AI. Launch with "start the [industry] B2B commerce demo", "start the [portal name] demo", or all three combined — e.g. "start the pharma VeriSupply B2B commerce demo". Covers 25 industry verticals in B2B Commerce mode and a distinct Sales and Service CRM mode with 9 acts. All scenarios are high-fidelity illustrative simulations using mock data — no live SAP system is connected. Activate on any combination of industry name, portal brand, and business process in the trigger statement.

Creates Microsoft Outlook calendar reminders from plain language in any conversation. Use this skill whenever the user wants to set a reminder, schedule something, create a calendar event, or says things like "remind me", "don't let me forget", "set a reminder", "add to my calendar", "every Monday remind me", "show me my reminders", or "set up sprint reminders". Generates a standard .ics file and opens it directly in Outlook for Mac — one click to confirm and the event lands in Exchange with a popup alarm. Supports timed reminders, all-day reminders, recurring weekly reminders, team-aware events (colleague name noted in description), sprint setup (4 events in one command), and listing all upcoming reminders. Note: currently macOS only (Outlook for Mac).

Bootstrap off-stack ABAP Unit testing plus an abaplint static-analysis gate onto an abapGit-serialised ABAP repository, with no live SAP system. Use when you need to run a repo's existing ABAP Unit tests in CI (GitHub Actions) by transpiling serialised ABAP to JavaScript with the abaplint transpiler and open-abap-core and executing them on Node. Covers pinning the transpiler parse dialect to a specific SAP_BASIS release (e.g. v816), breaking a class-under-test free of heavy DDIC drag with a shim or factory seam, authoring minimal domain-less DDIC fixtures, a reproducible npm ci committed-lockfile setup, and wiring the off-stack unit-test job beside the abaplint lint job on every push and pull request. Triggers on "off-stack ABAP Unit", "transpiled ABAP Unit on Node", "abaplint transpiler CI", "run ABAP tests without a SAP system", "ABAP GitHub Actions unit tests", "abaplint new-repo bootstrap". Scope boundary is load-bearing: it verifies orchestration and pure-ABAP logic only; any class calling classic BAPIs, the database, or HTTP is shimmed and remains an on-stack ATC + ABAP Unit concern, and an off-stack green is CI-grade provenance, not an in-system verification.