Salesforce Data Cloud Act phase. TRIGGER when: user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. DO NOT TRIGGER when: the task is segment creation (use sf-datacloud-segment), data retrieval/search work (use sf-datacloud-retrieve), or STDM/session tracing (use sf-ai-agentforce-observability).
Use this skill when the user needs downstream delivery work: activations, activation targets, data actions, or pushing Data Cloud outputs into other systems.
Use sf-datacloud-act when the work involves:
sf data360 activation *sf data360 activation-target *sf data360 data-action *sf data360 data-action-target *Delegate elsewhere when the user is:
Ask for or infer:
node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json.node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json
sf data360 activation platforms -o <org> 2>/dev/null
sf data360 activation-target list -o <org> 2>/dev/null
sf data360 data-action-target list -o <org> 2>/dev/null
sf data360 activation-target create -o <org> -f target.json 2>/dev/null
sf data360 data-action-target create -o <org> -f target.json 2>/dev/null
sf data360 activation create -o <org> -f activation.json 2>/dev/null
sf data360 data-action create -o <org> -f action.json 2>/dev/null
sf data360 activation list -o <org> 2>/dev/null
sf data360 activation data -o <org> --name <activation> 2>/dev/null
CdpActivationTarget or CdpActivationExternalPlatform means the activation surface is gated for the current org/user; guide the user toward activation setup, permissions, and destination configuration instead of retrying blindly.Act task: <activation / activation-target / data-action / data-action-target>
Destination: <platform or target>
Target org: <alias>
Artifacts: <definition files / commands>
Verification: <listed / created / blocked>
Next step: <destination validation or downstream testing>