SAP Automation Pilot
/plugin marketplace add SAP/automation-pilot-agent-skills /plugin install automation-pilot-skills@automation-pilot
Creates and manages custom SAP Automation Pilot catalogs. Use when a user wants a new catalog, changes its metadata, or requests catalog deletion. Discovery owns finding commands and Inputs within catalogs.
Calls the SAP Automation Pilot REST API through the verified, prebuilt autopi CLI. Use when configuring Bearer authentication, choosing API calls, or validating request payloads. Shared CLI transport for every Automation Pilot skill.
Authors and maintains SAP Automation Pilot commands and composite automations on the tenant. Use when a user wants to create a reusable command, build an orchestration flow (HTTP calls, scripts, polling, batching, conditionals), or change an existing command's contract, executor flow, expressions, or error handling. Also use for production-readiness reviews and local-only command definitions.
Validates the configured SAP Automation Pilot connection and reports its non-secret account summary. Use when a user wants to test connectivity, confirm which tenant is configured, or inspect effective access.
Finds and evaluates existing SAP Automation Pilot catalogs, commands, child dependencies, and reusable Inputs. Use when a user wants to locate something to run, check for an existing capability before building, identify reusable building blocks, or understand a command's contract and behavior. Do not use to create, change, or execute content.
Crafts, explains, and debugs SAP Automation Pilot dynamic expressions against representative input data. Use when a user wants to write a $(...) expression or responseBodyTransformer pipeline, diagnose an expression that returns an unexpected or empty result, or build a non-trivial expression while authoring or repairing a command. Do not use for jq unrelated to Automation Pilot.
Runs SAP Automation Pilot commands and operates their executions. Use to trigger/monitor runs or webhooks, inspect execution data, diagnose failures, analyze history, request single/bulk actions or operator choices, and delete execution history. Do not use to repair command definitions or schedules that failed to trigger.
Creates and manages reusable SAP Automation Pilot Inputs that store configuration and credentials. Use when a user wants to create, change, rotate, explain, or delete an Input. Do not use merely to find an existing Input for a command.
Creates and manages SAP Automation Pilot MCP servers with simplified tool contracts and reusable Input bindings. Use to publish commands as tools, verify injected configuration and client schemas, or change server and tool availability. Command Authoring owns backing-command changes; Executions owns run diagnosis.
Clarify an SAP Automation Pilot design through a structured interview and produce an implementation-ready specification.
Schedules SAP Automation Pilot commands for one-time or recurring execution and manages existing schedules. Use when a user wants to create, inspect, explain, update, enable, disable, or delete a scheduled execution, or diagnose why a schedule did not trigger. Do not use to troubleshoot a command run that the schedule successfully created.
Validates, applies, and interprets SAP Automation Pilot tags. Use when selecting regular or feature tags, configuring priority, retention, auto-abort, or execution logging, filtering resources by tag, or interpreting tag inheritance, origin, and execution lineage from service tags.