data360-harmonize

Name: data360-harmonize
Author: forcedotcom

744stars272forks

How to install data360-harmonize?

forcedotcom/sf-skills/data360-harmonize

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

Installs into the current project.

Summary

Salesforce Data Cloud Harmonize phase. Use this skill when the user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. TRIGGER when: user works with DMOs, mappings, relationships, identity resolution, unified profiles,

Files · 1

View on GitHub

SKILL.md

1	# data360-harmonize: Data Cloud Harmonize Phase
2
3	Use this skill when the user needs schema harmonization and unification work: DMOs, field mappings, relationships, identity resolution, unified profiles, data graphs, or universal ID lookup.
4
5	## When This Skill Owns the Task
6
7	Use `data360-harmonize` when the work involves:
8	- `sf data360 dmo *`
9	- `sf data360 identity-resolution *`
10	- `sf data360 data-graph *`
11	- `sf data360 profile *`
12	- `sf data360 universal-id lookup`
13
14	Delegate elsewhere when the user is:
15	- still ingesting streams or building DLOs → [data360-prepare](../data360-prepare/SKILL.md)
16	- working on segment logic or calculated insights → [data360-segment](../data360-segment/SKILL.md)
17	- running SQL, describe, or search-index workflows → [data360-query](../data360-query/SKILL.md)
18
19	---
20
21	## Required Context to Gather First
22
23	Ask for or infer:
24	- source DLO and target DMO names
25	- whether the task is schema creation, mapping, IR, or graph-related
26	- target org alias
27	- whether a ruleset already exists
28	- the user’s desired unified entity model
29
30	---
31
32	## Core Operating Rules
33
34	- Inspect DMO schema before creating mappings.
35	- Run the shared readiness classifier before mutating harmonization assets: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase harmonize --json`.
36	- Prefer `dmo list --all` when browsing the catalog, but use first-page `dmo list` for fast readiness checks.
37	- Use `query describe` or `dmo get --json` instead of inventing unsupported describe flows.
38	- Treat identity resolution runs as asynchronous and verify results after execution.
39	- Keep unified-profile work separate from STDM/session tracing work.
40
41	---
42
43	## Recommended Workflow
44
45	### 1. Classify readiness for harmonize work
46	```bash
47	node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase harmonize --json
48	```
49
50	### 2. Inspect the catalog
51	```bash
52	sf data360 dmo list --all -o <org> 2>/dev/null
53	sf data360 identity-resolution list -o <org> 2>/dev/null
54	```
55
56	### 3. Inspect schema before mapping
57	```bash
58	sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null
59	sf data360 dmo get -o <org> --name ssot__Individual__dlm --json 2>/dev/null
60	```
61
62	### 4. Create or review mappings intentionally
63	```bash
64	sf data360 dmo mapping-list -o <org> --source Contact_Home__dll --target ssot__Individual__dlm 2>/dev/null
65	sf data360 dmo map-to-canonical -o <org> --dlo Contact_Home__dll --dmo ssot__Individual__dlm --dry-run 2>/dev/null
66	```
67
68	### 5. Run IR only after mappings are trustworthy
69	```bash
70	sf data360 identity-resolution create -o <org> -f ir-ruleset.json 2>/dev/null
71	sf data360 identity-resolution run -o <org> --name Main 2>/dev/null
72	```
73
74	---
75
76	## High-Signal Gotchas
77
78	- `dmo list` should usually use `--all`.
79	- Use `query describe` or `dmo get --json`; there is no `dmo describe` command.
80	- Mapping and related commands can be sensitive to API-version differences.
81	- Unified DMO names are ruleset-specific rather than generic.
82	- Data graph definitions are sensitive to field selection and relationship shape.
83	- If `dmo list` works but `identity-resolution list` is gated, treat that as a phase-specific gap rather than a full Data Cloud outage.
84
85	---
86
87	## Output Format
88
89	```text
90	Harmonize task: <dmo / mapping / relationship / ir / data-graph>
91	Source/target: <dlo → dmo or ruleset/graph names>
92	Target org: <alias>
93	Artifacts: <json files / commands>
94	Verification: <passed / partial / blocked>
95	Next step: <segment / retrieve / follow-up>
96	```
97
98	---
99
100	## References
101
102	- [../data360-orchestrate/assets/definitions/dmo.template.json](../data360-orchestrate/assets/definitions/dmo.template.json)
103	- [../data360-orchestrate/assets/definitions/mapping.template.json](../data360-orchestrate/assets/definitions/mapping.template.json)
104	- [../data360-orchestrate/assets/definitions/relationship.template.json](../data360-orchestrate/assets/definitions/relationship.template.json)
105	- [../data360-orchestrate/assets/definitions/identity-resolution.template.json](../data360-orchestrate/assets/definitions/identity-resolution.template.json)
106	- [../data360-orchestrate/assets/definitions/data-graph.template.json](../data360-orchestrate/assets/definitions/data-graph.template.json)
107	- [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feature-readiness.md)

People who liked this also viewed

6 picks

Type

data360-harmonize

744stars272forks

View on GitHub

How to install data360-harmonize?

forcedotcom/sf-skills/data360-harmonize

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# data360-harmonize: Data Cloud Harmonize Phase
2
3	Use this skill when the user needs schema harmonization and unification work: DMOs, field mappings, relationships, identity resolution, unified profiles, data graphs, or universal ID lookup.
4
5	## When This Skill Owns the Task
6
7	Use `data360-harmonize` when the work involves:
8	- `sf data360 dmo *`
9	- `sf data360 identity-resolution *`
10	- `sf data360 data-graph *`
11	- `sf data360 profile *`
12	- `sf data360 universal-id lookup`
13
14	Delegate elsewhere when the user is:
15	- still ingesting streams or building DLOs → [data360-prepare](../data360-prepare/SKILL.md)
16	- working on segment logic or calculated insights → [data360-segment](../data360-segment/SKILL.md)
17	- running SQL, describe, or search-index workflows → [data360-query](../data360-query/SKILL.md)
18
19	---
20
21	## Required Context to Gather First
22
23	Ask for or infer:
24	- source DLO and target DMO names
25	- whether the task is schema creation, mapping, IR, or graph-related
26	- target org alias
27	- whether a ruleset already exists
28	- the user’s desired unified entity model
29
30	---
31
32	## Core Operating Rules
33
34	- Inspect DMO schema before creating mappings.
35	- Run the shared readiness classifier before mutating harmonization assets: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase harmonize --json`.
36	- Prefer `dmo list --all` when browsing the catalog, but use first-page `dmo list` for fast readiness checks.
37	- Use `query describe` or `dmo get --json` instead of inventing unsupported describe flows.
38	- Treat identity resolution runs as asynchronous and verify results after execution.
39	- Keep unified-profile work separate from STDM/session tracing work.
40
41	---
42
43	## Recommended Workflow
44
45	### 1. Classify readiness for harmonize work
46	```bash
47	node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase harmonize --json
48	```
49
50	### 2. Inspect the catalog
51	```bash
52	sf data360 dmo list --all -o <org> 2>/dev/null
53	sf data360 identity-resolution list -o <org> 2>/dev/null
54	```
55
56	### 3. Inspect schema before mapping
57	```bash
58	sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null
59	sf data360 dmo get -o <org> --name ssot__Individual__dlm --json 2>/dev/null
60	```
61
62	### 4. Create or review mappings intentionally
63	```bash
64	sf data360 dmo mapping-list -o <org> --source Contact_Home__dll --target ssot__Individual__dlm 2>/dev/null
65	sf data360 dmo map-to-canonical -o <org> --dlo Contact_Home__dll --dmo ssot__Individual__dlm --dry-run 2>/dev/null
66	```
67
68	### 5. Run IR only after mappings are trustworthy
69	```bash
70	sf data360 identity-resolution create -o <org> -f ir-ruleset.json 2>/dev/null
71	sf data360 identity-resolution run -o <org> --name Main 2>/dev/null
72	```
73
74	---
75
76	## High-Signal Gotchas
77
78	- `dmo list` should usually use `--all`.
79	- Use `query describe` or `dmo get --json`; there is no `dmo describe` command.
80	- Mapping and related commands can be sensitive to API-version differences.
81	- Unified DMO names are ruleset-specific rather than generic.
82	- Data graph definitions are sensitive to field selection and relationship shape.
83	- If `dmo list` works but `identity-resolution list` is gated, treat that as a phase-specific gap rather than a full Data Cloud outage.
84
85	---
86
87	## Output Format
88
89	```text
90	Harmonize task: <dmo / mapping / relationship / ir / data-graph>
91	Source/target: <dlo → dmo or ruleset/graph names>
92	Target org: <alias>
93	Artifacts: <json files / commands>
94	Verification: <passed / partial / blocked>
95	Next step: <segment / retrieve / follow-up>
96	```
97
98	---
99
100	## References
101
102	- [../data360-orchestrate/assets/definitions/dmo.template.json](../data360-orchestrate/assets/definitions/dmo.template.json)
103	- [../data360-orchestrate/assets/definitions/mapping.template.json](../data360-orchestrate/assets/definitions/mapping.template.json)
104	- [../data360-orchestrate/assets/definitions/relationship.template.json](../data360-orchestrate/assets/definitions/relationship.template.json)
105	- [../data360-orchestrate/assets/definitions/identity-resolution.template.json](../data360-orchestrate/assets/definitions/identity-resolution.template.json)
106	- [../data360-orchestrate/assets/definitions/data-graph.template.json](../data360-orchestrate/assets/definitions/data-graph.template.json)
107	- [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feature-readiness.md)

People who liked this also viewed

6 picks

Type