Salesforce Data Cloud Segment phase. TRIGGER when: user creates or publishes segments, manages calculated insights, inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud. DO NOT TRIGGER when: the task is DMO/mapping/identity-resolution work (use sf-datacloud-harmonize),

sf datacloud segment: Data Cloud Segment Phase Use this skill when the user needs audience and insight work : segments, calculated insights, publish workflows, member counts, or troubleshooting Data Cloud segment SQL. When This Skill Owns the Task Use sf datacloud segment when the work involves: sf data360 segment sf data360 calculated insight segment publish workflows member counts and segment troubleshooting calculated insight execution and verification Delegate elsewhere when the user is: still building DMOs, mappings, or identity resolution → [sf datacloud harmonize](../sf datacloud harmonize/SKILL.md) activating a segment downstream → [sf datacloud act](../sf datacloud act/SKILL.md) writing read only SQL or search index queries → [sf datacloud retrieve](../sf datacloud retrieve/SKILL.md) Required Context to Gather First Ask for or infer: target org alias unified DMO or base entity name whether the user wants create, publish, inspect, or troubleshoot whether the asset is a segment or calculated insight expected success metric: member count, aggregate value, or publish status Core Operating Rules Treat Data Cloud segment SQL as distinct from CRM SOQL. Run the shared readiness classifier before mutating audience assets: node ~/.claude/skills/sf datacloud/scripts/diagnose org.mjs o <org phase segment json . Prefer reusable JSON definitions for repeatable segment and CI creation. Use api version 64.0 when segment creation behavior is unstable on newer defaults. Verify with counts or SQL after publish/run steps instead of assuming success. Use SQL joins rather than segment members when readable member details are needed. Recommended Workflow 1. Classify readiness for segment work 2. Inspect current state 3. Create with reusable JSON definitions 4. Publish or run explicitly 5. Verify with counts or SQL High Signal Gotchas Segment creation can require api version 64.0 . segment members returns opaque IDs; use SQL joins when human readable member details are needed. Segment SQL is not SOQL. Calculated insight assets and segment SQL have different limitations. Publish/run steps may kick off asynchronous work even when the command returns quickly. An empty segment or calculated insight list usually means the module is reachable but unconfigured, not unavailable. Output Format References [README.md](README.md) [../sf datacloud/assets/definitions/calculated insight.template.json](../sf datacloud/assets/definitions/calculated insight.template.json) [../sf datacloud/assets/definitions/segment.template.json](../sf datacloud/assets/definitions/segment.template.json) [../sf datacloud/references/feature readiness.md](../sf datacloud/references/feature readiness.md) [../sf datacloud/UPSTREAM.md](../sf datacloud/UPSTREAM.md)

sf-datacloud-segment