forcedotcom/sf-skills / skills/platform-policy-rule-generate
platform-policy-rule-generate
VerifiedTHE skill for creating a Data Cloud / Data Governance access policy — authors and deploys a PolicyRuleDefinitionSet + PolicyRuleDefinition pair (CRUD) covering OLS, FLS, RLS, masking/transform, and tag/classification-based access for the DATACLOUD or ALL consumer. TRIGGER when the user wants to create/write/author a Data Cloud or Data Governance policy, access policy, or policy rule, or to grant access to a Data Cloud object THROUGH A POLICY — a Data Cloud policy-create request routes here, not to the tag/classification surface. Resolves every reference via Data 360 MCP. SCOPE: Data Cloud policies only (not Security Center, DSAR, or User Access Policies). DO NOT TRIGGER to create tags/classifications, or to grant object/dataspace access via a PERMISSION SET / RBAC grant (use platform-dataspace-access-configure). For a vague object-access ask, surface both skills and ASK the permission-set way vs the policy way; if unsure the object is Data Cloud, ask which first.
references/principal-expression.md
View on GitHub# Principal Expressions
Retrieved server evidence can contain a principal attribute selected from the principal record using `SOQLTARGETLISTEXPR`:
```xml
<conditions>
<clause>WHEN</clause>
<operator>EQUALS</operator>
<policyRuleValueSet>
<valueText>EXPECTED_VALUE</valueText>
</policyRuleValueSet>
<principalExpression>
<soqlTarget>
<select>PrincipalField</select>
</soqlTarget>
<type>SOQLTARGETLISTEXPR</type>
<version>1</version>
</principalExpression>
<principalPath>SCALAR_ATTRIBUTE</principalPath>
</conditions>
```
Construction:
1. Resolve the principal field name from the target org.
2. Put that field in `<soqlTarget><select>`.
3. Use `SOQLTARGETLISTEXPR`, version `1`.
4. Put the comparison value in the right-side `policyRuleValueSet`.
5. Use the operator appropriate to the value.
`SCALAR_ATTRIBUTE` paired with `SOQLTARGETLISTEXPR` is the normal-author-mode mechanism for a principal scalar-attribute comparison (for example, `Department`, `Title`, `Division`). It is not in the shorter enum table published for other principal paths, but it is a confirmed, deployable, Policy Builder-compatible construct per DG UI source: it is how the Data Governance UI itself creates user-attribute conditions (not established by a per-shape round-trip), which is why it appears throughout retrieved API 69.0 evidence for OLS, FLS, masking, and RLS. Generate it directly in normal author mode — resolve the requested attribute against the target org's supported-attribute table in `consumer-datacloud-ui.md` and use the exact field name in `<soqlTarget><select>`. Do not replace it with `ASSIGNED_PERMISSIONS_PATH`; permission membership and scalar principal attributes are different operands.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |