@salesforce/afv-skills 1.41.0 → 1.42.0

package/skills/data360-harmonize/SKILL.md

@@ -1,126 +0,0 @@
----
-name: data360-harmonize
-description: "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, data graphs, or universal IDs. DO NOT TRIGGER when: the task is only about streams/DLOs (use data360-prepare), segments/insights (use data360-segment), retrieval/search (use data360-query), or STDM/session tracing (use agentforce-observe)."
-metadata:
-  cliTools:
-    - tool: ["node"]
-      semver: ">=18.0.0"
-    - tool: ["sf"]
-      semver: ">=2.0.0"
-  relatedSkills:
-    - "agentforce-observe"
-    - "data360-orchestrate"
-    - "data360-prepare"
-    - "data360-query"
-    - "data360-segment"
-  version: "1.0"
-  domains: ["Data 360"]
----
-
-# data360-harmonize: Data Cloud Harmonize Phase
-
-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.
-
-## When This Skill Owns the Task
-
-Use `data360-harmonize` when the work involves:
-- `sf data360 dmo *`
-- `sf data360 identity-resolution *`
-- `sf data360 data-graph *`
-- `sf data360 profile *`
-- `sf data360 universal-id lookup`
-
-Delegate elsewhere when the user is:
-- still ingesting streams or building DLOs → [data360-prepare](../data360-prepare/SKILL.md)
-- working on segment logic or calculated insights → [data360-segment](../data360-segment/SKILL.md)
-- running SQL, describe, or search-index workflows → [data360-query](../data360-query/SKILL.md)
-
----
-
-## Required Context to Gather First
-
-Ask for or infer:
-- source DLO and target DMO names
-- whether the task is schema creation, mapping, IR, or graph-related
-- target org alias
-- whether a ruleset already exists
-- the user’s desired unified entity model
-
----
-
-## Core Operating Rules
-
-- Inspect DMO schema before creating mappings.
-- Run the shared readiness classifier before mutating harmonization assets: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase harmonize --json`.
-- Prefer `dmo list --all` when browsing the catalog, but use first-page `dmo list` for fast readiness checks.
-- Use `query describe` or `dmo get --json` instead of inventing unsupported describe flows.
-- Treat identity resolution runs as asynchronous and verify results after execution.
-- Keep unified-profile work separate from STDM/session tracing work.
-
----
-
-## Recommended Workflow
-
-### 1. Classify readiness for harmonize work
-```bash
-node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase harmonize --json
-```
-
-### 2. Inspect the catalog
-```bash
-sf data360 dmo list --all -o <org> 2>/dev/null
-sf data360 identity-resolution list -o <org> 2>/dev/null
-```
-
-### 3. Inspect schema before mapping
-```bash
-sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null
-sf data360 dmo get -o <org> --name ssot__Individual__dlm --json 2>/dev/null
-```
-
-### 4. Create or review mappings intentionally
-```bash
-sf data360 dmo mapping-list -o <org> --source Contact_Home__dll --target ssot__Individual__dlm 2>/dev/null
-sf data360 dmo map-to-canonical -o <org> --dlo Contact_Home__dll --dmo ssot__Individual__dlm --dry-run 2>/dev/null
-```
-
-### 5. Run IR only after mappings are trustworthy
-```bash
-sf data360 identity-resolution create -o <org> -f ir-ruleset.json 2>/dev/null
-sf data360 identity-resolution run -o <org> --name Main 2>/dev/null
-```
-
----
-
-## High-Signal Gotchas
-
-- `dmo list` should usually use `--all`.
-- Use `query describe` or `dmo get --json`; there is no `dmo describe` command.
-- Mapping and related commands can be sensitive to API-version differences.
-- Unified DMO names are ruleset-specific rather than generic.
-- Data graph definitions are sensitive to field selection and relationship shape.
-- If `dmo list` works but `identity-resolution list` is gated, treat that as a phase-specific gap rather than a full Data Cloud outage.
-
----
-
-## Output Format
-
-```text
-Harmonize task: <dmo / mapping / relationship / ir / data-graph>
-Source/target: <dlo → dmo or ruleset/graph names>
-Target org: <alias>
-Artifacts: <json files / commands>
-Verification: <passed / partial / blocked>
-Next step: <segment / retrieve / follow-up>
-```
-
----
-
-## References
-
-- [../data360-orchestrate/assets/definitions/dmo.template.json](../data360-orchestrate/assets/definitions/dmo.template.json)
-- [../data360-orchestrate/assets/definitions/mapping.template.json](../data360-orchestrate/assets/definitions/mapping.template.json)
-- [../data360-orchestrate/assets/definitions/relationship.template.json](../data360-orchestrate/assets/definitions/relationship.template.json)
-- [../data360-orchestrate/assets/definitions/identity-resolution.template.json](../data360-orchestrate/assets/definitions/identity-resolution.template.json)
-- [../data360-orchestrate/assets/definitions/data-graph.template.json](../data360-orchestrate/assets/definitions/data-graph.template.json)
-- [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feature-readiness.md)

package/skills/data360-orchestrate/README.md

@@ -1,120 +0,0 @@
-# data360-orchestrate
-
-Salesforce Data Cloud skill family for sf-skills. This is the **cross-phase orchestrator** for community-driven Data Cloud workflows built around the external `sf data360` CLI runtime.
-
-## What this skill is for
-
-Use `data360-orchestrate` when the task spans multiple Data Cloud phases:
-- connection + ingestion + harmonization setup
-- troubleshooting a Data Cloud pipeline end to end
-- managing data spaces or data kits
-- deciding which specialized Data Cloud skill to use next
-
-## What this skill is *not*
-
-- It does **not** vendor or fork the external Data Cloud CLI plugin.
-- It does **not** use MCP.
-- It does **not** replace phase-specific skills once the problem is localized.
-- It does **not** cover STDM/session tracing/parquet analysis; use `agentforce-observe` for that.
-
-## Data Cloud skill family
-
-| Skill | Purpose |
-|---|---|
-| [data360-orchestrate](../data360-orchestrate/) | Orchestrator, data spaces, data kits, cross-phase workflows |
-| [data360-connect](../data360-connect/) | Connections, connectors, source discovery |
-| [data360-prepare](../data360-prepare/) | Data streams, DLOs, transforms, DocAI |
-| [data360-harmonize](../data360-harmonize/) | DMOs, mappings, identity resolution, data graphs |
-| [data360-segment](../data360-segment/) | Segments, calculated insights |
-| [data360-activate](../data360-activate/) | Activations, activation targets, data actions |
-| [data360-query](../data360-query/) | SQL, async query, vector search, search indexes |
-
-## Runtime model
-
-This family assumes:
-- Salesforce CLI (`sf`)
-- a Data Cloud-enabled org
-- the external community `sf data360` plugin linked into `sf`
-
-See [references/plugin-setup.md](references/plugin-setup.md).
-
-## Deterministic helpers included
-
-| Path | Purpose |
-|---|---|
-| [scripts/bootstrap-plugin.sh](scripts/bootstrap-plugin.sh) | Clone/update the community plugin, compile it, and link it into `sf` |
-| [scripts/verify-plugin.sh](scripts/verify-plugin.sh) | Check that the runtime is available before starting Data Cloud work |
-| [scripts/diagnose-org.mjs](scripts/diagnose-org.mjs) | Classify org readiness by phase before mutating Data Cloud assets |
-| [references/feature-readiness.md](references/feature-readiness.md) | Map high-signal errors and feature gates to concrete next steps |
-| [assets/definitions/](assets/definitions/) | Generic JSON templates for repeatable Data Cloud definition files |
-
-## Generic templates
-
-The family includes reusable starting points for:
-- data streams
-- DMOs
-- mappings
-- identity resolution rulesets
-- segments
-- search indexes
-
-These are intentionally generic and should be adapted to the target org.
-
-## Quick start
-
-### 1. Verify the runtime
-
-```bash
-bash ./scripts/verify-plugin.sh
-# or with an org alias
-bash ./scripts/verify-plugin.sh myorg
-```
-
-The helper treats `sf data360 doctor` as advisory and falls back to additional read-only smoke checks when an org is only partially provisioned.
-
-### 2. Diagnose feature readiness before mutating
-
-```bash
-node ./scripts/diagnose-org.mjs -o myorg --json
-# optional retrieve-plane probe, only when you know the table is real
-node ./scripts/diagnose-org.mjs -o myorg --phase retrieve --describe-table MyDMO__dlm --json
-```
-
-Use the diagnose helper to distinguish between:
-- feature-gated modules
-- empty-but-enabled modules
-- query-plane issues
-- runtime/auth problems
-
-### 3. Bootstrap the plugin if needed
-
-```bash
-python3 ~/.claude/sf-skills-install.py --with-datacloud-runtime
-# or run the helper script directly
-bash ./scripts/bootstrap-plugin.sh
-```
-
-### 4. Start with read-only inspection
-
-```bash
-sf data360 man
-sf data360 doctor -o myorg 2>/dev/null
-sf data360 dmo list -o myorg 2>/dev/null
-sf data360 segment list -o myorg 2>/dev/null
-sf data360 activation platforms -o myorg 2>/dev/null
-```
-
-## Common examples
-
-```text
-"Set up a Customer 360 proof of concept in Data Cloud"
-"Troubleshoot why my unified profiles are not increasing"
-"I need to figure out whether this issue is in mappings, identity resolution, or segment SQL"
-"Show me how to inspect data spaces and data kits for this org"
-```
-
-## References
-
-- [SKILL.md](SKILL.md) - Orchestrator guidance
-- [references/plugin-setup.md](references/plugin-setup.md) - Plugin install and verification
-- [references/feature-readiness.md](references/feature-readiness.md) - Readiness classification and setup guidance

package/skills/data360-orchestrate/SKILL.md

@@ -1,263 +0,0 @@
----
-name: data360-orchestrate
-description: "Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use agentforce-observe), standard CRM SOQL (use platform-soql-query), or Apex implementation (use platform-apex-generate)."
-metadata:
-  cliTools:
-    - tool: ["curl"]
-      semver: ">=7.0.0"
-    - tool: ["git"]
-      semver: ">=2.0.0"
-    - tool: ["node"]
-      semver: ">=18.0.0"
-    - tool: ["npx"]
-      semver: ">=9.0.0"
-    - tool: ["python3"]
-      semver: ">=3.10.0"
-    - tool: ["sf"]
-      semver: ">=2.0.0"
-    - tool: ["yarn"]
-      semver: ">=1.22.0"
-  relatedSkills:
-    - "agentforce-observe"
-    - "automation-flow-generate"
-    - "data360-activate"
-    - "data360-connect"
-    - "data360-harmonize"
-    - "data360-prepare"
-    - "data360-query"
-    - "data360-segment"
-    - "platform-apex-generate"
-    - "platform-custom-field-generate"
-    - "platform-custom-object-generate"
-    - "platform-data-manage"
-    - "platform-metadata-deploy"
-    - "platform-soql-query"
-  version: "1.0"
-  domains: ["Data 360"]
----
-
-# data360-orchestrate: Salesforce Data Cloud Orchestrator
-
-Use this skill when the user needs **product-level Data Cloud workflow guidance** rather than a single isolated command family: pipeline setup, cross-phase troubleshooting, data spaces, data kits, or deciding whether a task belongs in Connect, Prepare, Harmonize, Segment, Act, or Retrieve.
-
-This skill intentionally follows sf-skills house style while using the external `sf data360` command surface as the runtime. The plugin is **not vendored into this repo**.
-
----
-
-## When This Skill Owns the Task
-
-Use `data360-orchestrate` when the work involves:
-- multi-phase Data Cloud setup or remediation
-- data spaces (`sf data360 data-space *`)
-- data kits (`sf data360 data-kit *`)
-- health checks (`sf data360 doctor`)
-- CRM-to-unified-profile pipeline design
-- deciding how to move from ingestion → harmonization → segmentation → activation
-- cross-phase troubleshooting where the root cause is not yet clear
-
-Delegate to a phase-specific skill when the user is focused on one area:
-
-| Phase | Use this skill | Typical scope |
-|---|---|---|
-| Connect | [data360-connect](../data360-connect/SKILL.md) | connections, connectors, source discovery |
-| Prepare | [data360-prepare](../data360-prepare/SKILL.md) | data streams, DLOs, transforms, DocAI |
-| Harmonize | [data360-harmonize](../data360-harmonize/SKILL.md) | DMOs, mappings, identity resolution, data graphs |
-| Segment | [data360-segment](../data360-segment/SKILL.md) | segments, calculated insights |
-| Act | [data360-activate](../data360-activate/SKILL.md) | activations, activation targets, data actions |
-| Retrieve | [data360-query](../data360-query/SKILL.md) | SQL, search indexes, vector search, async query |
-
-Delegate outside the family when the user is:
-- extracting Session Tracing / STDM telemetry → [agentforce-observe](../agentforce-observe/SKILL.md)
-- writing CRM SOQL only → [platform-soql-query](../platform-soql-query/SKILL.md)
-- loading CRM source data → [platform-data-manage](../platform-data-manage/SKILL.md)
-- creating missing CRM schema → [platform-custom-object-generate](../platform-custom-object-generate/SKILL.md) or [platform-custom-field-generate](../platform-custom-field-generate/SKILL.md)
-- implementing downstream Apex or Flow logic → [platform-apex-generate](../platform-apex-generate/SKILL.md), [automation-flow-generate](../automation-flow-generate/SKILL.md)
-
----
-
-## Required Context to Gather First
-
-Ask for or infer:
-- target org alias
-- whether the plugin is already installed and linked
-- whether the user wants design guidance, read-only inspection, or live mutation
-- data sources involved: CRM objects, external databases, file ingestion, knowledge, etc.
-- desired outcome: unified profiles, segments, activations, vector search, analytics, or troubleshooting
-- whether the user is working in the default data space or a custom one
-- whether the org has already been classified with `scripts/diagnose-org.mjs`
-- which command family is failing today, if any
-
-If plugin availability or org readiness is uncertain, start with:
-- [references/plugin-setup.md](references/plugin-setup.md)
-- [references/feature-readiness.md](references/feature-readiness.md)
-- `scripts/verify-plugin.sh`
-- `scripts/diagnose-org.mjs`
-- `scripts/bootstrap-plugin.sh`
-
----
-
-## Core Operating Rules
-
-- Use the external `sf data360` plugin runtime; do **not** reimplement or vendor the command layer.
-- Prefer the smallest phase-specific skill once the task is localized.
-- Run readiness classification before mutation-heavy work. Prefer `scripts/diagnose-org.mjs` over guessing from one failing command.
-- For `sf data360` commands, suppress linked-plugin warning noise with `2>/dev/null` unless the stderr output is needed for debugging.
-- Distinguish **Data Cloud SQL** from CRM SOQL.
-- Do **not** treat `sf data360 doctor` as a full-product readiness check; the current upstream command only checks the search-index surface.
-- Do **not** treat `query describe` as a universal tenant probe; only use it with a known DMO/DLO table after broader readiness is confirmed.
-- Preserve Data Cloud-specific API-version workarounds when they matter.
-- Prefer generic, reusable JSON definition files over org-specific workshop payloads.
-
----
-
-## Recommended Workflow
-
-### 1. Verify the runtime and auth
-Confirm:
-- `sf` is installed
-- the community Data Cloud plugin is linked
-- the target org is authenticated
-
-Recommended checks:
-```bash
-sf data360 man
-sf org display -o <alias>
-bash ./scripts/verify-plugin.sh <alias>
-```
-
-Treat `sf data360 doctor` as a broad health signal, not the sole gate. On partially provisioned orgs it can fail even when read-only command families like connectors, DMOs, or segments still work.
-
-### 2. Classify readiness before changing anything
-Run the shared classifier first:
-```bash
-node ./scripts/diagnose-org.mjs -o <org> --json
-```
-
-Only use a query-plane probe after you know the table name is real:
-```bash
-node ./scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json
-```
-
-Use the classifier to distinguish:
-- empty-but-enabled modules
-- feature-gated modules
-- query-plane issues
-- runtime/auth failures
-
-### 3. Discover existing state with read-only commands
-Use targeted inspection after classification:
-```bash
-sf data360 doctor -o <org> 2>/dev/null
-sf data360 data-space list -o <org> 2>/dev/null
-sf data360 data-stream list -o <org> 2>/dev/null
-sf data360 dmo list -o <org> 2>/dev/null
-sf data360 identity-resolution list -o <org> 2>/dev/null
-sf data360 segment list -o <org> 2>/dev/null
-sf data360 activation platforms -o <org> 2>/dev/null
-```
-
-### 4. Localize the phase
-Route the task:
-- source/connector issue → Connect
-- ingestion/DLO/stream issue → Prepare
-- mapping/IR/unified profile issue → Harmonize
-- audience or insight issue → Segment
-- downstream push issue → Act
-- SQL/search/index issue → Retrieve
-
-### 5. Choose deterministic artifacts when possible
-Prefer JSON definition files and repeatable scripts over one-off manual steps. Generic templates live in:
-- `assets/definitions/data-stream.template.json`
-- `assets/definitions/dmo.template.json`
-- `assets/definitions/mapping.template.json`
-- `assets/definitions/relationship.template.json`
-- `assets/definitions/identity-resolution.template.json`
-- `assets/definitions/data-graph.template.json`
-- `assets/definitions/calculated-insight.template.json`
-- `assets/definitions/segment.template.json`
-- `assets/definitions/activation-target.template.json`
-- `assets/definitions/activation.template.json`
-- `assets/definitions/data-action-target.template.json`
-- `assets/definitions/data-action.template.json`
-- `assets/definitions/search-index.template.json`
-
-### 6. Verify after each phase
-Typical verification:
-- stream/DLO exists
-- DMO/mapping exists
-- identity resolution run completed
-- unified records or segment counts look correct
-- activation/search index status is healthy
-
----
-
-## High-Signal Gotchas
-
-- `connection list` requires `--connector-type`.
-- `dmo list --all` is useful when you need the full catalog, but first-page `dmo list` is often enough for readiness checks and much faster.
-- Segment creation may need `--api-version 64.0`.
-- `segment members` returns opaque IDs; use SQL joins for human-readable details.
-- `sf data360 doctor` can fail on partially provisioned orgs even when some read-only commands still work; fall back to targeted smoke checks.
-- `query describe` errors such as `Couldn't find CDP tenant ID` or `DataModelEntity ... not found` are query-plane clues, not automatic proof that the whole product is disabled.
-- Many long-running jobs are asynchronous in practice even when the command returns quickly.
-- Some Data Cloud operations still require UI setup outside the CLI runtime.
-
----
-
-## Output Format
-
-When finishing, report in this order:
-1. **Task classification**
-2. **Runtime status**
-3. **Readiness classification**
-4. **Phase(s) involved**
-5. **Commands or artifacts used**
-6. **Verification result**
-7. **Next recommended step**
-
-Suggested shape:
-
-```text
-Data Cloud task: <setup / inspect / troubleshoot / migrate>
-Runtime: <plugin ready / missing / partially verified>
-Readiness: <ready / ready_empty / partial / feature_gated / blocked>
-Phases: <connect / prepare / harmonize / segment / act / retrieve>
-Artifacts: <json files, commands, scripts>
-Verification: <passed / partial / blocked>
-Next step: <next phase, setup guidance, or cross-skill handoff>
-```
-
----
-
-## Cross-Skill Integration
-
-| Need | Delegate to | Reason |
-|---|---|---|
-| load or clean CRM source data | [platform-data-manage](../platform-data-manage/SKILL.md) | seed or fix source records before ingestion |
-| create missing CRM schema | [platform-custom-object-generate](../platform-custom-object-generate/SKILL.md), [platform-custom-field-generate](../platform-custom-field-generate/SKILL.md) | Data Cloud expects existing objects/fields |
-| deploy permissions or bundles | [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md) | environment preparation |
-| write Apex against Data Cloud outputs | [platform-apex-generate](../platform-apex-generate/SKILL.md) | code implementation |
-| Flow automation after segmentation/activation | [automation-flow-generate](../automation-flow-generate/SKILL.md) | declarative orchestration |
-| session tracing / STDM / parquet analysis | [agentforce-observe](../agentforce-observe/SKILL.md) | different Data Cloud use case |
-
----
-
-## Reference Map
-
-### Start here
-- [references/plugin-setup.md](references/plugin-setup.md)
-- [references/feature-readiness.md](references/feature-readiness.md)
-
-### Phase skills
-- [data360-connect](../data360-connect/SKILL.md)
-- [data360-prepare](../data360-prepare/SKILL.md)
-- [data360-harmonize](../data360-harmonize/SKILL.md)
-- [data360-segment](../data360-segment/SKILL.md)
-- [data360-activate](../data360-activate/SKILL.md)
-- [data360-query](../data360-query/SKILL.md)
-
-### Deterministic helpers
-- [scripts/bootstrap-plugin.sh](scripts/bootstrap-plugin.sh)
-- [scripts/verify-plugin.sh](scripts/verify-plugin.sh)
-- [scripts/diagnose-org.mjs](scripts/diagnose-org.mjs)
-- [assets/definitions/](assets/definitions/)

package/skills/data360-orchestrate/assets/definitions/activation-target.template.json

@@ -1,5 +0,0 @@
-{
-  "developerName": "CRM_Target",
-  "displayName": "CRM Target",
-  "description": "Example activation target definition for a downstream destination"
-}

package/skills/data360-orchestrate/assets/definitions/activation.template.json

@@ -1,7 +0,0 @@
-{
-  "developerName": "High_Value_Customers_Activation",
-  "displayName": "High Value Customers Activation",
-  "description": "Example activation linking a published segment to a destination target",
-  "segmentName": "High_Value_Customers",
-  "activationTargetName": "CRM_Target"
-}

package/skills/data360-orchestrate/assets/definitions/calculated-insight.template.json

@@ -1,7 +0,0 @@
-{
-  "developerName": "Lifetime_Value",
-  "displayName": "Lifetime Value",
-  "description": "Example calculated insight over an order-style DMO",
-  "definitionType": "CALCULATED_METRIC",
-  "expression": "SELECT ssot__IndividualId__c, SUM(ssot__TotalAmount__c) AS total_spend FROM ssot__SalesOrder__dlm GROUP BY ssot__IndividualId__c"
-}

package/skills/data360-orchestrate/assets/definitions/data-action-target.template.json

@@ -1,5 +0,0 @@
-{
-  "developerName": "Webhook_Target",
-  "displayName": "Webhook Target",
-  "description": "Example data action target for downstream delivery"
-}

package/skills/data360-orchestrate/assets/definitions/data-action.template.json

@@ -1,5 +0,0 @@
-{
-  "developerName": "Notify_High_Value_Customer_System",
-  "displayName": "Notify High Value Customer System",
-  "description": "Example data action definition that uses a downstream data action target"
-}

package/skills/data360-orchestrate/assets/definitions/data-graph.template.json

@@ -1,21 +0,0 @@
-{
-  "developerName": "Customer_360_Graph",
-  "displayName": "Customer 360 Graph",
-  "description": "Example Data Graph rooted on a unified customer entity",
-  "sourceObject": {
-    "name": "UnifiedssotIndividualMain__dlm",
-    "type": "derived",
-    "fields": [
-      {
-        "name": "ssot__Id__c"
-      },
-      {
-        "name": "ssot__FirstName__c"
-      },
-      {
-        "name": "ssot__LastName__c"
-      }
-    ],
-    "relatedObjects": []
-  }
-}

package/skills/data360-orchestrate/assets/definitions/data-stream.template.json

@@ -1,55 +0,0 @@
-{
-  "name": "Customer_Stream",
-  "label": "Customer Stream",
-  "datasource": "SalesforceDotCom_Home",
-  "datastreamType": "CONNECTORSFRAMEWORK",
-  "connectorInfo": {
-    "connectorType": "SalesforceDotCom",
-    "connectorDetails": {
-      "name": "SalesforceDotCom_Home",
-      "sourceObject": "Custom_Object__c"
-    }
-  },
-  "dataLakeObjectInfo": {
-    "label": "Customer",
-    "name": "Customer__dll",
-    "category": "Profile",
-    "dataspaceInfo": [
-      {
-        "name": "Default"
-      }
-    ],
-    "dataLakeFieldInputRepresentations": [
-      {
-        "name": "Id",
-        "label": "Record ID",
-        "dataType": "Text",
-        "isPrimaryKey": true
-      },
-      {
-        "name": "External_Id_c",
-        "label": "External ID",
-        "dataType": "Text",
-        "isPrimaryKey": false
-      }
-    ]
-  },
-  "sourceFields": [
-    {
-      "name": "Id",
-      "dataType": "Text"
-    },
-    {
-      "name": "External_Id__c",
-      "dataType": "Text"
-    }
-  ],
-  "mappings": [],
-  "refreshConfig": {
-    "isAccelerationEnabled": true,
-    "refreshMode": "UPSERT",
-    "frequency": {
-      "frequencyType": "HOURLY"
-    }
-  }
-}

package/skills/data360-orchestrate/assets/definitions/dmo.template.json

@@ -1,17 +0,0 @@
-{
-  "developerName": "Customer_Profile__dlm",
-  "label": "Customer Profile",
-  "category": "Profile",
-  "fields": [
-    {
-      "name": "External_Id_c__c",
-      "label": "External ID",
-      "type": "Text"
-    },
-    {
-      "name": "Preferred_Tier_c__c",
-      "label": "Preferred Tier",
-      "type": "Text"
-    }
-  ]
-}

package/skills/data360-orchestrate/assets/definitions/identity-resolution.template.json

@@ -1,30 +0,0 @@
-{
-  "label": "Main",
-  "description": "Generic identity resolution ruleset using customer identifiers and contact points",
-  "configurationType": "individual",
-  "rulesetId": "main",
-  "doesRunAutomatically": false,
-  "matchRules": [
-    {
-      "label": "Exact Email",
-      "criteria": [
-        {
-          "entityName": "ssot__ContactPointEmail__dlm",
-          "fieldName": "ssot__EmailAddress__c",
-          "matchMethodType": "exactnormalized",
-          "caseSensitiveMatch": false,
-          "shouldMatchOnBlank": false
-        }
-      ]
-    }
-  ],
-  "reconciliationRules": [
-    {
-      "entityName": "ssot__Individual__dlm",
-      "ruleType": "lastupdated",
-      "shouldIgnoreEmptyValue": true,
-      "sources": [],
-      "fields": []
-    }
-  ]
-}