Managed event subscriptions configurator
Create, read, update or delete ManagedEventSubscription metadata for Salesforce platform event channels — with replay presets and verification checklists
- What
- Create, read, update or delete ManagedEventSubscription metadata for Salesforce platform event channels — with replay presets and verification checklists
- Cost
- Free
- Needs
- a Salesforce org with the platform event channel already created (this skill subscribes to it — it does not create it); the sf CLI (>=2.0.0) authenticated against the org; org on API v60.0+
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @forcedotcom's managed-event-subscription playbook: create, read, update and delete `ManagedEventSubscription` metadata — Salesforce's construct for durably subscribing to platform event channels with managed replay tracking. Generates exactly one file (`managedEventSubscriptions/<DeveloperName>.managedEventSubscription-meta.xml`) from a template, with clarifying questions up front (topic name in the right path format, developer name, label, `LATEST`/`EARLIEST` default and error-recovery replay presets, `RUN`/`STOP` state), a rules table that rejects the platform-reserved `PAUSE` state and read-only fields, and a verification checklist before presenting any XML — plus a destructive-deployment procedure for deletes. By @forcedotcom, listed here with credit to its creator. Honest caveats: requires the sf CLI and an org on API v60.0+; it does NOT create the event channel itself (that's a separate skill); `EARLIEST` replay on a high-volume channel can replay up to 72 hours of backlog on activation — always confirm with the user; deleting a subscription permanently discards its replay state. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Salesforce org with the platform event channel already created (this skill subscribes to it — it does not create it); the sf CLI (>=2.0.0) authenticated against the org; org on API v60.0+ Install "Managed event subscriptions configurator" for me. It teaches the agent @forcedotcom's workflow to manage ManagedEventSubscription metadata: confirm the topic name, developer name, label, default and error-recovery replay presets (LATEST/EARLIEST), and state (RUN/STOP — PAUSE is rejected); generate exactly one .managedEventSubscription-meta.xml file from the asset template; run the verification checklist before presenting it; and handle read/update/delete with the right constraints (update-constraints reference, destructive deploy for deletes, Tooling API id lookup). Repository: https://github.com/forcedotcom/sf-skills/blob/main/plugins/builder/integration/skills/integration-eventing-subscription-configure/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "integration-eventing-subscription-configure". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. confirm the event channel exists in my org and give the agent the topic name, developer name and replay preferences when invoking). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.