@salesforce/afv-skills 1.41.0 → 1.43.0

package/skills/data360-prepare/SKILL.md

@@ -1,203 +0,0 @@
----
-name: data360-prepare
-description: "Salesforce Data Cloud Prepare phase. Use this skill when the user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations. TRIGGER when: user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations, or asks about ingestion into Data Cloud. DO NOT TRIGGER when: the task is connection setup only (use data360-connect), DMOs and identity resolution (use data360-harmonize), or query/search work (use data360-query)."
-metadata:
-  cliTools:
-    - tool: ["node"]
-      semver: ">=18.0.0"
-    - tool: ["pip"]
-      semver: ">=21.0"
-    - tool: ["python3"]
-      semver: ">=3.10.0"
-    - tool: ["sf"]
-      semver: ">=2.0.0"
-  relatedSkills:
-    - "data360-connect"
-    - "data360-harmonize"
-    - "data360-orchestrate"
-    - "data360-query"
-  version: "1.0"
-  domains: ["Data 360"]
----
-
-# data360-prepare: Data Cloud Prepare Phase
-
-Use this skill when the user needs **ingestion and lake preparation work**: data streams, Data Lake Objects (DLOs), transforms, Document AI, unstructured ingestion, or the handoff from connector setup into a live stream.
-
-## When This Skill Owns the Task
-
-Use `data360-prepare` when the work involves:
-- `sf data360 data-stream *`
-- `sf data360 dlo *`
-- `sf data360 transform *`
-- `sf data360 docai *`
-- choosing how data should enter Data Cloud
-- rerunning or rescanning ingestion after a source update
-- preparing Ingestion API-backed streams after connector setup is complete
-
-Delegate elsewhere when the user is:
-- still creating/testing source connections → [data360-connect](../data360-connect/SKILL.md)
-- mapping to DMOs or designing IR/data graphs → [data360-harmonize](../data360-harmonize/SKILL.md)
-- querying ingested data → [data360-query](../data360-query/SKILL.md)
-
----
-
-## Required Context to Gather First
-
-Ask for or infer:
-- target org alias
-- source connection name
-- source object / dataset / document source
-- desired stream type
-- DLO naming expectations
-- whether the user is creating, updating, running, or deleting a stream
-- whether the source is CRM, a database connector, an unstructured file source, or an Ingestion API feed
-
----
-
-## Core Operating Rules
-
-- Verify the external plugin runtime before running Data Cloud commands.
-- Run the shared readiness classifier before mutating ingestion assets: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase prepare --json`.
-- Prefer inspecting existing streams and DLOs before creating new ingestion assets.
-- Suppress linked-plugin warning noise with `2>/dev/null` for normal usage.
-- Treat DLO naming and field naming as Data Cloud-specific, not CRM-native.
-- Confirm whether each dataset should be treated as `Profile`, `Engagement`, or `Other` before creating the stream.
-- Distinguish stream-level refresh from connection-level reruns when working with unstructured sources.
-- Use UI setup intentionally when initial stream or unstructured asset creation is platform-gated.
-- Hand off to Harmonize only after ingestion assets are clearly healthy.
-
----
-
-## Recommended Workflow
-
-### 1. Classify readiness for prepare work
-```bash
-node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase prepare --json
-```
-
-### 2. Inspect existing ingestion assets
-```bash
-sf data360 data-stream list -o <org> 2>/dev/null
-sf data360 dlo list -o <org> 2>/dev/null
-```
-
-### 3. Confirm the stream category before creation
-Use these rules when suggesting categories:
-
-| Category | Use for | Typical requirement |
-|---|---|---|
-| `Profile` | person/entity records | primary key |
-| `Engagement` | time-based events or interactions | primary key + event time field |
-| `Other` | reference/configuration/supporting datasets | primary key |
-
-When the source is ambiguous, ask the user explicitly whether the dataset should be treated as `Profile`, `Engagement`, or `Other`.
-
-### 4. Create or inspect streams intentionally
-```bash
-sf data360 data-stream get -o <org> --name <stream> 2>/dev/null
-sf data360 data-stream create-from-object -o <org> --object Contact --connection SalesforceDotCom_Home 2>/dev/null
-sf data360 data-stream create -o <org> -f stream.json 2>/dev/null
-sf data360 data-stream run -o <org> --name <stream> 2>/dev/null
-```
-
-### 5. Check DLO shape
-```bash
-sf data360 dlo get -o <org> --name Contact_Home__dll 2>/dev/null
-```
-
-### 6. Choose the right refresh mechanism
-Use the smaller refresh scope that matches the user goal:
-
-```bash
-sf data360 data-stream run -o <org> --name <stream> 2>/dev/null
-sf data360 connection run-existing -o <org> --name <connection-id> 2>/dev/null
-```
-
-- `data-stream run` is the closest match to a stream-level refresh or re-scan.
-- `connection run-existing` runs at the connection level and can be useful for some connector workflows, but it is not a reliable replacement for stream refresh on unstructured sources.
-- For unstructured document connectors, prefer `data-stream run` when the goal is to re-scan newly added or changed files.
-
-### 7. Handle unstructured sources deliberately
-For SharePoint-style document ingestion, a minimal unstructured DLO payload can look like:
-
-```json
-{
-  "name": "my_udlo",
-  "label": "My UDLO",
-  "category": "Directory_Table",
-  "dataSource": {
-    "sourceType": "SF_DRIVE",
-    "directoryAndFilesDetails": [
-      {
-        "dirName": "SPUnstructuredDocument/<CONNECTION_ID>/<SITE_ID>",
-        "fileName": "*"
-      }
-    ],
-    "sourceConfig": {
-      "reservedPrefix": "$dcf_content$"
-    }
-  }
-}
-```
-
-Use the UI for the first-time unstructured setup when the user needs the richer end-to-end pipeline. The UI path can seed additional document metadata fields and downstream assets that a bare CLI DLO create flow may not provision automatically.
-
-### 8. Use the local Ingestion API example for send-data workflows
-For external systems pushing records into Data Cloud:
-
-1. create the connector in [data360-connect](../data360-connect/SKILL.md)
-2. upload the schema with `sf data360 connection schema-upsert`
-3. create the stream in the UI when required
-4. send records with the local example in `examples/ingestion-api/`
-
-```bash
-cd examples/ingestion-api
-cp .env.example .env
-python3 send-data.py
-```
-
-Key details:
-- auth is a staged flow: JWT → Salesforce token → Data Cloud token
-- the ingestion endpoint uses the tenant URL, not the Salesforce instance URL
-- `202` means the payload was accepted for processing, not that records are queryable immediately
-- validation failures often surface in the Problem Records DLO family
-
-### 9. Only then move into harmonization
-Once the stream and DLO are healthy, hand off to [data360-harmonize](../data360-harmonize/SKILL.md).
-
----
-
-## High-Signal Gotchas
-
-- CRM-backed stream behavior is not the same as fully custom connector-framework ingestion.
-- `sf data360 data-stream run` and `sf data360 connection run-existing` are not interchangeable; prefer stream-level refresh for unstructured rescans.
-- `SFDC` streams sync on a platform-managed schedule; `data-stream run` is not the general control path for CRM connector refresh.
-- Some external database connectors can be created via API while stream creation still requires UI flow or org-specific browser automation. Do not promise a pure CLI stream-creation path for every connector type.
-- Initial SharePoint-style unstructured setup can be richer in the UI than in a minimal CLI DLO create flow.
-- Stream deletion can also delete the associated DLO unless the delete mode says otherwise.
-- DLO field naming differs from CRM field naming, including `__c` → `_c` transformations.
-- Query DLO record counts with Data Cloud SQL instead of assuming list output is sufficient.
-- `CdpDataStreams` means the stream module is gated for the current org/user; guide the user to provisioning/permissions review instead of retrying blindly.
-
----
-
-## Output Format
-
-```text
-Prepare task: <stream / dlo / transform / docai>
-Source: <connection + object>
-Target org: <alias>
-Artifacts: <stream names / dlo names / json definitions>
-Verification: <passed / partial / blocked>
-Next step: <harmonize or retrieve>
-```
-
----
-
-## References
-
-- [examples/ingestion-api/README.md](examples/ingestion-api/README.md)
-- [../data360-orchestrate/assets/definitions/data-stream.template.json](../data360-orchestrate/assets/definitions/data-stream.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-prepare/examples/ingestion-api/.env.example

@@ -1,8 +0,0 @@
-CONSUMER_KEY=<your consumer key from External Client App>
-CONSUMER_SECRET=<your consumer secret>
-SF_USERNAME=<your salesforce username>
-SF_LOGIN_URL=https://login.salesforce.com
-TENANT_URL=https://<tenant-id>.c360a.salesforce.com
-PRIVATE_KEY_FILE=/path/to/server.key
-CONNECTOR_NAME=Badge_Scanner
-OBJECT_NAME=Badge_Scan

package/skills/data360-prepare/examples/ingestion-api/README.md

@@ -1,48 +0,0 @@
-# Ingestion API example
-
-This folder contains a minimal, public-safe example for sending records into Salesforce Data Cloud through the Ingestion API.
-
-## What this example assumes
-
-Before running `send-data.py`, complete the connect/prepare setup steps:
-
-1. create an Ingestion API connector
-2. upload the schema with `sf data360 connection schema-upsert`
-3. create the corresponding data stream in the UI if your org requires that step
-
-Related connector definitions live in:
-- [../../../data360-connect/examples/connections/ingest-api-connection.json](../../../data360-connect/examples/connections/ingest-api-connection.json)
-- [../../../data360-connect/examples/connections/ingest-api-schema.json](../../../data360-connect/examples/connections/ingest-api-schema.json)
-
-## Prerequisites
-
-```bash
-pip install PyJWT cryptography requests
-```
-
-## Setup
-
-```bash
-cd skills/data360-prepare/examples/ingestion-api
-cp .env.example .env
-# edit .env with your values
-python3 send-data.py
-```
-
-## Environment variables
-
-- `CONSUMER_KEY` — external client app consumer key
-- `CONSUMER_SECRET` — external client app consumer secret if your auth flow needs it
-- `SF_USERNAME` — Salesforce username used for JWT auth
-- `SF_LOGIN_URL` — login host such as `https://login.salesforce.com`
-- `TENANT_URL` — Data Cloud tenant URL such as `https://<tenant>.c360a.salesforce.com`
-- `PRIVATE_KEY_FILE` — path to the JWT private key
-- `CONNECTOR_NAME` — Ingestion API connector name
-- `OBJECT_NAME` — uploaded schema object name
-
-## Notes
-
-- auth is a staged flow: JWT → Salesforce token → Data Cloud token
-- the ingestion endpoint uses the Data Cloud tenant URL, not the Salesforce instance URL
-- `202` means the payload was accepted for processing
-- validation failures often appear in the Problem Records DLO family

package/skills/data360-prepare/examples/ingestion-api/send-data.py

@@ -1,144 +0,0 @@
-#!/usr/bin/env python3
-"""
-Send data to Data Cloud through the Ingestion API.
-
-Prerequisites:
-  pip install PyJWT cryptography requests
-
-Usage:
-  1. Copy .env.example to .env and fill in your values
-  2. python3 send-data.py
-
-See README.md in this folder for setup notes.
-"""
-
-from __future__ import annotations
-
-import os
-import time
-import uuid
-from datetime import datetime, timezone
-from pathlib import Path
-
-import jwt
-import requests
-
-
-def load_env_file() -> None:
-    env_file = Path(__file__).parent / ".env"
-    if not env_file.exists():
-        return
-
-    for line in env_file.read_text().splitlines():
-        if "=" in line and not line.startswith("#"):
-            key, val = line.split("=", 1)
-            os.environ.setdefault(key.strip(), val.strip())
-
-
-load_env_file()
-
-CONSUMER_KEY = os.environ["CONSUMER_KEY"]
-SF_USERNAME = os.environ["SF_USERNAME"]
-SF_LOGIN_URL = os.environ.get("SF_LOGIN_URL", "https://login.salesforce.com")
-TENANT_URL = os.environ["TENANT_URL"]
-PRIVATE_KEY_FILE = os.environ["PRIVATE_KEY_FILE"]
-CONNECTOR_NAME = os.environ["CONNECTOR_NAME"]
-OBJECT_NAME = os.environ["OBJECT_NAME"]
-
-
-def get_cdp_token() -> str:
-    """Authenticate: JWT -> Salesforce access token -> Data Cloud token."""
-    private_key = Path(PRIVATE_KEY_FILE).read_text()
-
-    claim = {
-        "iss": CONSUMER_KEY,
-        "sub": SF_USERNAME,
-        "aud": SF_LOGIN_URL,
-        "exp": int(time.time()) + 300,
-    }
-    assertion = jwt.encode(claim, private_key, algorithm="RS256")
-
-    token_data = requests.post(
-        f"{SF_LOGIN_URL}/services/oauth2/token",
-        data={
-            "grant_type": "urn:ietf:params:oauth:grant-type:jwt-bearer",
-            "assertion": assertion,
-        },
-        timeout=60,
-    ).json()
-
-    if "access_token" not in token_data:
-        raise RuntimeError(f"Salesforce auth failed: {token_data}")
-
-    cdp_data = requests.post(
-        f"{token_data['instance_url']}/services/a360/token",
-        headers={"Content-Type": "application/x-www-form-urlencoded"},
-        data={
-            "grant_type": "urn:salesforce:grant-type:external:cdp",
-            "subject_token": token_data["access_token"],
-            "subject_token_type": "urn:ietf:params:oauth:token-type:access_token",
-        },
-        timeout=60,
-    ).json()
-
-    if "access_token" not in cdp_data:
-        raise RuntimeError(f"Data Cloud token exchange failed: {cdp_data}")
-
-    return cdp_data["access_token"]
-
-
-def send_records(cdp_token: str, records: list[dict[str, str]]) -> tuple[int, str]:
-    """Send records to the Ingestion API."""
-    url = f"{TENANT_URL}/api/v1/ingest/sources/{CONNECTOR_NAME}/{OBJECT_NAME}"
-    response = requests.post(
-        url,
-        headers={
-            "Authorization": f"Bearer {cdp_token}",
-            "Content-Type": "application/json",
-        },
-        json={"data": records},
-        timeout=60,
-    )
-    return response.status_code, response.text
-
-
-if __name__ == "__main__":
-    print("Authenticating...")
-    token = get_cdp_token()
-    print("Data Cloud token acquired")
-
-    records = [
-        {
-            "ScanId": str(uuid.uuid4()),
-            "EventId": "EVT-001",
-            "AttendeeId": "ATT-001",
-            "Scantime": datetime.now(timezone.utc).isoformat(),
-            "Room": "Main Hall",
-        },
-        {
-            "ScanId": str(uuid.uuid4()),
-            "EventId": "EVT-001",
-            "AttendeeId": "ATT-002",
-            "Scantime": datetime.now(timezone.utc).isoformat(),
-            "Room": "Workshop A",
-        },
-        {
-            "ScanId": str(uuid.uuid4()),
-            "EventId": "EVT-001",
-            "AttendeeId": "ATT-003",
-            "Scantime": datetime.now(timezone.utc).isoformat(),
-            "Room": "Workshop B",
-        },
-    ]
-
-    print(f"Sending {len(records)} records to {CONNECTOR_NAME}/{OBJECT_NAME}...")
-    status, body = send_records(token, records)
-    print(f"Response: {status} {body}")
-
-    if status == 202:
-        print("\nData accepted. Records typically appear in Data Cloud within a few minutes.")
-        print(
-            "Query with: sf data360 query sql -o <org> --sql 'SELECT * FROM \"<DLO_NAME>__dll\" LIMIT 10'"
-        )
-    else:
-        print("\nIngestion failed. Check the response above for details.")

package/skills/data360-query/README.md

@@ -1,43 +0,0 @@
-# data360-query
-
-Query and search workflows for Salesforce Data Cloud.
-
-## Use this skill for
-
-- quick SQL counts
-- paginated SQL (`sqlv2`)
-- async query lifecycles
-- table describe
-- vector search
-- hybrid search with optional prefilter
-- search index inspection and lifecycle work
-
-## Example requests
-
-```text
-"Run a Data Cloud SQL query against unified profiles"
-"Describe this Data Cloud table before I write SQL"
-"Help me troubleshoot vector search in Data Cloud"
-"Run a hybrid search with a prefilter in Data Cloud"
-"Create and inspect a search index"
-```
-
-## Common commands
-
-```bash
-sf data360 query sql -o myorg --sql 'SELECT COUNT(*) FROM "ssot__Individual__dlm"' 2>/dev/null
-sf data360 query describe -o myorg --table ssot__Individual__dlm 2>/dev/null
-sf data360 search-index list -o myorg 2>/dev/null
-sf data360 query vector -o myorg --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
-sf data360 query hybrid -o myorg --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
-```
-
-## Example payloads
-
-- [examples/search-indexes/vector-knowledge.json](examples/search-indexes/vector-knowledge.json)
-- [examples/search-indexes/hybrid-structured.json](examples/search-indexes/hybrid-structured.json)
-
-## References
-
-- [SKILL.md](SKILL.md)
-- [../data360-orchestrate/assets/definitions/search-index.template.json](../data360-orchestrate/assets/definitions/search-index.template.json)

package/skills/data360-query/SKILL.md

@@ -1,128 +0,0 @@
----
-name: data360-query
-description: "Salesforce Data Cloud Retrieve phase. Use this skill when the user runs Data Cloud SQL, async queries, vector search, search-index workflows, or metadata introspection for Data Cloud objects. TRIGGER when: user runs Data Cloud SQL, describe, async queries, vector search, search-index workflows, or metadata introspection for Data Cloud objects. DO NOT TRIGGER when: the task is standard CRM SOQL (use platform-soql-query), segment creation or calculated insight design (use data360-segment), or STDM/session tracing/parquet analysis (use agentforce-observe)."
-metadata:
-  cliTools:
-    - tool: ["node"]
-      semver: ">=18.0.0"
-    - tool: ["sf"]
-      semver: ">=2.0.0"
-  relatedSkills:
-    - "agentforce-observe"
-    - "data360-orchestrate"
-    - "data360-segment"
-    - "platform-soql-query"
-  version: "1.0"
-  domains: ["Data 360"]
----
-
-# data360-query: Data Cloud Retrieve Phase
-
-Use this skill when the user needs **query, search, and metadata introspection** for Data Cloud: sync SQL, paginated SQL, async query workflows, table describe, vector search, hybrid search, or search index operations.
-
-## When This Skill Owns the Task
-
-Use `data360-query` when the work involves:
-- `sf data360 query *`
-- `sf data360 search-index *`
-- `sf data360 metadata *`
-- `sf data360 profile *` or `sf data360 insight *` inspection
-- understanding Data Cloud SQL results or query shape
-
-Delegate elsewhere when the user is:
-- writing standard CRM SOQL only → [platform-soql-query](../platform-soql-query/SKILL.md)
-- designing segment or calculated insight assets → [data360-segment](../data360-segment/SKILL.md)
-- analyzing STDM/session tracing/parquet telemetry → [agentforce-observe](../agentforce-observe/SKILL.md)
-
----
-
-## Required Context to Gather First
-
-Ask for or infer:
-- target org alias
-- whether the user needs quick count, medium result set, large export, schema inspection, or semantic search
-- table/index name if known
-- whether the task is read-only SQL or search-index lifecycle management
-
----
-
-## Core Operating Rules
-
-- Treat Data Cloud SQL as its own query language, not SOQL.
-- Run the shared readiness classifier before relying on query/search surfaces: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --json`.
-- Use describe before guessing columns.
-- Prefer `sqlv2` or async query flows for larger result sets.
-- Use vector search or hybrid search only when the search index lifecycle is healthy.
-- Keep STDM/parquet/session-tracing workflows out of this skill family.
-
----
-
-## Recommended Workflow
-
-### 1. Classify readiness for retrieve work
-```bash
-node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --json
-# optional query-plane probe, only with a real table name
-node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json
-```
-
-### 2. Choose the smallest correct query shape
-```bash
-sf data360 query sql -o <org> --sql 'SELECT COUNT(*) FROM "ssot__Individual__dlm"' 2>/dev/null
-sf data360 query sqlv2 -o <org> --sql 'SELECT * FROM "ssot__Individual__dlm"' 2>/dev/null
-sf data360 query async-create -o <org> --sql 'SELECT * FROM "ssot__Individual__dlm"' 2>/dev/null
-```
-
-### 3. Use describe before guessing fields
-```bash
-sf data360 query describe -o <org> --table ssot__Individual__dlm 2>/dev/null
-```
-
-### 4. Use vector or hybrid search only when an index exists
-```bash
-sf data360 search-index list -o <org> 2>/dev/null
-sf data360 query vector -o <org> --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
-sf data360 query hybrid -o <org> --index Knowledge_Index --query "reset password" --limit 5 2>/dev/null
-sf data360 query hybrid -o <org> --index Insurance_Index --query "weather damage coverage" --prefilter "Type_of_Insurance__c='Home'" --limit 10 2>/dev/null
-```
-
-### 5. Reuse curated search-index examples when creating indexes
-Use the phase-owned examples instead of inventing JSON from scratch:
-- `examples/search-indexes/vector-knowledge.json`
-- `examples/search-indexes/hybrid-structured.json`
-
----
-
-## High-Signal Gotchas
-
-- Data Cloud SQL is not SOQL.
-- Table names should be double-quoted in SQL.
-- `sqlv2` is better than ad hoc OFFSET paging for medium result sets.
-- async query is preferable for large results.
-- search-index operations and vector/hybrid queries depend on the index lifecycle being healthy.
-- Hybrid search can use `--prefilter`, but only on fields configured as prefilter-capable when the search index was created.
-- HNSW index parameters are typically read-only on create; leave `userValues: []` unless the platform explicitly documents otherwise.
-- `query describe` is not a universal tenant probe; only run it with a known DMO or DLO table after broader readiness has been confirmed.
-
----
-
-## Output Format
-
-```text
-Retrieve task: <sql / sqlv2 / async / describe / vector / search-index>
-Target org: <alias>
-Target object: <table or index>
-Commands: <key commands run>
-Verification: <query rows / schema / status>
-Next step: <segment / harmonize / follow-up>
-```
-
----
-
-## References
-
-- [examples/search-indexes/vector-knowledge.json](examples/search-indexes/vector-knowledge.json)
-- [examples/search-indexes/hybrid-structured.json](examples/search-indexes/hybrid-structured.json)
-- [../data360-orchestrate/assets/definitions/search-index.template.json](../data360-orchestrate/assets/definitions/search-index.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-query/examples/search-indexes/hybrid-structured.json

@@ -1,44 +0,0 @@
-{
-  "label": "<INDEX_NAME>",
-  "developerName": "<INDEX_NAME>",
-  "description": "Hybrid search index on a structured Data Cloud DMO",
-  "sourceDmoDeveloperName": "<SOURCE_DMO>__dlm",
-  "chunkDmoName": "<INDEX_NAME> chunk",
-  "chunkDmoDeveloperName": "<INDEX_NAME>_chunk",
-  "vectorDmoName": "<INDEX_NAME> index",
-  "vectorDmoDeveloperName": "<INDEX_NAME>_index",
-  "searchType": "HYBRID",
-  "vectorEmbedding": {
-    "vectorEmbeddingRelatedFields": []
-  },
-  "rankingConfigurations": [],
-  "chunkingConfiguration": {
-    "fieldLevelConfigurations": [
-      {
-        "sourceDmoDeveloperName": "<SOURCE_DMO>__dlm",
-        "sourceDmoFieldDeveloperName": "<TEXT_FIELD>__c",
-        "config": {
-          "id": "passage_extraction",
-          "userValues": [
-            { "id": "max_tokens", "value": "512" },
-            { "id": "strip_html", "value": "true" }
-          ]
-        }
-      }
-    ]
-  },
-  "vectorEmbeddingConfiguration": {
-    "embeddingModel": {
-      "id": "e5_large_v2",
-      "userValues": [
-        { "id": "dimension", "value": "1024" },
-        { "id": "max_token_limit", "value": "512" }
-      ]
-    },
-    "index": {
-      "id": "HNSW",
-      "userValues": []
-    },
-    "similarityMetric": "COSINE"
-  }
-}

package/skills/data360-query/examples/search-indexes/vector-knowledge.json

@@ -1,43 +0,0 @@
-{
-  "label": "My_kav",
-  "developerName": "My_kav",
-  "sourceDmoDeveloperName": "ssot__KnowledgeArticleVersion__dlm",
-  "chunkDmoName": "My_kav chunk",
-  "chunkDmoDeveloperName": "My_kav_chunk",
-  "vectorDmoName": "My_kav index",
-  "vectorDmoDeveloperName": "My_kav_index",
-  "searchType": "VECTOR",
-  "vectorEmbedding": {
-    "vectorEmbeddingRelatedFields": []
-  },
-  "chunkingConfiguration": {
-    "fieldLevelConfigurations": [
-      {
-        "sourceDmoDeveloperName": "ssot__KnowledgeArticleVersion__dlm",
-        "sourceDmoFieldDeveloperName": "ssot__Name__c",
-        "config": {
-          "id": "passage_extraction",
-          "userValues": [
-            { "id": "strip_html", "value": "true" },
-            { "id": "max_tokens", "value": "512" }
-          ]
-        }
-      }
-    ]
-  },
-  "vectorEmbeddingConfiguration": {
-    "embeddingModel": {
-      "id": "e5_large_v2",
-      "userValues": [
-        { "id": "dimension", "value": "1024" },
-        { "id": "max_token_limit", "value": "512" }
-      ]
-    },
-    "index": {
-      "id": "HNSW",
-      "userValues": []
-    },
-    "similarityMetric": "COSINE"
-  },
-  "rankingConfigurations": []
-}