data360-activate

Name: data360-activate
Author: forcedotcom

744stars272forks

How to install data360-activate?

forcedotcom/sf-skills/data360-activate

$npx -y skills add forcedotcom/sf-skills --skill data360-activate

Installs into the current project.

Summary

Salesforce Data Cloud Act phase. Use this skill when the user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. TRIGGER when: user manages activations, activation targets, data actions, or downstream delivery of Data C

Files · 1

View on GitHub

SKILL.md

1	# data360-activate: Data Cloud Act Phase
2
3	Use this skill when the user needs downstream delivery work: activations, activation targets, data actions, or pushing Data Cloud outputs into other systems.
4
5	## When This Skill Owns the Task
6
7	Use `data360-activate` when the work involves:
8	- `sf data360 activation *`
9	- `sf data360 activation-target *`
10	- `sf data360 data-action *`
11	- `sf data360 data-action-target *`
12	- verifying downstream delivery setup
13
14	Delegate elsewhere when the user is:
15	- still building the audience or insight → [data360-segment](../data360-segment/SKILL.md)
16	- exploring query/search or search indexes → [data360-query](../data360-query/SKILL.md)
17	- setting up base connections or ingestion → [data360-connect](../data360-connect/SKILL.md), [data360-prepare](../data360-prepare/SKILL.md)
18
19	---
20
21	## Required Context to Gather First
22
23	Ask for or infer:
24	- target org alias
25	- destination platform or downstream system
26	- whether the segment already exists and is published
27	- whether the user needs create, inspect, update, or delete
28	- whether the task is activation-focused or data-action-focused
29
30	---
31
32	## Core Operating Rules
33
34	- Verify the upstream segment or insight is healthy before creating downstream delivery assets.
35	- Run the shared readiness classifier before mutating activation assets: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json`.
36	- Inspect available platforms and targets before mutating activation setup.
37	- Keep destination definitions deterministic and reusable where possible.
38	- Treat downstream credential and platform constraints as separate validation concerns.
39	- Prefer read-only inspection first when the destination state is unclear.
40
41	---
42
43	## Recommended Workflow
44
45	### 1. Classify readiness for act work
46	```bash
47	node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json
48	```
49
50	### 2. Inspect destinations first
51	```bash
52	sf data360 activation platforms -o <org> 2>/dev/null
53	sf data360 activation-target list -o <org> 2>/dev/null
54	sf data360 data-action-target list -o <org> 2>/dev/null
55	```
56
57	### 3. Create the destination before the activation
58	```bash
59	sf data360 activation-target create -o <org> -f target.json 2>/dev/null
60	sf data360 data-action-target create -o <org> -f target.json 2>/dev/null
61	```
62
63	### 4. Create the activation or data action
64	```bash
65	sf data360 activation create -o <org> -f activation.json 2>/dev/null
66	sf data360 data-action create -o <org> -f action.json 2>/dev/null
67	```
68
69	### 5. Verify downstream readiness
70	```bash
71	sf data360 activation list -o <org> 2>/dev/null
72	sf data360 activation data -o <org> --name <activation> 2>/dev/null
73	```
74
75	---
76
77	## High-Signal Gotchas
78
79	- Activation design depends on a healthy published upstream segment.
80	- Destination configuration usually comes before activation creation.
81	- Downstream credential and platform constraints may live outside the Data Cloud CLI alone.
82	- Read-only inspection is the safest first move when the destination setup is unclear.
83	- `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.
84
85	---
86
87	## Output Format
88
89	```text
90	Act task: <activation / activation-target / data-action / data-action-target>
91	Destination: <platform or target>
92	Target org: <alias>
93	Artifacts: <definition files / commands>
94	Verification: <listed / created / blocked>
95	Next step: <destination validation or downstream testing>
96	```
97
98	---
99
100	## References
101
102	- [../data360-orchestrate/assets/definitions/activation-target.template.json](../data360-orchestrate/assets/definitions/activation-target.template.json)
103	- [../data360-orchestrate/assets/definitions/activation.template.json](../data360-orchestrate/assets/definitions/activation.template.json)
104	- [../data360-orchestrate/assets/definitions/data-action-target.template.json](../data360-orchestrate/assets/definitions/data-action-target.template.json)
105	- [../data360-orchestrate/assets/definitions/data-action.template.json](../data360-orchestrate/assets/definitions/data-action.template.json)
106	- [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)
107	- [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feat

People who liked this also viewed

6 picks

Type

data360-activate

744stars272forks

View on GitHub

How to install data360-activate?

forcedotcom/sf-skills/data360-activate

$npx -y skills add forcedotcom/sf-skills --skill data360-activate

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# data360-activate: Data Cloud Act Phase
2
3	Use this skill when the user needs downstream delivery work: activations, activation targets, data actions, or pushing Data Cloud outputs into other systems.
4
5	## When This Skill Owns the Task
6
7	Use `data360-activate` when the work involves:
8	- `sf data360 activation *`
9	- `sf data360 activation-target *`
10	- `sf data360 data-action *`
11	- `sf data360 data-action-target *`
12	- verifying downstream delivery setup
13
14	Delegate elsewhere when the user is:
15	- still building the audience or insight → [data360-segment](../data360-segment/SKILL.md)
16	- exploring query/search or search indexes → [data360-query](../data360-query/SKILL.md)
17	- setting up base connections or ingestion → [data360-connect](../data360-connect/SKILL.md), [data360-prepare](../data360-prepare/SKILL.md)
18
19	---
20
21	## Required Context to Gather First
22
23	Ask for or infer:
24	- target org alias
25	- destination platform or downstream system
26	- whether the segment already exists and is published
27	- whether the user needs create, inspect, update, or delete
28	- whether the task is activation-focused or data-action-focused
29
30	---
31
32	## Core Operating Rules
33
34	- Verify the upstream segment or insight is healthy before creating downstream delivery assets.
35	- Run the shared readiness classifier before mutating activation assets: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json`.
36	- Inspect available platforms and targets before mutating activation setup.
37	- Keep destination definitions deterministic and reusable where possible.
38	- Treat downstream credential and platform constraints as separate validation concerns.
39	- Prefer read-only inspection first when the destination state is unclear.
40
41	---
42
43	## Recommended Workflow
44
45	### 1. Classify readiness for act work
46	```bash
47	node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json
48	```
49
50	### 2. Inspect destinations first
51	```bash
52	sf data360 activation platforms -o <org> 2>/dev/null
53	sf data360 activation-target list -o <org> 2>/dev/null
54	sf data360 data-action-target list -o <org> 2>/dev/null
55	```
56
57	### 3. Create the destination before the activation
58	```bash
59	sf data360 activation-target create -o <org> -f target.json 2>/dev/null
60	sf data360 data-action-target create -o <org> -f target.json 2>/dev/null
61	```
62
63	### 4. Create the activation or data action
64	```bash
65	sf data360 activation create -o <org> -f activation.json 2>/dev/null
66	sf data360 data-action create -o <org> -f action.json 2>/dev/null
67	```
68
69	### 5. Verify downstream readiness
70	```bash
71	sf data360 activation list -o <org> 2>/dev/null
72	sf data360 activation data -o <org> --name <activation> 2>/dev/null
73	```
74
75	---
76
77	## High-Signal Gotchas
78
79	- Activation design depends on a healthy published upstream segment.
80	- Destination configuration usually comes before activation creation.
81	- Downstream credential and platform constraints may live outside the Data Cloud CLI alone.
82	- Read-only inspection is the safest first move when the destination setup is unclear.
83	- `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.
84
85	---
86
87	## Output Format
88
89	```text
90	Act task: <activation / activation-target / data-action / data-action-target>
91	Destination: <platform or target>
92	Target org: <alias>
93	Artifacts: <definition files / commands>
94	Verification: <listed / created / blocked>
95	Next step: <destination validation or downstream testing>
96	```
97
98	---
99
100	## References
101
102	- [../data360-orchestrate/assets/definitions/activation-target.template.json](../data360-orchestrate/assets/definitions/activation-target.template.json)
103	- [../data360-orchestrate/assets/definitions/activation.template.json](../data360-orchestrate/assets/definitions/activation.template.json)
104	- [../data360-orchestrate/assets/definitions/data-action-target.template.json](../data360-orchestrate/assets/definitions/data-action-target.template.json)
105	- [../data360-orchestrate/assets/definitions/data-action.template.json](../data360-orchestrate/assets/definitions/data-action.template.json)
106	- [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)
107	- [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feat

People who liked this also viewed

6 picks

Type