Agent skill · forcedotcom
integration-eventing-subscription-configure
Create, read, update, and delete ManagedEventSubscription metadata in Salesforce. Use this skill for any work involving managed event subscriptions, platform event subscriptions, event channel subscribers, or .managedEventSubscription-meta.xml files. TRIGGER when: user asks to subscribe to a platform event, create a managed subscription, set up event replay, configure an event channel subscriber, update replay preset, activate or deactivate a subscription, delete a subscription, or manage ManagedEventSubscription metadata. SKIP when: user needs to create the platform event channel itself (use platform-custom-object-generate skill) or needs Flow-based event subscriptions (use automation-flow-generate skill).
What it needs
About 6k tokens when loaded.
What this skill does
Managing ManagedEventSubscription Create, read, update, and delete ManagedEventSubscription metadata — the Salesforce construct for durably subscribing to platform event channels with managed replay tracking. Scope In scope: Generating and modifying .managedEventSubscription-meta.xml files for create, read, update, and delete operations Out of scope: Creating the underlying platform event (e) channel itself; Flow-based or Apex-based event subscriptions; deploying metadata to an org Only generate one file — the .managedEventSubscription-meta.xml file. Do NOT generate the referenced platform event object or any other metadata type. --- Clarifying Questions Before generating, confirm if not already clear: What is the topic name? (see format table in references/topic-name-formats.md) What is the developer name? (required for Create — alphanumeric and underscores only, no spaces; optional for Read/Update/Delete if Id is known) What is the label (human-readable name)? What default replay preset — LATEST (default) or EARLIEST? What error recovery replay preset — LATEST (default) or EARLIEST? What should the initial state be — RUN (active) or STOP (inactive)? (default: RUN) --- Required Inputs Gather or infer before proceeding: Operation: create, read, update, or delete DeveloperName: required for Create (becomes the filename); optional for Read/Update/Delete if Id is provided instead Id: Tooling API record Id — can be used to identify the subscription for Read/Update/Delete instead of DeveloperName label: human-readable label (can include spaces) topicName: event channel path — read references/topic-name-formats.md for valid formats (platform events, change events, custom channels) defaultReplay: LATEST or EARLIEST (default: LATEST) errorRecoveryReplay: LATEST or EARLIEST (default: LATEST) state: RUN or STOP (default: RUN) — PAUSE is reserved for internal platform use and will be rejected with INVALIDINPUT version: Metadata API version (default: match org API version, e.g. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/integration-eventing-subscription-configure--f5cd59