activating-datacloud

activating-datacloud: 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 activating-datacloud 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 → segmenting-datacloud
exploring query/search or search indexes → retrieving-datacloud
setting up base connections or ingestion → connecting-datacloud, preparing-datacloud

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 ../orchestrating-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

node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json

2. Inspect destinations first

sf data360 activation platforms -o <org> 2>

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

activating-datacloud: 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 activating-datacloud 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 → segmenting-datacloud
exploring query/search or search indexes → retrieving-datacloud
setting up base connections or ingestion → connecting-datacloud, preparing-datacloud

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 ../orchestrating-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

node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json

2. Inspect destinations first

sf data360 activation platforms -o <org> 2>

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.

Documentation

Documentation

activating-datacloud: Data Cloud Act Phase

When This Skill Owns the Task

Required Context to Gather First

Core Operating Rules

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

Output Format

References

Documentation

activating-datacloud

Documentation

activating-datacloud: Data Cloud Act Phase

When This Skill Owns the Task

Required Context to Gather First

Core Operating Rules

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

Output Format

References