@salesforce/afv-skills 1.65.0 → 1.65.1

package/skills/data360-semantic-data-object-mcp-configure/SKILL.md

@@ -1,93 +0,0 @@
----
-name: data360-semantic-data-object-mcp-configure
-description: "Use this skill when users want to execute Data Cloud SemanticDataObject operations via the Data 360 MCP facade. Trigger when users mention data360/semantic, data, object, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/semantic Data Object
-
-## When to Use This Skill
-
-Execute Data Cloud SemanticDataObject 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:**
-
-- **`sdm-data-object-delete`** — Delete a data object from a semantic model.
-  - 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 |
-|-----------|---------|--------|------|------------|
-| `sdm-data-object-create` | write | implemented | `execute_sdm-data-object-create` | — |
-| `sdm-data-object-delete` | delete | implemented | `execute_sdm-data-object-delete` | — |
-| `sdm-data-object-get` | read | implemented | `execute_sdm-data-object-get` | — |
-| `sdm-data-object-update` | write | implemented | `execute_sdm-data-object-update` | — |
-| `sdm-data-objects-list` | read | implemented | `execute_sdm-data-objects-list` | — |
-
-### Read operations
-
-#### `sdm-data-object-get`
-
-Get a data object from a semantic model.
-
-**Call:** `execute_sdm-data-object-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_data_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_sdm-data-object-get) for the param schema and, where available, a worked example.
-
-#### `sdm-data-objects-list`
-
-List data objects in a semantic model.
-
-**Call:** `execute_sdm-data-objects-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_data_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_sdm-data-objects-list) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `sdm-data-object-create`
-
-Add an existing Data Cloud Object as a new Semantic Data Object to a specific Semantic Model. Required body: { dataObjectName, label, dataObjectType, shouldIncludeAllFields }. dataObjectType values: 'Dmo' for DMOs, 'Dlo' for DLOs, 'Cio' for Calculated Insights (NOT 'CalculatedInsight'). Use shouldIncludeAllFields: true to auto-include all fields as dimensions/measurements.
-
-**Call:** `execute_sdm-data-object-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_data_object_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_sdm-data-object-create) for the param schema and, where available, a worked example.
-
-#### `sdm-data-object-update`
-
-Update a data object in a semantic model.
-
-**Call:** `execute_sdm-data-object-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_data_object_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_sdm-data-object-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `sdm-data-object-delete`
-
-Delete a data object from a semantic model.
-
-**Call:** `execute_sdm-data-object-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_data_object_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_sdm-data-object-delete) for the param schema and, where available, a worked example.

package/skills/data360-semantic-dimension-mcp-configure/SKILL.md

@@ -1,38 +0,0 @@
----
-name: data360-semantic-dimension-mcp-configure
-description: "Use this skill when users want to execute Data Cloud SemanticDimension operations via the Data 360 MCP facade. Trigger when users mention data360/semantic, dimension, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Querying Data360/semantic Dimension
-
-## When to Use This Skill
-
-Execute Data Cloud SemanticDimension 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 |
-|-----------|---------|--------|------|------------|
-| `sdm-dimensions-list` | read | implemented | `execute_sdm-dimensions-list` | — |
-
-### Read operations
-
-#### `sdm-dimensions-list`
-
-List dimensions for a data object in a semantic model.
-
-**Call:** `execute_sdm-dimensions-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_dimensions_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_sdm-dimensions-list) for the param schema and, where available, a worked example.

package/skills/data360-semantic-engine-mcp-configure/SKILL.md

@@ -1,62 +0,0 @@
----
-name: data360-semantic-engine-mcp-configure
-description: "Use this skill when users want to execute Data Cloud SemanticEngine operations via the Data 360 MCP facade. Trigger when users mention data360/semantic, engine, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/semantic Engine
-
-## When to Use This Skill
-
-Execute Data Cloud SemanticEngine 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 |
-|-----------|---------|--------|------|------------|
-| `sdm-formula-metadata` | read | implemented | `execute_sdm-formula-metadata` | — |
-| `sdm-generate-sql` | write | implemented | `execute_sdm-generate-sql` | — |
-| `sdm-query` | read | implemented | `execute_sdm-query` | — |
-
-### Read operations
-
-#### `sdm-formula-metadata`
-
-Get supported formula metadata for semantic models.
-
-**Call:** `execute_sdm-formula-metadata`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_formula_metadata (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_sdm-formula-metadata) for the param schema and, where available, a worked example.
-
-#### `sdm-query`
-
-Execute a semantic query against a semantic data model. The body must follow this structure: { semanticModelId, structuredSemanticQuery: { fields: [{expression, alias, rowGrouping?, semanticAggregationMethod?}, ...], options: {limitOptions: {limit: 10}} } }. For regular fields: use tableField with tableName (e.g. 'Norm_Geography' in table 'AccountRevenue'). For calculated dimensions/measurements: use semanticField with just name (e.g. {semanticField: {name: 'Cluster_Size_Tier'}}) — these are model-level, NOT on a specific table.
-
-**Call:** `execute_sdm-query`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_query (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_sdm-query) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `sdm-generate-sql`
-
-Generate SQL from a semantic data model query without executing it. Takes the same body shape as d360_sdm_query and returns the SQL string that would be executed against the data source.
-
-**Call:** `execute_sdm-generate-sql`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_generate_sql (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_sdm-generate-sql) for the param schema and, where available, a worked example.

package/skills/data360-semantic-measurement-mcp-configure/SKILL.md

@@ -1,38 +0,0 @@
----
-name: data360-semantic-measurement-mcp-configure
-description: "Use this skill when users want to execute Data Cloud SemanticMeasurement operations via the Data 360 MCP facade. Trigger when users mention data360/semantic, measurement, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Querying Data360/semantic Measurement
-
-## When to Use This Skill
-
-Execute Data Cloud SemanticMeasurement 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 |
-|-----------|---------|--------|------|------------|
-| `sdm-measurements-list` | read | implemented | `execute_sdm-measurements-list` | — |
-
-### Read operations
-
-#### `sdm-measurements-list`
-
-List measurements for a data object in a semantic model.
-
-**Call:** `execute_sdm-measurements-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_measurements_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_sdm-measurements-list) for the param schema and, where available, a worked example.

package/skills/data360-semantic-metric-mcp-configure/SKILL.md

@@ -1,93 +0,0 @@
----
-name: data360-semantic-metric-mcp-configure
-description: "Use this skill when users want to execute Data Cloud SemanticMetric operations via the Data 360 MCP facade. Trigger when users mention data360/semantic, metric, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/semantic Metric
-
-## When to Use This Skill
-
-Execute Data Cloud SemanticMetric 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:**
-
-- **`sdm-metric-delete`** — Delete a metric from a semantic model.
-  - 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 |
-|-----------|---------|--------|------|------------|
-| `sdm-metric-create` | write | implemented | `execute_sdm-metric-create` | — |
-| `sdm-metric-delete` | delete | implemented | `execute_sdm-metric-delete` | — |
-| `sdm-metric-get` | read | implemented | `execute_sdm-metric-get` | — |
-| `sdm-metric-update` | write | implemented | `execute_sdm-metric-update` | — |
-| `sdm-metrics-list` | read | implemented | `execute_sdm-metrics-list` | — |
-
-### Read operations
-
-#### `sdm-metric-get`
-
-Get a metric from a semantic model.
-
-**Call:** `execute_sdm-metric-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_metric_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_sdm-metric-get) for the param schema and, where available, a worked example.
-
-#### `sdm-metrics-list`
-
-List metrics in a semantic model.
-
-**Call:** `execute_sdm-metrics-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_metrics_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_sdm-metrics-list) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `sdm-metric-create`
-
-Create a metric in a semantic model.
-
-**Call:** `execute_sdm-metric-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_metric_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_sdm-metric-create) for the param schema and, where available, a worked example.
-
-#### `sdm-metric-update`
-
-Update a metric in a semantic model.
-
-**Call:** `execute_sdm-metric-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_metric_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_sdm-metric-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `sdm-metric-delete`
-
-Delete a metric from a semantic model.
-
-**Call:** `execute_sdm-metric-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_metric_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_sdm-metric-delete) for the param schema and, where available, a worked example.

package/skills/data360-semantic-model-mcp-configure/SKILL.md

@@ -1,115 +0,0 @@
----
-name: data360-semantic-model-mcp-configure
-description: "Use this skill when users want to execute Data Cloud SemanticModel operations via the Data 360 MCP facade. Trigger when users mention data360/semantic, model, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/semantic Model
-
-## When to Use This Skill
-
-Execute Data Cloud SemanticModel 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:**
-
-- **`sdm-delete`** — Delete a semantic data model.
-  - 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 |
-|-----------|---------|--------|------|------------|
-| `sdm-clone` | write | implemented | `execute_sdm-clone` | — |
-| `sdm-create` | write | implemented | `execute_sdm-create` | — |
-| `sdm-delete` | delete | implemented | `execute_sdm-delete` | — |
-| `sdm-get` | read | implemented | `execute_sdm-get` | — |
-| `sdm-list` | read | implemented | `execute_sdm-list` | — |
-| `sdm-update` | write | implemented | `execute_sdm-update` | — |
-| `sdm-validate` | read | implemented | `execute_sdm-validate` | — |
-
-### Read operations
-
-#### `sdm-get`
-
-Get a semantic data model by API name or ID.
-
-**Call:** `execute_sdm-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_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_sdm-get) for the param schema and, where available, a worked example.
-
-#### `sdm-list`
-
-List semantic data models in the org. All parameters are optional; with no filters returns all models the caller can see. 
-
-**Call:** `execute_sdm-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_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_sdm-list) for the param schema and, where available, a worked example.
-
-#### `sdm-validate`
-
-Validate a semantic data model.
-
-**Call:** `execute_sdm-validate`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_validate (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_sdm-validate) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `sdm-clone`
-
-Clone a semantic data model.
-
-**Call:** `execute_sdm-clone`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_clone (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_sdm-clone) for the param schema and, where available, a worked example.
-
-#### `sdm-create`
-
-Create a semantic data model shell. Body: { apiName, label, description, dataspace (REQUIRED in body) }. Then add data objects, relationships, calc dims/measures via separate tools. DEPENDENCY: All CIs/DMOs must exist before adding as data objects.
-
-**Call:** `execute_sdm-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_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_sdm-create) for the param schema and, where available, a worked example.
-
-#### `sdm-update`
-
-Updates specific entity fields in the Semantic Model object without affecting child dependencies or relationships.
-
-**Call:** `execute_sdm-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_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_sdm-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `sdm-delete`
-
-Delete a semantic data model.
-
-**Call:** `execute_sdm-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_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_sdm-delete) for the param schema and, where available, a worked example.

package/skills/data360-standard-mapping-mcp-configure/SKILL.md

@@ -1,38 +0,0 @@
----
-name: data360-standard-mapping-mcp-configure
-description: "Use this skill when users want to execute Data Cloud StandardMapping operations via the Data 360 MCP facade. Trigger when users mention data360/standard, mapping, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/standard Mapping
-
-## When to Use This Skill
-
-Execute Data Cloud StandardMapping 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 |
-|-----------|---------|--------|------|------------|
-| `create-standard-mapping` | write | implemented | `execute_create-standard-mapping` | — |
-
-### Write operations
-
-#### `create-standard-mapping`
-
-Create the standard Data Cloud mapping for a single DLO of an opinionated standard Salesforce object. Given one DLO developer name, checks whether it is opinionated and, if so, triggers its standard mapping deployment. Returns success=true with the mapped DLO developer name when the mapping was created, or success=false when the DLO was not mapped.
-
-**Call:** `execute_create-standard-mapping`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_create_standard_mapping (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_create-standard-mapping) for the param schema and, where available, a worked example.

package/skills/data360-tenant-lifecycle-mcp-configure/SKILL.md

@@ -1,73 +0,0 @@
----
-name: data360-tenant-lifecycle-mcp-configure
-description: "Use this skill when users want to execute Data Cloud TenantLifecycle operations via the Data 360 MCP facade. Trigger when users mention data360/tenant, lifecycle, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/tenant Lifecycle
-
-## When to Use This Skill
-
-Execute Data Cloud TenantLifecycle 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 |
-|-----------|---------|--------|------|------------|
-| `tenantlifecycle-details` | read | implemented | `execute_tenantlifecycle-details` | — |
-| `tenantlifecycle-enable` | write | implemented | `execute_tenantlifecycle-enable` | — |
-| `tenantlifecycle-retry` | write | implemented | `execute_tenantlifecycle-retry` | — |
-| `tenantlifecycle-status` | read | implemented | `execute_tenantlifecycle-status` | — |
-
-### Read operations
-
-#### `tenantlifecycle-details`
-
-Retrieve detailed Data Cloud (Data 360) tenant metadata for the org: homeOrgId, homeOrgInstance, tenantEndpoint, tenantId, coreId, and the counts of configured data spaces (dataSpacesCount) and connections (connectionsCount). Prerequisite: the tenant must already be provisioned — this metadata is only available after provisioning has completed successfully. Call d360_tenantlifecycle_status first and confirm isProvisioned is true before calling this tool; if the tenant is not yet provisioned, enable it with d360_tenantlifecycle_enable.
-
-**Call:** `execute_tenantlifecycle-details`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_tenantlifecycle_details (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_tenantlifecycle-details) for the param schema and, where available, a worked example.
-
-#### `tenantlifecycle-status`
-
-Retrieve the current Data Cloud (Data 360) tenant lifecycle status for the org. Returns isActive (the tenant has a valid license and provisioning completed successfully), isProvisioned (provisioning finished successfully), isLicensed (the org has a valid Data Cloud license), and the current provisionStatus code with a provisionStatusDetail message. Call this first to decide the next step: if isProvisioned is false and isLicensed is true, enable provisioning with d360_tenantlifecycle_enable; if a prior provisioning attempt failed, retry with d360_tenantlifecycle_retry; once isProvisioned is true, fetch tenant metadata with d360_tenantlifecycle_details.
-
-**Call:** `execute_tenantlifecycle-status`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_tenantlifecycle_status (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_tenantlifecycle-status) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `tenantlifecycle-enable`
-
-Enable Data Cloud (Data 360) tenant provisioning for the org. Optionally set installCIMPackage to true to also install the Customer Information Model (CIM) package as part of provisioning. Validation: the org must hold a valid Data Cloud license and must not already be provisioned — first call d360_tenantlifecycle_status and confirm isLicensed is true and isProvisioned is false before invoking this tool. This is an asynchronous, long-running operation; it returns the provisioning action result (status, message, success). Poll d360_tenantlifecycle_status for completion, and if provisioning fails use d360_tenantlifecycle_retry.
-
-**Call:** `execute_tenantlifecycle-enable`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_tenantlifecycle_enable (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_tenantlifecycle-enable) for the param schema and, where available, a worked example.
-
-#### `tenantlifecycle-retry`
-
-Retry a previously failed Data Cloud (Data 360) tenant provisioning attempt for the org. Optionally set installCIMPackage to true to install the Customer Information Model (CIM) package during the retry. Use this when d360_tenantlifecycle_status reports a provisioning failure (isProvisioned is false with an error provisionStatus) after a prior d360_tenantlifecycle_enable call. This is an asynchronous, long-running operation; it returns the provisioning action result (status, message, success). Poll d360_tenantlifecycle_status for completion.
-
-**Call:** `execute_tenantlifecycle-retry`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_tenantlifecycle_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_tenantlifecycle-retry) for the param schema and, where available, a worked example.