sf-datacloud-act

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: Delegate elsewhere when the user is: Ask for or infer: - sf data360 activation * - sf data360 activation-target * - sf data360 data-action * - sf data360 data-action-target * - verifying downstream delivery setup - still building the audience or insight → sf-datacloud-segment - exploring query/search or search indexes → sf-datacloud-retrieve - setting up base connections or ingestion → sf-datacloud-connect , sf-datacloud-prepare - 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 - 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 --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...