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

sf datacloud act: Data Cloud Act Phase Use this skill when the user needs downstream delivery work : activations, activation targets, data actions, or pushing Data Cloud outputs into other systems. When This Skill Owns the Task Use sf datacloud act when the work involves: sf data360 activation sf data360 activation target sf data360 data action sf data360 data action target verifying downstream delivery setup Delegate elsewhere when the user is: still building the audience or insight → [sf datacloud segment](../sf datacloud segment/SKILL.md) exploring query/search or search indexes → [sf datacloud retrieve](../sf datacloud retrieve/SKILL.md) setting up base connections or ingestion → [sf datacloud connect](../sf datacloud connect/SKILL.md), [sf datacloud prepare](../sf datacloud prepare/SKILL.md) Required Context to Gather First Ask for or infer: target org alias destination platform or downstream system whether the segment already exists and is published whether the user needs create, inspect, update, or delete whether the task is activation focused or data action focused Core Operating Rules Verify the upstream segment or insight is healthy before creating downstream delivery assets. Run the shared readiness classifier before mutating activation assets: node ~/.claude/skills/sf datacloud/scripts/diagnose org.mjs o <org phase act json . Inspect available platforms and targets before mutating activation setup. Keep destination definitions deterministic and reusable where possible. Treat downstream credential and platform constraints as separate validation concerns. Prefer read only inspection first when the destination state is unclear. Recommended Workflow 1. Classify readiness for act work 2. Inspect destinations first 3. Create the destination before the activation 4. Create the activation or data action 5. Verify downstream readiness High Signal Gotchas Activation design depends on a healthy published upstream segment. Destination configuration usually comes before activation creation. Downstream credential and platform constraints may live outside the Data Cloud CLI alone. Read only inspection is the safest first move when the destination setup is unclear. 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. Output Format References [README.md](README.md) [../sf datacloud/assets/definitions/activation target.template.json](../sf datacloud/assets/definitions/activation target.template.json) [../sf datacloud/assets/definitions/activation.template.json](../sf datacloud/assets/definitions/activation.template.json) [../sf datacloud/assets/definitions/data action target.template.json](../sf datacloud/assets/definitions/data action target.template.json) [../sf datacloud/assets/definitions/data action.template.json](../sf datacloud/assets/definitions/data action.template.json) [../sf datacloud/UPSTREAM.md](../sf datacloud/UPSTREAM.md) [../sf datacloud/references/plugin setup.md](../sf datacloud/references/plugin setup.md) [../sf datacloud/references/feature readiness.md](../sf datacloud/references/feature readiness.md)

sf-datacloud-act