@salesforce/afv-skills 1.65.0 → 1.66.0

package/skills/data360-multi-org-mcp-configure/SKILL.md

@@ -1,117 +0,0 @@
----
-name: data360-multi-org-mcp-configure
-description: "Use this skill when users want to execute Data Cloud MultiOrg operations via the Data 360 MCP facade. Trigger when users mention data360/multi, org, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/multi Org
-
-## When to Use This Skill
-
-Execute Data Cloud MultiOrg 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 |
-|-----------|---------|--------|------|------------|
-| `multiorg-connection-disconnect` | write | implemented | `execute_multiorg-connection-disconnect` | — |
-| `multiorg-connection-get` | read | implemented | `execute_multiorg-connection-get` | — |
-| `multiorg-connection-list` | read | implemented | `execute_multiorg-connection-list` | — |
-| `multiorg-scope-dependencies` | read | implemented | `execute_multiorg-scope-dependencies` | — |
-| `multiorg-scope-get` | read | implemented | `execute_multiorg-scope-get` | — |
-| `multiorg-scope-list` | read | implemented | `execute_multiorg-scope-list` | — |
-| `multiorg-scope-share` | write | implemented | `execute_multiorg-scope-share` | — |
-| `multiorg-scope-unshare` | write | implemented | `execute_multiorg-scope-unshare` | — |
-
-### Read operations
-
-#### `multiorg-connection-get`
-
-Get detailed status of a specific multi-org connection by ID. Returns connection metadata, sync status, pending changesets, and metadata sync errors. Use includeScopes=true to see all assigned scopes and their states.
-
-**Call:** `execute_multiorg-connection-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_multiorg_connection_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_multiorg-connection-get) for the param schema and, where available, a worked example.
-
-#### `multiorg-connection-list`
-
-List all multi-org connections for the current org. Returns connection status, org info, and optionally scope details. Use filters to narrow by orgType (HOME/LOB), developerName, or scopeFeatureType (Dc1/Tua/Moma). Set includeScopes=true to embed scope arrays.
-
-**Call:** `execute_multiorg-connection-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_multiorg_connection_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_multiorg-connection-list) for the param schema and, where available, a worked example.
-
-#### `multiorg-scope-dependencies`
-
-Get cross-org references (dependencies) for a scope before unsharing. Returns records grouped by entity type (segments, activations, etc.) that reference this scope from other orgs. Use pagination (pageSize/pageOffset) for large result sets. MUST check before unshare - dependencies block unshare operations.
-
-**Call:** `execute_multiorg-scope-dependencies`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_multiorg_scope_dependencies (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_multiorg-scope-dependencies) for the param schema and, where available, a worked example.
-
-#### `multiorg-scope-get`
-
-Get detailed status of a single scope within a connection. Use for polling after share/unshare operations. Returns status (SHARING/ACTIVATING/ACTIVE/REMOVING_SHARING/ERROR), day0 errors (Home org only), sync timestamps, and sharing metadata. Returns 404 when scope is fully unshared (expected after successful unshare).
-
-**Call:** `execute_multiorg-scope-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_multiorg_scope_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_multiorg-scope-get) for the param schema and, where available, a worked example.
-
-#### `multiorg-scope-list`
-
-List all scopes (dataspaces) assigned to a connection with their sharing status. Filter by featureType (Dc1/Tua/Moma). Returns scope metadata, sync status, last synced timestamp, and who shared it.
-
-**Call:** `execute_multiorg-scope-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_multiorg_scope_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_multiorg-scope-list) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `multiorg-connection-disconnect`
-
-Disconnect a multi-org connection and revoke 3-way trust. All scopes must be unshared first - check with d360_multiorg_connection_get to verify no active scopes remain. Returns 412 if scopes are still shared.
-
-**Call:** `execute_multiorg-connection-disconnect`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_multiorg_connection_disconnect (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_multiorg-connection-disconnect) for the param schema and, where available, a worked example.
-
-#### `multiorg-scope-share`
-
-Share one or more dataspaces (scopes) with a connected companion org. Triggers async sharing pipeline - returns 202 Accepted immediately. Poll d360_multiorg_scope_get to track status flow SHARING to ACTIVATING to ACTIVE. Returns 409 if scope already shared or sandbox reconciliation in progress.
-
-**Call:** `execute_multiorg-scope-share`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_multiorg_scope_share (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_multiorg-scope-share) for the param schema and, where available, a worked example.
-
-#### `multiorg-scope-unshare`
-
-Unshare one or more dataspaces from a connected companion org. Check d360_multiorg_scope_dependencies first - returns 412 if dependencies exist. Triggers async removal - status flow ACTIVE to REMOVING_SHARING to UNSHARED (404). Returns 409 if sandbox reconciliation in progress.
-
-**Call:** `execute_multiorg-scope-unshare`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_multiorg_scope_unshare (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_multiorg-scope-unshare) for the param schema and, where available, a worked example.

package/skills/data360-secondary-index-mcp-configure/SKILL.md

@@ -1,126 +0,0 @@
----
-name: data360-secondary-index-mcp-configure
-description: "Use this skill when users want to execute Data Cloud SecondaryIndex operations via the Data 360 MCP facade. Trigger when users mention data360/secondary, index, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/secondary Index
-
-## When to Use This Skill
-
-Execute Data Cloud SecondaryIndex 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:**
-
-- **`secondary-index-delete`** — Delete a secondary index by its developer name or Salesforce ID. This removes the index configuration and associated platform entities.
-  - 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 |
-|-----------|---------|--------|------|------------|
-| `secondary-index-create` | write | implemented | `execute_secondary-index-create` | — |
-| `secondary-index-delete` | delete | implemented | `execute_secondary-index-delete` | — |
-| `secondary-index-get` | read | implemented | `execute_secondary-index-get` | — |
-| `secondary-index-list` | read | implemented | `execute_secondary-index-list` | — |
-| `secondary-index-run-history` | read | implemented | `execute_secondary-index-run-history` | — |
-| `secondary-index-schedule-get` | read | implemented | `execute_secondary-index-schedule-get` | — |
-| `secondary-index-schedule-update` | write | implemented | `execute_secondary-index-schedule-update` | — |
-| `secondary-index-status` | read | implemented | `execute_secondary-index-status` | — |
-
-### Read operations
-
-#### `secondary-index-get`
-
-Retrieve a specific secondary index by its developer name or Salesforce ID. Returns detailed configuration including fields, source object, and related entities.
-
-**Call:** `execute_secondary-index-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_secondary_index_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_secondary-index-get) for the param schema and, where available, a worked example.
-
-#### `secondary-index-list`
-
-List all secondary indexes configured in the org with optional filtering, sorting and pagination. Use d360_secondary_index_get to fetch a specific one by developer name or id.
-
-**Call:** `execute_secondary-index-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_secondary_index_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_secondary-index-list) for the param schema and, where available, a worked example.
-
-#### `secondary-index-run-history`
-
-Retrieve the run history for a secondary index by its developer name or ID. Shows execution results, timestamps, and status of past index builds.
-
-**Call:** `execute_secondary-index-run-history`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_secondary_index_run_history (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_secondary-index-run-history) for the param schema and, where available, a worked example.
-
-#### `secondary-index-schedule-get`
-
-Get the schedule configuration for a secondary index by its developer name or ID. Returns frequency, timing, and recurrence settings.
-
-**Call:** `execute_secondary-index-schedule-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_secondary_index_schedule_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_secondary-index-schedule-get) for the param schema and, where available, a worked example.
-
-#### `secondary-index-status`
-
-Get the aggregated status of a secondary index and its related platform entities by developer name or ID. Returns health, runtime status, and related entity states.
-
-**Call:** `execute_secondary-index-status`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_secondary_index_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_secondary-index-status) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `secondary-index-create`
-
-Create a new secondary index. Specify the source object, fields to index, and related entity configurations.
-
-**Call:** `execute_secondary-index-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_secondary_index_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_secondary-index-create) for the param schema and, where available, a worked example.
-
-#### `secondary-index-schedule-update`
-
-Update the schedule configuration for a secondary index. Modify frequency, timing, and recurrence settings for automated index builds.
-
-**Call:** `execute_secondary-index-schedule-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_secondary_index_schedule_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_secondary-index-schedule-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `secondary-index-delete`
-
-Delete a secondary index by its developer name or Salesforce ID. This removes the index configuration and associated platform entities.
-
-**Call:** `execute_secondary-index-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_secondary_index_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_secondary-index-delete) for the param schema and, where available, a worked example.

package/skills/data360-segment-mcp-configure/SKILL.md

@@ -1,159 +0,0 @@
----
-name: data360-segment-mcp-configure
-description: "Use this skill when users want to execute Data Cloud Segment operations via the Data 360 MCP facade. Trigger when users mention data360/segment, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/segment
-
-## When to Use This Skill
-
-Execute Data Cloud Segment 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:**
-
-- **`segment-delete`** — Delete an audience segment by segmentApiName. Removes the segment definition; published audiences are no longer regenerated.
-  - 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 |
-|-----------|---------|--------|------|------------|
-| `segment-count` | read | implemented | `execute_segment-count` | — |
-| `segment-create` | write | implemented | `execute_segment-create` | — |
-| `segment-deactivate` | write | implemented | `execute_segment-deactivate` | — |
-| `segment-deactivate-by-name` | write | implemented | `execute_segment-deactivate-by-name` | — |
-| `segment-delete` | delete | implemented | `execute_segment-delete` | — |
-| `segment-get` | read | implemented | `execute_segment-get` | — |
-| `segment-get-by-id` | read | implemented | `execute_segment-get-by-id` | — |
-| `segment-list` | read | implemented | `execute_segment-list` | — |
-| `segment-member-list` | read | implemented | `execute_segment-member-list` | — |
-| `segment-publish` | write | implemented | `execute_segment-publish` | — |
-| `segment-update` | write | implemented | `execute_segment-update` | — |
-
-### Read operations
-
-#### `segment-count`
-
-Trigger an asynchronous count of an audience segment by segmentApiName. Returns a job handle; poll for completion. Use to estimate audience size before publishing.
-
-**Call:** `execute_segment-count`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_count (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_segment-count) for the param schema and, where available, a worked example.
-
-#### `segment-get`
-
-Get a specific audience segment by its segmentApiName. Returns segment definition, criteria, and metadata.
-
-**Call:** `execute_segment-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_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_segment-get) for the param schema and, where available, a worked example.
-
-#### `segment-get-by-id`
-
-Get a specific audience segment by its 18-character segmentId (ID-typed lookup, distinct from d360_segment_get which uses segmentApiName). Returns segment definition, criteria, and metadata.
-
-**Call:** `execute_segment-get-by-id`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_get_by_id (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_segment-get-by-id) for the param schema and, where available, a worked example.
-
-#### `segment-list`
-
-List audience segments with batchSize/offset paging, ordering, and optional filters. Use d360_segment_get to fetch a single segment by API name.
-
-**Call:** `execute_segment-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_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_segment-list) for the param schema and, where available, a worked example.
-
-#### `segment-member-list`
-
-List members of an audience segment by segmentApiName. Supports pagination (limit/offset), ordering, field projection, and filtering. Use after d360_segment_publish to inspect the resolved audience.
-
-**Call:** `execute_segment-member-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_member_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_segment-member-list) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `segment-create`
-
-Create a new segment. DEPENDENCY: All CIs referenced in segment filters must be in ACTIVE status before creation. 
-
-**Call:** `execute_segment-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_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_segment-create) for the param schema and, where available, a worked example.
-
-#### `segment-deactivate`
-
-Deactivate an audience segment by segmentId. Stops scheduled publishes; existing audiences remain but are no longer regenerated.
-
-**Call:** `execute_segment-deactivate`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_deactivate (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_segment-deactivate) for the param schema and, where available, a worked example.
-
-#### `segment-deactivate-by-name`
-
-Deactivate an audience segment by segmentApiName (name-based; pair with d360_segment_deactivate which uses segmentId). Stops scheduled publishes; existing audiences remain but are no longer regenerated.
-
-**Call:** `execute_segment-deactivate-by-name`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_deactivate_by_name (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_segment-deactivate-by-name) for the param schema and, where available, a worked example.
-
-#### `segment-publish`
-
-Publish an audience segment on demand by segmentId. Triggers immediate evaluation and produces a fresh audience snapshot.
-
-**Call:** `execute_segment-publish`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_publish (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_segment-publish) for the param schema and, where available, a worked example.
-
-#### `segment-update`
-
-Update an existing audience segment by segmentApiName. Use to modify criteria, label, or metadata without recreating the segment.
-
-**Call:** `execute_segment-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_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_segment-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `segment-delete`
-
-Delete an audience segment by segmentApiName. Removes the segment definition; published audiences are no longer regenerated.
-
-**Call:** `execute_segment-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_segment_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_segment-delete) for the param schema and, where available, a worked example.

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

@@ -1,93 +0,0 @@
----
-name: data360-semantic-calculated-dimension-mcp-configure
-description: "Use this skill when users want to execute Data Cloud SemanticCalculatedDimension operations via the Data 360 MCP facade. Trigger when users mention data360/semantic, calculated, dimension, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/semantic Calculated Dimension
-
-## When to Use This Skill
-
-Execute Data Cloud SemanticCalculatedDimension 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-calc-dim-delete`** — Delete a calculated dimension 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-calc-dim-create` | write | implemented | `execute_sdm-calc-dim-create` | — |
-| `sdm-calc-dim-delete` | delete | implemented | `execute_sdm-calc-dim-delete` | — |
-| `sdm-calc-dim-get` | read | implemented | `execute_sdm-calc-dim-get` | — |
-| `sdm-calc-dim-update` | write | implemented | `execute_sdm-calc-dim-update` | — |
-| `sdm-calc-dims-list` | read | implemented | `execute_sdm-calc-dims-list` | — |
-
-### Read operations
-
-#### `sdm-calc-dim-get`
-
-Get a calculated dimension from a semantic model.
-
-**Call:** `execute_sdm-calc-dim-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_calc_dim_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-calc-dim-get) for the param schema and, where available, a worked example.
-
-#### `sdm-calc-dims-list`
-
-List calculated dimensions in a semantic model.
-
-**Call:** `execute_sdm-calc-dims-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_calc_dims_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-calc-dims-list) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `sdm-calc-dim-create`
-
-Create a calculated dimension in a semantic model. Body: { label, expression, dataType: 'Text'|'Number'|'DateTime' }. Formula syntax uses [DataObject].[Field] references (NOT {field}). Use IF/ELSEIF/ELSE/END for conditionals (not CASE WHEN). Example: IF [MyObj].[field1] > 10 THEN 'High' ELSE 'Low' END
-
-**Call:** `execute_sdm-calc-dim-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_calc_dim_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-calc-dim-create) for the param schema and, where available, a worked example.
-
-#### `sdm-calc-dim-update`
-
-Update a calculated dimension in a semantic model.
-
-**Call:** `execute_sdm-calc-dim-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_calc_dim_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-calc-dim-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `sdm-calc-dim-delete`
-
-Delete a calculated dimension from a semantic model.
-
-**Call:** `execute_sdm-calc-dim-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_calc_dim_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-calc-dim-delete) for the param schema and, where available, a worked example.

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

@@ -1,93 +0,0 @@
----
-name: data360-semantic-calculated-measurement-mcp-configure
-description: "Use this skill when users want to execute Data Cloud SemanticCalculatedMeasurement operations via the Data 360 MCP facade. Trigger when users mention data360/semantic, calculated, measurement, shared, cdp, mcp, connect, api, shared-cdp-mcp-connect-api."
-metadata:
-  version: "1.0"
----
-
-# Managing Data360/semantic Calculated Measurement
-
-## When to Use This Skill
-
-Execute Data Cloud SemanticCalculatedMeasurement 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-calc-measure-delete`** — Delete a calculated measurement 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-calc-measure-create` | write | implemented | `execute_sdm-calc-measure-create` | — |
-| `sdm-calc-measure-delete` | delete | implemented | `execute_sdm-calc-measure-delete` | — |
-| `sdm-calc-measure-get` | read | implemented | `execute_sdm-calc-measure-get` | — |
-| `sdm-calc-measure-update` | write | implemented | `execute_sdm-calc-measure-update` | — |
-| `sdm-calc-measures-list` | read | implemented | `execute_sdm-calc-measures-list` | — |
-
-### Read operations
-
-#### `sdm-calc-measure-get`
-
-Get a calculated measurement from a semantic model.
-
-**Call:** `execute_sdm-calc-measure-get`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_calc_measure_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-calc-measure-get) for the param schema and, where available, a worked example.
-
-#### `sdm-calc-measures-list`
-
-List calculated measurements in a semantic model.
-
-**Call:** `execute_sdm-calc-measures-list`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_calc_measures_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-calc-measures-list) for the param schema and, where available, a worked example.
-
-### Write operations
-
-#### `sdm-calc-measure-create`
-
-Create a calculated measurement in a semantic model. Body: { label, expression, dataType: 'Number', aggregationType: 'UserAgg' }. IMPORTANT: aggregationType 'UserAgg' is REQUIRED for any formula containing aggregation functions (SUM, COUNT, AVG, etc.). Formula syntax uses [DataObject].[Field] references. Use IIF(condition, true_val, false_val) for inline conditionals.
-
-**Call:** `execute_sdm-calc-measure-create`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_calc_measure_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-calc-measure-create) for the param schema and, where available, a worked example.
-
-#### `sdm-calc-measure-update`
-
-Update a calculated measurement in a semantic model.
-
-**Call:** `execute_sdm-calc-measure-update`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_calc_measure_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-calc-measure-update) for the param schema and, where available, a worked example.
-
-### Destructive operations
-
-#### `sdm-calc-measure-delete`
-
-Delete a calculated measurement from a semantic model.
-
-**Call:** `execute_sdm-calc-measure-delete`   — status: `implemented`
-
-**Inputs:**
-
-- `paramsJson` *(`string`)* — JSON-encoded params for d360_sdm_calc_measure_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-calc-measure-delete) for the param schema and, where available, a worked example.