@salesforce/afv-skills 1.65.0 → 1.65.1

package/skills/data360-data-graph-create/SKILL.md

@@ -1,82 +0,0 @@
----
-name: data360-data-graph-create
-description: "Use this skill when users want to execute Data Cloud DataGraph operations via the Data 360 MCP facade. Trigger when users mention data360/data, graph, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/data Graph
-
-## When to Use This Skill
-
-Execute Data Cloud DataGraph operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Critical Constraints
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`data-graph-delete`** — Delete a Data Graph by its dataGraphName. This permanently removes the graph definition; ensure no dependent segments, calculated insights, or activations reference it before deleting.
-  - Rollback: No automatic rollback.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `data-graph-create` | write | implemented | `execute_data-graph-create` | — |
-| `data-graph-delete` | delete | implemented | `execute_data-graph-delete` | — |
-| `data-graph-get` | read | implemented | `execute_data-graph-get` | — |
-| `data-graph-update` | write | implemented | `execute_data-graph-update` | — |
-
-### Read operations
-
-#### `data-graph-get`
-
-Get a Data Graph by its dataGraphName. Returns the graph definition, and optionally calculated insight (CI) and segment usage details via includeCIDetails/includeSegmentDetails.
-
-**Call:** `execute_data-graph-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_data_graph_get (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_data-graph-get) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `data-graph-create`
-
-Create a Data Graph from a primary DMO and its related objects/fields for low-latency lookup. Use d360_data_graph_get afterwards to verify the resulting definition.
-
-**Call:** `execute_data-graph-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_data_graph_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_data-graph-create) for the param schema and, where available, a worked example.
-
-#### `data-graph-update`
-
-Update (edit) an existing Data Graph by dataGraphName. Provide the full input definition to redefine the graph, or set editScheduleOnly to true to only update its refresh schedule. Use d360_data_graph_get first to review the current definition.
-
-**Call:** `execute_data-graph-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_data_graph_update (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_data-graph-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `data-graph-delete`
-
-Delete a Data Graph by its dataGraphName. This permanently removes the graph definition; ensure no dependent segments, calculated insights, or activations reference it before deleting.
-
-**Call:** `execute_data-graph-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_data_graph_delete (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_data-graph-delete) for the param schema and, where available, a worked example.

package/skills/data360-data-harmonized-model-object-reference-create/SKILL.md

@@ -1,38 +0,0 @@
----
-name: data360-data-harmonized-model-object-reference-create
-description: "Use this skill when users want to execute Data Cloud DataHarmonizedModelObjRef operations via the Data 360 MCP facade. Trigger when users mention data360/data, harmonized, model, obj, ref, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/data Harmonized Model Obj Ref
-
-## When to Use This Skill
-
-Execute Data Cloud DataHarmonizedModelObjRef operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `ek-dhmor-create` | write | implemented | `execute_ek-dhmor-create` | — |
-
-### Write operations
-
-#### `ek-dhmor-create`
-
-create/get a Data Harmonized Model Object Reference bridging harmonized content to a DMO.
-
-**Call:** `execute_ek-dhmor-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_ek_dhmor_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_ek-dhmor-create) for the param schema and, where available, a worked example.

package/skills/data360-data-lake-object-create/SKILL.md

@@ -1,207 +0,0 @@
----
-name: data360-data-lake-object-create
-description: "Use this skill when users want to execute Data Cloud DataLakeObject operations via the Data 360 MCP facade. Trigger when users mention data360/data, lake, object, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/data Lake Object
-
-## When to Use This Skill
-
-Execute Data Cloud DataLakeObject operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Critical Constraints
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`dlo-delete`** — Delete a Data Lake Object. Use this to remove a DLO and its data from the data lake. Ensure no mappings or data streams reference it before deleting.
-  - Rollback: No automatic rollback.
-- **`dlo-field-delete`** — Delete a field from a Data Lake Object.
-  - Rollback: No automatic rollback.
-- **`dlo-kq-remove`** — Remove the Key Qualifier designation from a Data Lake Object field. The field itself is not deleted — only the Key Qualifier designation is cleared.
-  - Rollback: No automatic rollback.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `dlo-create` | write | implemented | `execute_dlo-create` | — |
-| `dlo-delete` | delete | implemented | `execute_dlo-delete` | — |
-| `dlo-dependencies-list` | read | implemented | `execute_dlo-dependencies-list` | — |
-| `dlo-field-delete` | delete | implemented | `execute_dlo-field-delete` | — |
-| `dlo-get` | read | implemented | `execute_dlo-get` | — |
-| `dlo-kq-dependencies-list` | read | implemented | `execute_dlo-kq-dependencies-list` | — |
-| `dlo-kq-get` | read | implemented | `execute_dlo-kq-get` | — |
-| `dlo-kq-list` | read | implemented | `execute_dlo-kq-list` | — |
-| `dlo-kq-remove` | delete | implemented | `execute_dlo-kq-remove` | — |
-| `dlo-kq-retry` | write | implemented | `execute_dlo-kq-retry` | — |
-| `dlo-kq-upsert` | write | implemented | `execute_dlo-kq-upsert` | — |
-| `dlo-list` | read | implemented | `execute_dlo-list` | — |
-| `dlo-refresh-history-list` | read | implemented | `execute_dlo-refresh-history-list` | — |
-| `dlo-retry` | write | implemented | `execute_dlo-retry` | — |
-| `dlo-update` | write | implemented | `execute_dlo-update` | — |
-
-### Read operations
-
-#### `dlo-dependencies-list`
-
-List entities that depend on a Data Lake Object. Use as a pre-flight check before deleting the Data Lake Object.
-
-**Call:** `execute_dlo-dependencies-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_dependencies_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-dependencies-list) for the param schema and, where available, a worked example.
-
-#### `dlo-get`
-
-Get ONE DLO with all field definitions by API name. PREREQUISITE for creating mappings - returns exact field API names needed for sourceFieldName values. Pair with d360_dmo_get for target field names.
-
-**Call:** `execute_dlo-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_get (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-get) for the param schema and, where available, a worked example.
-
-#### `dlo-kq-dependencies-list`
-
-List entities that depend on a specific Key Qualifier of a Data Lake Object. Use as a pre-flight check before removing the Key Qualifier.
-
-**Call:** `execute_dlo-kq-dependencies-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_kq_dependencies_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-kq-dependencies-list) for the param schema and, where available, a worked example.
-
-#### `dlo-kq-get`
-
-Get a single Key Qualifier designation on a Data Lake Object by its record id or developer name.
-
-**Call:** `execute_dlo-kq-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_kq_get (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-kq-get) for the param schema and, where available, a worked example.
-
-#### `dlo-kq-list`
-
-List all Key Qualifier designations configured on a Data Lake Object.
-
-**Call:** `execute_dlo-kq-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_kq_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-kq-list) for the param schema and, where available, a worked example.
-
-#### `dlo-list`
-
-List all Data Lake Objects (DLOs) - raw ingested data sources. Essential for discovering DLO names and field API names before creating mappings.
-
-**Call:** `execute_dlo-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-list) for the param schema and, where available, a worked example.
-
-#### `dlo-refresh-history-list`
-
-List the most recent 50 refresh history records for a Data Lake Object, ordered by refresh start time descending.
-
-**Call:** `execute_dlo-refresh-history-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_refresh_history_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-refresh-history-list) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `dlo-create`
-
-Create a new Data Lake Object. Typically created automatically via data stream ingestion, but can be created manually for custom use cases. Specify fields, types, and category.
-
-**Call:** `execute_dlo-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-create) for the param schema and, where available, a worked example.
-
-#### `dlo-kq-retry`
-
-Retry a Key Qualifier that is in ERROR status on a Data Lake Object.
-
-**Call:** `execute_dlo-kq-retry`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_kq_retry (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-kq-retry) for the param schema and, where available, a worked example.
-
-#### `dlo-kq-upsert`
-
-Add or update the Key Qualifier designation on a Data Lake Object field. Only the Constant type is accepted.
-
-**Call:** `execute_dlo-kq-upsert`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_kq_upsert (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-kq-upsert) for the param schema and, where available, a worked example.
-
-#### `dlo-retry`
-
-Retry a Data Lake Object that is in ERROR status.
-
-**Call:** `execute_dlo-retry`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_retry (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-retry) for the param schema and, where available, a worked example.
-
-#### `dlo-update`
-
-Update an existing Data Lake Object. Use this to modify a DLO's schema - add or change fields, update labels, or adjust field types.
-
-**Call:** `execute_dlo-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_update (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `dlo-delete`
-
-Delete a Data Lake Object. Use this to remove a DLO and its data from the data lake. Ensure no mappings or data streams reference it before deleting.
-
-**Call:** `execute_dlo-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_delete (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-delete) for the param schema and, where available, a worked example.
-
-#### `dlo-field-delete`
-
-Delete a field from a Data Lake Object.
-
-**Call:** `execute_dlo-field-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_field_delete (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-field-delete) for the param schema and, where available, a worked example.
-
-#### `dlo-kq-remove`
-
-Remove the Key Qualifier designation from a Data Lake Object field. The field itself is not deleted — only the Key Qualifier designation is cleared.
-
-**Call:** `execute_dlo-kq-remove`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dlo_kq_remove (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dlo-kq-remove) for the param schema and, where available, a worked example.

package/skills/data360-data-model-object-catalog-get/SKILL.md

@@ -1,49 +0,0 @@
----
-name: data360-data-model-object-catalog-get
-description: "Use this skill when users want to execute Data Cloud DataModelObjectCatalog operations via the Data 360 MCP facade. Trigger when users mention data360/data, model, object, catalog, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Querying Data360/data Model Object Catalog
-
-## When to Use This Skill
-
-Execute Data Cloud DataModelObjectCatalog operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `data-model-object-get` | read | implemented | `execute_data-model-object-get` | — |
-| `data-model-objects-list` | read | implemented | `execute_data-model-objects-list` | — |
-
-### Read operations
-
-#### `data-model-object-get`
-
-Get a single standard Data Cloud data model object (model / object / DMO) by its name. Returns the model's name, label, type, description, and its fields (each with name, label, and type). Use d360_data_model_objects_list to discover available model names.
-
-**Call:** `execute_data-model-object-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_data_model_object_get (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_data-model-object-get) for the param schema and, where available, a worked example.
-
-#### `data-model-objects-list`
-
-List the standard Data Cloud data model objects (models / objects / DMOs) available to map to. Supports pagination and ordering, plus an optional search that matches on either the model name or its label (case-insensitive, minimum 3 characters). Returns each model's name, label, type, and description; call d360_data_model_object_get for a model's fields.
-
-**Call:** `execute_data-model-objects-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_data_model_objects_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_data-model-objects-list) for the param schema and, where available, a worked example.

package/skills/data360-data-model-object-create/SKILL.md

@@ -1,128 +0,0 @@
----
-name: data360-data-model-object-create
-description: "Use this skill when users want to execute Data Cloud DataModelObject operations via the Data 360 MCP facade. Trigger when users mention data360/data, model, object, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/data Model Object
-
-## When to Use This Skill
-
-Execute Data Cloud DataModelObject operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Critical Constraints
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`dmo-delete`** — Delete a Data Model Object.
-  - Rollback: No automatic rollback.
-- **`dmo-relationship-delete`** — Delete a DMO relationship by name. Only Custom relationships can 
-  - Rollback: No automatic rollback.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `dmo-create` | write | implemented | `execute_dmo-create` | — |
-| `dmo-delete` | delete | implemented | `execute_dmo-delete` | — |
-| `dmo-get` | read | implemented | `execute_dmo-get` | — |
-| `dmo-list` | read | implemented | `execute_dmo-list` | — |
-| `dmo-relationship-create` | write | implemented | `execute_dmo-relationship-create` | — |
-| `dmo-relationship-delete` | delete | implemented | `execute_dmo-relationship-delete` | — |
-| `dmo-relationship-list` | read | implemented | `execute_dmo-relationship-list` | — |
-| `dmo-update` | write | implemented | `execute_dmo-update` | — |
-
-### Read operations
-
-#### `dmo-get`
-
-Get a specific Data Model Object by name with all field definitions. 
-
-**Call:** `execute_dmo-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_get (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-get) for the param schema and, where available, a worked example.
-
-#### `dmo-list`
-
-List the Data Model Objects (DMOs) in this org, excluding the standard/canonical DMOs (those are listed by d360_data_model_objects_list). Returns customer-created and derived DMOs — custom, SQL/transform, segment membership, calculated insight, and so on. Supports pagination and ordering, plus optional filters on data space, category, and enablement.
-
-**Call:** `execute_dmo-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-list) for the param schema and, where available, a worked example.
-
-#### `dmo-relationship-list`
-
-List the relationships where the provided Data Model Object (DMO) is the source or 
-
-**Call:** `execute_dmo-relationship-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_relationship_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-relationship-list) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `dmo-create`
-
-Create a new Data Model Object. 
-
-**Call:** `execute_dmo-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-create) for the param schema and, where available, a worked example.
-
-#### `dmo-relationship-create`
-
-Create one or more relationships on a Data Model Object (DMO). The DMO must be 
-
-**Call:** `execute_dmo-relationship-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_relationship_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-relationship-create) for the param schema and, where available, a worked example.
-
-#### `dmo-update`
-
-Update an existing Data Model Object.
-
-**Call:** `execute_dmo-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_update (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `dmo-delete`
-
-Delete a Data Model Object.
-
-**Call:** `execute_dmo-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_delete (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-delete) for the param schema and, where available, a worked example.
-
-#### `dmo-relationship-delete`
-
-Delete a DMO relationship by name. Only Custom relationships can 
-
-**Call:** `execute_dmo-relationship-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_relationship_delete (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-relationship-delete) for the param schema and, where available, a worked example.

package/skills/data360-data-model-object-mapping-create/SKILL.md

@@ -1,106 +0,0 @@
----
-name: data360-data-model-object-mapping-create
-description: "Use this skill when users want to execute Data Cloud DataModelObjectMapping operations via the Data 360 MCP facade. Trigger when users mention data360/data, model, object, mapping, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/data Model Object Mapping
-
-## When to Use This Skill
-
-Execute Data Cloud DataModelObjectMapping operations via the Data 360 MCP facade.
-
-## Workflow
-
-Each step lists an `operation` id. Call describe(<operation>) BEFORE dispatching to get that tool's parameter schema and, where available, a worked example. `paramsJson` decodes to the operation's requestBody schema VERBATIM, including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap or omit it. The only envelope the step handles for you is `{toolName, paramsJson}` (its `invocation` already wraps it); do not POST the operation path directly. If the tool's error suggests `payload_examples`, ignore it — that tool isn't available here; call describe(<operation>) instead.
-
-## Critical Constraints
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`dmo-field-mapping-delete`** — Delete a single field mapping from an existing object mapping (e.g. MailingCity__c_fieldmap_ssot__CityId__c) without deleting the entire object mapping.
-  - Rollback: No automatic rollback.
-- **`dmo-mapping-delete`** — Delete a DMO mapping by its developer name. Removes the DLO-to-DMO field mapping; the data stream and DMO still exist but data will no longer flow into the target DMO from that source.
-  - Rollback: No automatic rollback.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `dmo-field-mapping-add` | write | implemented | `execute_dmo-field-mapping-add` | — |
-| `dmo-field-mapping-delete` | delete | implemented | `execute_dmo-field-mapping-delete` | — |
-| `dmo-mapping-create` | write | implemented | `execute_dmo-mapping-create` | — |
-| `dmo-mapping-delete` | delete | implemented | `execute_dmo-mapping-delete` | — |
-| `dmo-mapping-get` | read | implemented | `execute_dmo-mapping-get` | — |
-| `dmo-mapping-list` | read | implemented | `execute_dmo-mapping-list` | — |
-
-### Read operations
-
-#### `dmo-mapping-get`
-
-Get a specific DMO mapping by its developer name (e.g. Account_std_map_Account_1000000000000). Returns the field-level mapping between a DLO and DMO.
-
-**Call:** `execute_dmo-mapping-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_mapping_get (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-mapping-get) for the param schema and, where available, a worked example.
-
-#### `dmo-mapping-list`
-
-List DMO mappings filtered by DMO developer name or CRM source object name. Provide either dmoDeveloperName or sourceObjectName (at least one is required).
-
-**Call:** `execute_dmo-mapping-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_mapping_list (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-mapping-list) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `dmo-field-mapping-add`
-
-Add field mappings to an existing object mapping between a DLO and DMO without recreating the entire object mapping.
-
-**Call:** `execute_dmo-field-mapping-add`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_field_mapping_add (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-field-mapping-add) for the param schema and, where available, a worked example.
-
-#### `dmo-mapping-create`
-
-Create a single DMO mapping (one source-to-DMO mapping per call). DLO field names include a __c suffix (e.g., customer_id__c). Use d360_dlo_get for source field names and d360_dmo_get for target field names. For Engagement DLOs, the event date field MUST be included in the mapping and source/target field types must match exactly.
-
-**Call:** `execute_dmo-mapping-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_mapping_create (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-mapping-create) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `dmo-field-mapping-delete`
-
-Delete a single field mapping from an existing object mapping (e.g. MailingCity__c_fieldmap_ssot__CityId__c) without deleting the entire object mapping.
-
-**Call:** `execute_dmo-field-mapping-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_field_mapping_delete (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-field-mapping-delete) for the param schema and, where available, a worked example.
-
-#### `dmo-mapping-delete`
-
-Delete a DMO mapping by its developer name. Removes the DLO-to-DMO field mapping; the data stream and DMO still exist but data will no longer flow into the target DMO from that source.
-
-**Call:** `execute_dmo-mapping-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_dmo_mapping_delete (a STRING, double-encoded). Serialize the operation's requestBody schema VERBATIM including its top-level key (e.g. `input`, `dataTransform`) — do not unwrap it. Call describe(execute_dmo-mapping-delete) for the param schema and, where available, a worked example.