Salesforce Change Data Capture — channel and metadata generator
Generate valid CDC metadata (PlatformEventChannelMember/PlatformEventChannel) for subscribing objects to change events, custom channels, enrichment fields and filters
- What
- Generate valid CDC metadata (PlatformEventChannelMember/PlatformEventChannel) for subscribing objects to change events, custom channels, enrichment fields and filters
- Cost
- Free
- Needs
- a Salesforce org with Change Data Capture enabled (right edition/permissions) and the sf CLI (>=2.0.0) installed; deployment costs/limits are your own responsibility — check the CDC Developer Guide
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @forcedotcom's official skill for wiring Salesforce Change Data Capture without memorizing metadata quirks. The agent generates only the two metadata types CDC actually accepts — `PlatformEventChannelMember` per subscribed (entity, channel) pair and `PlatformEventChannel` for custom channels — translating source objects to ChangeEvent entity names, deriving valid custom channel developer names (`__chn` suffix), adding enrichment fields and SOQL-style filter expressions, and steering clear of the many documented deploy landmines (single-underscore filenames, no `data/` channel prefix, four-element-only member XML, DateTime filters restricted to equality, no relationship traversals). It asks clarifying questions when the entity, channel, enrichments or filters are unclear, never runs the deploy itself, and delegates related work (custom objects, fields, permission sets) to sibling skills. Apache-2.0 licensed. Honest caveats: you still need a Salesforce org with the right edition/permissions plus the `sf` CLI to dry-run and deploy; pricing and CDC event limits are explicitly out of scope — check the CDC Developer Guide yourself. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Salesforce Change Data Capture is a free Muse skill, the skill for wiring Salesforce Change Data Capture without metadata quirks. It generates only the two metadata types CDC accepts, PlatformEventChannelMember per subscribed entity, channel pair, and PlatformEventChannel for custom channels, translating source objects to ChangeEvent names, deriving valid custom channel names with __chn suffix, and adding enrichment fields, SOQL-style filters.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit e5164d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Salesforce org with Change Data Capture enabled (right edition/permissions) and the sf CLI (>=2.0.0) installed; deployment costs/limits are your own responsibility — check the CDC Developer Guide Install "Salesforce Change Data Capture — channel and metadata generator" for me. It gives my agent @forcedotcom's official CDC workflow: generate valid PlatformEventChannelMember and PlatformEventChannel metadata to subscribe standard/custom objects to change events, create custom channels, add enrichment fields and filter expressions — while avoiding the documented deploy pitfalls. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/forcedotcom/sf-skills/e5164d94d7511c00fa02a5b8b60754b2361e178f/plugins/builder/integration/skills/integration-eventing-cdc-configure/SKILL.md Pinned version: install the code at commit e5164d94d7511c00fa02a5b8b60754b2361e178f exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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-cdc-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. connect the sf CLI to my org — never paste org credentials into chat; deployment is a separate step I run myself). 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- e5164d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.