@salesforce/afv-skills 1.41.0 → 1.42.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/afv-skills",
-  "version": "1.41.0",
+  "version": "1.42.0",
   "description": "Salesforce skills for Agentforce Vibes",
   "license": "CC-BY-NC-4.0",
   "files": [

package/skills/dx-app-analytics-query/SKILL.md

@@ -1,12 +1,11 @@
 ---
 name: dx-app-analytics-query
-description: "ISV App Analytics metadata types — AppAnalyticsQueryRequest and AppAnalyticsSettings. Use this skill when the user asks about retrieving managed package usage data, configuring App Analytics simulation mode, querying subscriber snapshots, or understanding the AppAnalyticsQueryRequest lifecycle (New → Pending → Complete → Expired). TRIGGER when: user mentions App Analytics, AppAnalyticsQueryRequest, AppAnalyticsSettings, package usage data, subscriber analytics, ISV analytics, or simulation mode for app analytics. DO NOT TRIGGER when: the task is about standard Salesforce reports/dashboards (use reporting skills), custom SOQL on Account/Contact (use platform-soql-query), or Data Cloud query/search (use data360-query)."
+description: "ISV App Analytics metadata types — AppAnalyticsQueryRequest and AppAnalyticsSettings. Use this skill when the user asks about retrieving managed package usage data, configuring App Analytics simulation mode, querying subscriber snapshots, or understanding the AppAnalyticsQueryRequest lifecycle (New → Pending → Complete → Expired). TRIGGER when: user mentions App Analytics, AppAnalyticsQueryRequest, AppAnalyticsSettings, package usage data, subscriber analytics, ISV analytics, or simulation mode for app analytics. DO NOT TRIGGER when: the task is about standard Salesforce reports/dashboards (use reporting skills), custom SOQL on Account/Contact (use platform-soql-query)."
 metadata:
   cliTools:
     - tool: ["sf"]
       semver: ">=2.0.0"
   relatedSkills:
-    - "data360-query"
     - "platform-metadata-deploy"
     - "platform-soql-query"
   version: "1.0"
@@ -29,7 +28,6 @@ Use `dx-app-analytics-query` when the work involves:
 
 Delegate elsewhere when the user is:
 - Running standard CRM SOQL queries → platform-soql-query
-- Working with Data Cloud SQL or DMOs → data360-query
 - Building reports/dashboards on standard objects → reporting skills
 - Deploying or retrieving generic metadata XML → platform-metadata-deploy / retrieving-metadata
 

package/skills/platform-dataspace-access-configure/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-dataspace-access-configure
-description: "Use this skill to configure or inspect Salesforce Data Cloud DataSpace access for permission sets. Grants dataspace-level access via MDAPI PermissionSet XML with dataspaceScopes elements, optionally grants object-level access to DMO, DLO, or CIO objects via the Object Access Grants Connect API, and inspects existing scopes via read-only PermissionSet metadata retrieval. TRIGGER when: user needs to create or update a permission set with DataSpace access, grant access to a specific dataspace, list permission sets with access to a DataSpace, configure dataAccessLevel/objectAccessLevel, add RBAC object access grants, or list/remove object access grants for a permission set + DataSpace pair. DO NOT TRIGGER when: the task is a generic permission set without dataspace access (use platform-permission-set-generate), the request is about data ingestion/streams (use data360-prepare), or the work involves creating dataspaces themselves rather than granting access to them."
+description: "Use this skill to configure or inspect Salesforce Data Cloud DataSpace access for permission sets. Grants dataspace-level access via MDAPI PermissionSet XML with dataspaceScopes elements, optionally grants object-level access to DMO, DLO, or CIO objects via the Object Access Grants Connect API, and inspects existing scopes via read-only PermissionSet metadata retrieval. TRIGGER when: user needs to create or update a permission set with DataSpace access, grant access to a specific dataspace, list permission sets with access to a DataSpace, configure dataAccessLevel/objectAccessLevel, add RBAC object access grants, or list/remove object access grants for a permission set + DataSpace pair. DO NOT TRIGGER when: the task is a generic permission set without dataspace access (use platform-permission-set-generate), the request is about data ingestion/streams, or the work involves creating dataspaces themselves rather than granting access to them."
 metadata:
   version: "1.0"
   domains: ["Platform", "Data 360"]
@@ -65,8 +65,6 @@ Trigger this skill when the user wants to:
 
 Delegate elsewhere when:
 - The permission set has no DataSpace access at all → `platform-permission-set-generate`
-- The task is creating the DataSpace itself → `data360-orchestrate`
-- The task is ingesting data or configuring streams → `data360-prepare`
 
 ---
 

package/skills/data360-activate/README.md

@@ -1,38 +0,0 @@
-# data360-activate
-
-Activation and downstream delivery workflows for Salesforce Data Cloud.
-
-## Use this skill for
-
-- activations
-- activation targets
-- data actions
-- data action targets
-- downstream platform inspection before push
-
-## Example requests
-
-```text
-"Activate this segment to the downstream platform"
-"Show me what activation targets already exist"
-"Create a data action target for this integration"
-"Help me inspect why this activation is not ready"
-```
-
-## Common commands
-
-```bash
-sf data360 activation platforms -o myorg 2>/dev/null
-sf data360 activation-target list -o myorg 2>/dev/null
-sf data360 activation list -o myorg 2>/dev/null
-sf data360 data-action-target list -o myorg 2>/dev/null
-```
-
-## References
-
-- [SKILL.md](SKILL.md)
-- [../data360-orchestrate/assets/definitions/activation-target.template.json](../data360-orchestrate/assets/definitions/activation-target.template.json)
-- [../data360-orchestrate/assets/definitions/activation.template.json](../data360-orchestrate/assets/definitions/activation.template.json)
-- [../data360-orchestrate/assets/definitions/data-action-target.template.json](../data360-orchestrate/assets/definitions/data-action-target.template.json)
-- [../data360-orchestrate/assets/definitions/data-action.template.json](../data360-orchestrate/assets/definitions/data-action.template.json)
-- [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)

package/skills/data360-activate/SKILL.md

@@ -1,127 +0,0 @@
----
-name: data360-activate
-description: "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 Cloud audiences and data. DO NOT TRIGGER when: the task is segment creation (use data360-segment), data retrieval/search work (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-connect"
-    - "data360-orchestrate"
-    - "data360-prepare"
-    - "data360-query"
-    - "data360-segment"
-  version: "1.0"
-  domains: ["Data 360"]
----
-
-# data360-activate: 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 `data360-activate` 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 → [data360-segment](../data360-segment/SKILL.md)
-- exploring query/search or search indexes → [data360-query](../data360-query/SKILL.md)
-- setting up base connections or ingestion → [data360-connect](../data360-connect/SKILL.md), [data360-prepare](../data360-prepare/SKILL.md)
-
----
-
-## 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 ../data360-orchestrate/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
-```bash
-node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json
-```
-
-### 2. Inspect destinations first
-```bash
-sf data360 activation platforms -o <org> 2>/dev/null
-sf data360 activation-target list -o <org> 2>/dev/null
-sf data360 data-action-target list -o <org> 2>/dev/null
-```
-
-### 3. Create the destination before the activation
-```bash
-sf data360 activation-target create -o <org> -f target.json 2>/dev/null
-sf data360 data-action-target create -o <org> -f target.json 2>/dev/null
-```
-
-### 4. Create the activation or data action
-```bash
-sf data360 activation create -o <org> -f activation.json 2>/dev/null
-sf data360 data-action create -o <org> -f action.json 2>/dev/null
-```
-
-### 5. Verify downstream readiness
-```bash
-sf data360 activation list -o <org> 2>/dev/null
-sf data360 activation data -o <org> --name <activation> 2>/dev/null
-```
-
----
-
-## 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
-
-```text
-Act task: <activation / activation-target / data-action / data-action-target>
-Destination: <platform or target>
-Target org: <alias>
-Artifacts: <definition files / commands>
-Verification: <listed / created / blocked>
-Next step: <destination validation or downstream testing>
-```
-
----
-
-## References
-
-- [../data360-orchestrate/assets/definitions/activation-target.template.json](../data360-orchestrate/assets/definitions/activation-target.template.json)
-- [../data360-orchestrate/assets/definitions/activation.template.json](../data360-orchestrate/assets/definitions/activation.template.json)
-- [../data360-orchestrate/assets/definitions/data-action-target.template.json](../data360-orchestrate/assets/definitions/data-action-target.template.json)
-- [../data360-orchestrate/assets/definitions/data-action.template.json](../data360-orchestrate/assets/definitions/data-action.template.json)
-- [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)
-- [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feature-readiness.md)

package/skills/data360-connect/README.md

@@ -1,57 +0,0 @@
-# data360-connect
-
-Connection and connector workflows for Salesforce Data Cloud.
-
-## Use this skill for
-
-- listing available connector types
-- inspecting configured connections
-- testing a connection
-- browsing source objects, databases, fields, and uploaded schemas
-- preparing connector JSON for Snowflake, SharePoint Unstructured, and Ingestion API sources
-- preparing for stream creation
-
-## Key reminders
-
-- `connection list` requires `--connector-type`
-- `connection test` may need `--connector-type` for non-Salesforce name resolution
-- use `connection schema-upsert` after creating an Ingestion API connector
-- start with inspection before mutation
-- use `2>/dev/null` to suppress linked-plugin warning noise
-- some connector types can be created by API while downstream stream creation still requires UI flow
-
-## Example requests
-
-```text
-"Show me which Data Cloud connections already exist in this org"
-"Test my Snowflake Data Cloud connection"
-"What source objects are available on this Salesforce connector?"
-"Help me create an Ingestion API connector and upload its schema"
-"Set up a SharePoint Unstructured connection for document ingestion"
-```
-
-## Common commands
-
-```bash
-sf data360 connection connector-list -o myorg 2>/dev/null
-sf data360 connection list -o myorg --connector-type SalesforceDotCom 2>/dev/null
-sf data360 connection get -o myorg --name SalesforceDotCom_Home 2>/dev/null
-sf data360 connection test -o myorg --name Snowflake_Demo --connector-type SNOWFLAKE 2>/dev/null
-sf data360 connection schema-get -o myorg --name <connector-id> 2>/dev/null
-sf data360 connection create -o myorg -f examples/connections/heroku-postgres.json 2>/dev/null
-sf data360 connection schema-upsert -o myorg --name <connector-id> -f examples/connections/ingest-api-schema.json 2>/dev/null
-```
-
-## Example payloads
-
-- [examples/connections/heroku-postgres.json](examples/connections/heroku-postgres.json)
-- [examples/connections/redshift.json](examples/connections/redshift.json)
-- [examples/connections/sharepoint-unstructured.json](examples/connections/sharepoint-unstructured.json)
-- [examples/connections/snowflake-connection.json](examples/connections/snowflake-connection.json)
-- [examples/connections/ingest-api-connection.json](examples/connections/ingest-api-connection.json)
-- [examples/connections/ingest-api-schema.json](examples/connections/ingest-api-schema.json)
-
-## References
-
-- [SKILL.md](SKILL.md)
-- [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)

package/skills/data360-connect/SKILL.md

@@ -1,163 +0,0 @@
----
-name: data360-connect
-description: "Salesforce Data Cloud Connect phase. Use this skill when the user manages Data Cloud connections, connectors, or sets up a new source system. TRIGGER when: user manages Data Cloud connections, connectors, connector metadata, tests a connection, browses source objects or databases, or sets up a new source system. DO NOT TRIGGER when: the task is about data streams or DLOs (use data360-prepare), DMOs or identity resolution (use data360-harmonize), retrieval/search (use data360-query), or STDM telemetry (use agentforce-observe)."
-metadata:
-  cliTools:
-    - tool: ["node"]
-      semver: ">=18.0.0"
-    - tool: ["sf"]
-      semver: ">=2.0.0"
-  relatedSkills:
-    - "agentforce-observe"
-    - "data360-harmonize"
-    - "data360-orchestrate"
-    - "data360-prepare"
-    - "data360-query"
-  version: "1.0"
-  domains: ["Data 360"]
----
-
-# data360-connect: Data Cloud Connect Phase
-
-Use this skill when the user needs **source connection work**: connector discovery, connection metadata, connection testing, source-object browsing, connector schema inspection, or connector-specific setup payloads for external sources.
-
-## When This Skill Owns the Task
-
-Use `data360-connect` when the work involves:
-- `sf data360 connection *`
-- connector catalog inspection
-- connection creation, update, test, or delete
-- browsing source objects, fields, databases, or schemas
-- identifying connector types already in use
-- preparing connector definitions for Snowflake, SharePoint Unstructured, or Ingestion API sources
-
-Delegate elsewhere when the user is:
-- creating data streams or DLOs → [data360-prepare](../data360-prepare/SKILL.md)
-- creating DMOs, mappings, IR rulesets, or data graphs → [data360-harmonize](../data360-harmonize/SKILL.md)
-- writing Data Cloud SQL or search-index workflows → [data360-query](../data360-query/SKILL.md)
-
----
-
-## Required Context to Gather First
-
-Ask for or infer:
-- target org alias
-- connector type or source system
-- whether the user wants inspection only or live mutation
-- connection name or ID if one already exists
-- whether credentials are already configured outside the CLI
-- whether the user also expects stream creation right after connection setup
-- whether the source is a database, an unstructured document source, or an Ingestion API feed
-
----
-
-## Core Operating Rules
-
-- Verify the plugin runtime first; see [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md).
-- Run the shared readiness classifier before mutating connections: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase connect --json`.
-- Prefer read-only discovery before connection creation.
-- Suppress linked-plugin warning noise with `2>/dev/null` for standard usage.
-- Remember that `connection list` requires `--connector-type`.
-- For `connection test`, pass `--connector-type` when resolving a non-Salesforce connection by name.
-- Discover existing connector types from streams first when the org is unfamiliar.
-- Use curated example payloads before inventing connector-specific credentials or parameters.
-- For connector types outside the curated examples, inspect a known-good UI-created connection via REST before building JSON.
-- Do not promise API-based stream creation for every connector type just because connection creation succeeds.
-
----
-
-## Recommended Workflow
-
-### 1. Classify readiness for connect work
-```bash
-node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase connect --json
-```
-
-### 2. Discover connector types
-```bash
-sf data360 connection connector-list -o <org> 2>/dev/null
-sf data360 data-stream list -o <org> 2>/dev/null
-```
-
-### 3. Inspect connections by type
-```bash
-sf data360 connection list -o <org> --connector-type SalesforceDotCom 2>/dev/null
-sf data360 connection list -o <org> --connector-type REDSHIFT 2>/dev/null
-sf data360 connection list -o <org> --connector-type SNOWFLAKE 2>/dev/null
-```
-
-### 4. Inspect a specific connection or uploaded schema
-```bash
-sf data360 connection get -o <org> --name <connection> 2>/dev/null
-sf data360 connection objects -o <org> --name <connection> 2>/dev/null
-sf data360 connection fields -o <org> --name <connection> 2>/dev/null
-sf data360 connection schema-get -o <org> --name <connection-id> 2>/dev/null
-```
-
-### 5. Test or create only after discovery
-```bash
-sf data360 connection test -o <org> --name <connection> --connector-type <type> 2>/dev/null
-sf data360 connection create -o <org> -f connection.json 2>/dev/null
-```
-
-### 6. Start from curated example payloads for external connectors
-Use the phase-owned examples before inventing a payload from scratch:
-- `examples/connections/heroku-postgres.json`
-- `examples/connections/redshift.json`
-- `examples/connections/sharepoint-unstructured.json`
-- `examples/connections/snowflake-connection.json`
-- `examples/connections/ingest-api-connection.json`
-- `examples/connections/ingest-api-schema.json`
-
-Typical Ingestion API setup flow:
-```bash
-sf data360 connection create -o <org> -f examples/connections/ingest-api-connection.json 2>/dev/null
-sf data360 connection schema-upsert -o <org> --name <connector-id> -f examples/connections/ingest-api-schema.json 2>/dev/null
-sf data360 connection schema-get -o <org> --name <connector-id> 2>/dev/null
-```
-
-### 7. Discover payload fields for unknown connector types
-Create one in the UI, then inspect it directly:
-```bash
-sf api request rest "/services/data/v66.0/ssot/connections/<id>" -o <org>
-```
-
----
-
-## High-Signal Gotchas
-
-- `connection list` has no true global "list all" mode; query by connector type.
-- The connector catalog name and connection connector type are not always the same label.
-- `connection test` may need `--connector-type` for name resolution when the source is not a default Salesforce connector.
-- An empty connection list usually means "enabled but not configured yet", not "feature disabled".
-- Heroku Postgres, Redshift, Snowflake, SharePoint Unstructured, and Ingestion API all use different credential and parameter shapes; reuse the curated examples instead of guessing.
-- SharePoint Unstructured uses `clientId`, `clientSecret`, and `tokenEndpoint` in the `credentials` array and does not require a `parameters` array.
-- Snowflake uses key-pair auth and can often be created through the API, but downstream stream creation can still remain UI-only.
-- Ingestion API connector setup is incomplete until `connection schema-upsert` has uploaded the object schema.
-- Some external connector credential setup still depends on UI-side configuration or external-system permissions.
-
----
-
-## Output Format
-
-```text
-Connect task: <inspect / create / test / update>
-Connector type: <SalesforceDotCom / REDSHIFT / SNOWFLAKE / SPUnstructuredDocument / IngestApi / ...>
-Target org: <alias>
-Commands: <key commands run>
-Verification: <passed / partial / blocked>
-Next step: <prepare phase or connector follow-up>
-```
-
----
-
-## References
-
-- [examples/connections/heroku-postgres.json](examples/connections/heroku-postgres.json)
-- [examples/connections/redshift.json](examples/connections/redshift.json)
-- [examples/connections/sharepoint-unstructured.json](examples/connections/sharepoint-unstructured.json)
-- [examples/connections/snowflake-connection.json](examples/connections/snowflake-connection.json)
-- [examples/connections/ingest-api-connection.json](examples/connections/ingest-api-connection.json)
-- [examples/connections/ingest-api-schema.json](examples/connections/ingest-api-schema.json)
-- [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)
-- [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feature-readiness.md)

package/skills/data360-connect/examples/connections/heroku-postgres.json

@@ -1,15 +0,0 @@
-{
-  "connectorType": "HerokuPostgres",
-  "label": "My Heroku DB",
-  "name": "My_Heroku_DB",
-  "method": "Ingress",
-  "credentials": [
-    { "paramName": "credentialType", "value": "UsernamePasswordAuthentication" },
-    { "paramName": "user", "value": "<HEROKU_DB_USER>" },
-    { "paramName": "password", "value": "<HEROKU_DB_PASSWORD>" }
-  ],
-  "parameters": [
-    { "paramName": "jdbc_connection_url", "value": "<HOST>:<PORT>" },
-    { "paramName": "DATABASE", "value": "<DATABASE_NAME>" }
-  ]
-}

package/skills/data360-connect/examples/connections/ingest-api-connection.json

@@ -1,5 +0,0 @@
-{
-  "connectorType": "IngestApi",
-  "label": "<CONNECTOR_LABEL>",
-  "name": "<CONNECTOR_NAME>"
-}

package/skills/data360-connect/examples/connections/ingest-api-schema.json

@@ -1,31 +0,0 @@
-{
-  "schemas": [
-    {
-      "label": "<OBJECT_NAME>",
-      "name": "<OBJECT_NAME>",
-      "schemaType": "IngestApi",
-      "fields": [
-        {
-          "name": "Id",
-          "label": "Id",
-          "dataType": "Text"
-        },
-        {
-          "name": "Name",
-          "label": "Name",
-          "dataType": "Text"
-        },
-        {
-          "name": "Timestamp",
-          "label": "Timestamp",
-          "dataType": "DateTime"
-        },
-        {
-          "name": "Value",
-          "label": "Value",
-          "dataType": "Number"
-        }
-      ]
-    }
-  ]
-}

package/skills/data360-connect/examples/connections/redshift.json

@@ -1,16 +0,0 @@
-{
-  "connectorType": "REDSHIFT",
-  "label": "My Redshift",
-  "name": "My_Redshift",
-  "method": "Ingress",
-  "credentials": [
-    { "paramName": "authenticationOption", "value": "usernameAndPassword" },
-    { "paramName": "username", "value": "<REDSHIFT_USER>" },
-    { "paramName": "password", "value": "<REDSHIFT_PASSWORD>" }
-  ],
-  "parameters": [
-    { "paramName": "url", "value": "<HOST>:<PORT>" },
-    { "paramName": "database", "value": "<DATABASE_NAME>" },
-    { "paramName": "hasPrivateNetworkRoute", "value": "false" }
-  ]
-}

package/skills/data360-connect/examples/connections/sharepoint-unstructured.json

@@ -1,20 +0,0 @@
-{
-  "connectorType": "SPUnstructuredDocument",
-  "label": "My SharePoint Docs",
-  "name": "My_SharePoint_Docs",
-  "method": "Ingress",
-  "credentials": [
-    {
-      "paramName": "clientId",
-      "value": "<AZURE_APP_CLIENT_ID>"
-    },
-    {
-      "paramName": "clientSecret",
-      "value": "<AZURE_APP_CLIENT_SECRET>"
-    },
-    {
-      "paramName": "tokenEndpoint",
-      "value": "https://login.microsoftonline.com/<AZURE_TENANT_ID>/oauth2/v2.0/token"
-    }
-  ]
-}

package/skills/data360-connect/examples/connections/snowflake-connection.json

@@ -1,42 +0,0 @@
-{
-  "connectorType": "SNOWFLAKE",
-  "label": "Snowflake Demo",
-  "name": "Snowflake_Demo",
-  "method": "Ingress",
-  "credentials": [
-    {
-      "paramName": "credentialType",
-      "value": "KeyPairAuthentication"
-    },
-    {
-      "paramName": "user",
-      "value": "<SNOWFLAKE_USERNAME>"
-    },
-    {
-      "paramName": "privateKey",
-      "value": "<YOUR_PRIVATE_KEY_WITHOUT_BEGIN_END_HEADERS>"
-    }
-  ],
-  "parameters": [
-    {
-      "paramName": "accountUrl",
-      "value": "https://<ORG_ID>-<ACCOUNT_ID>.snowflakecomputing.com"
-    },
-    {
-      "paramName": "database",
-      "value": "<DATABASE_NAME>"
-    },
-    {
-      "paramName": "warehouse",
-      "value": "<WAREHOUSE_NAME>"
-    },
-    {
-      "paramName": "region",
-      "value": "<AWS_REGION>"
-    },
-    {
-      "paramName": "hasPrivateNetworkRoute",
-      "value": "false"
-    }
-  ]
-}

package/skills/data360-harmonize/README.md

@@ -1,31 +0,0 @@
-# data360-harmonize
-
-Schema harmonization and unification workflows for Salesforce Data Cloud.
-
-## Use this skill for
-
-- DMOs (Data Model Objects)
-- Field mappings
-- Relationships
-- Identity resolution
-- Unified profiles
-- Data graphs
-- Universal ID lookup
-
-## Example requests
-
-```text
-"Map this DLO to ssot__Individual__dlm"
-"Help me create an identity resolution ruleset"
-"Why are unified profiles not appearing?"
-"Show me the DMO fields before I create mappings"
-```
-
-## Common commands
-
-```bash
-sf data360 dmo list --all -o myorg 2>/dev/null
-sf data360 query describe -o myorg --table ssot__Individual__dlm 2>/dev/null
-sf data360 dmo mapping-list -o myorg --source Contact_Home__dll --target ssot__Individual__dlm 2>/dev/null
-sf data360 identity-resolution list -o myorg 2>/dev/null
-```