Data Cloud policy rule authoring
Author PolicyRuleDefinition and PolicyRuleDefinitionSet metadata for Salesforce Data Cloud governance — ACCESS, GOVERNANCE, RECORD and TRANSFORM variants
- What
- Author PolicyRuleDefinition and PolicyRuleDefinitionSet metadata for Salesforce Data Cloud governance — ACCESS, GOVERNANCE, RECORD and TRANSFORM variants
- Cost
- Free
- Needs
- a Salesforce org with the EnforceOMatic and PolicyRuleMDAPI org permissions (Data Cloud governance); the sf CLI (>=2.0.0) authenticated against the org; target org on API v64.0+ (v66.0+ for PolicyJsonExpression conditions)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @forcedotcom's authoring guide for Salesforce Data Cloud governance policies on disk: the deployable package layout (`policyRuleDefinitions/`, `policyRuleDefinitionSets/`, `package.xml`), the full `PolicyRuleDefinition` schema, a category decision tree (category names the enforcement domain — ACCESS, GOVERNANCE, RECORD, TRANSFORM — effect names the action — Permit, Forbid, Transform — independent except for the bidirectional Transform coupling), the scope×category compatibility matrix that throws `INVALIDFORCATEGORY` when violated, ten validation guardrails, and a Data Governance Policy Builder UI-compatibility checklist (bare conjunction indices and OR-of-ENTITYTYPE clauses crash the builder on load — the skill shows the UI-safe rewrites). Ships copy-paste templates for all four variants and a three-layer correctness check: runtime enforcement, MDAPI deploy validity, UI editability. By @forcedotcom, listed here with credit to its creator. Honest caveats: gated on the `EnforceOMatic` and `PolicyRuleMDAPI` org permissions, min API v64.0 (66.0 for `PolicyJsonExpression` conditions); some shapes are not authorable via MDAPI at all (identified-guest record access, `SCALAR`/`PLURAL_ATTRIBUTE` paths need a runtime RuleProvider); the agent's user-facing text must never name internal engines or implementation internals (the skill's output-hygiene rules). Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Data Cloud policy rule authoring is a free guide from @forcedotcom for Salesforce Data Cloud policies on disk. It covers the package layout, the PolicyRuleDefinition schema, a category decision tree naming domain and action, the scope-by-category compatibility matrix that throws INVALIDFORCATEGORY when violated, ten guardrails, and a UI checklist, with copy-paste templates for all four variants and a three-layer check.
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 the EnforceOMatic and PolicyRuleMDAPI org permissions (Data Cloud governance); the sf CLI (>=2.0.0) authenticated against the org; target org on API v64.0+ (v66.0+ for PolicyJsonExpression conditions) Install "Data Cloud policy rule authoring" for me. It teaches the agent @forcedotcom's authoring workflow for PolicyRuleDefinition/PolicyRuleDefinitionSet metadata XML: pick the category first with the decision tree (ACCESS/GOVERNANCE/RECORD/TRANSFORM), lay out the bare rule from the closest copy-paste template, add WHEN/UNLESS conditions one at a time with all four anchors (clause, operator, path element, value), keep the scope×category matrix in bounds, run the UI-compatibility check (wrapping bare conjunction indices, adding the OR-of-ENTITYTYPE clause), update package.xml, and validate with a dry-run before any real deploy. Repository: https://raw.githubusercontent.com/forcedotcom/sf-skills/e5164d94d7511c00fa02a5b8b60754b2361e178f/skills/platform-policy-rule-generate/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 "platform-policy-rule-generate". 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 org has the required permissions and tell the agent which policy variant I want to author — ACCESS, GOVERNANCE, RECORD or TRANSFORM). 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.