@salesforce/afv-skills 1.22.0 → 1.24.0

package/package.json

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

package/skills/{developing-datacloud-code-extension → data360-code-extension-generate}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: developing-datacloud-code-extension
+name: data360-code-extension-generate
 description: "Develop and deploy Data Cloud Code Extensions using SF CLI plugin. Use this skill when creating custom Python transformations for Data Cloud, deploying code extensions, or testing data transformations. Supports init, run, scan, and deploy operations."
 metadata:
   version: "1.0"
 ---
 
-# developing-datacloud-code-extension Skill
+# data360-code-extension-generate Skill
 
 ## Overview
 
@@ -79,7 +79,7 @@ sf data-code-extension function init --package-dir <directory>
 - `--package-dir, -p` - Directory path where the package will be created
 
 **What it creates:**
-```
+```text
 my-transform/              # Project root
 ├── payload/               # CRITICAL: This is what --package-dir must point to for deploy
 │   ├── entrypoint.py      # Main transformation code
@@ -172,7 +172,7 @@ cat payload/config.json
 
 #### Step 4b: Validate Each DLO Schema
 
-**Use the `getting-datacloud-schema` skill to verify DLOs exist and check field names.**
+**Use the `data360-schema-get` skill to verify DLOs exist and check field names.**
 
 For each DLO referenced in your code:
 
@@ -260,7 +260,7 @@ sf data-code-extension script deploy --target-org <org_alias> --name <name> --pa
 | `Cannot connect to Docker daemon` | Start Docker Desktop |
 | `No org found for alias` | `sf org login web --alias <org_alias>` |
 | `config.json not found` | `sf data-code-extension script scan --entrypoint ./payload/entrypoint.py` |
-| `DLO not found` | Verify DLO exists (use getting-datacloud-schema skill), check spelling and `__dll` suffix |
+| `DLO not found` | Verify DLO exists (use data360-schema-get skill), check spelling and `__dll` suffix |
 | `Permission denied writing` | Re-run scan, verify target DLO exists and is writable |
 | `Deploy fails - wrong directory` | Ensure `--package-dir` points to `payload/` directory, not project root |
 
@@ -285,9 +285,9 @@ sf data-code-extension script deploy --target-org <org_alias> --name <name> --pa
 
 ## Integration with Other Skills
 
-**Use with getting-datacloud-schema skill (CRITICAL for validation):**
+**Use with data360-schema-get skill (CRITICAL for validation):**
 
-The `getting-datacloud-schema` skill is **required** for validating DLOs before testing code extensions.
+The `data360-schema-get` skill is **required** for validating DLOs before testing code extensions.
 
 **Use with Datakit Workflow:**
 1. Create DLO via code extension

package/skills/{developing-datacloud-code-extension → data360-code-extension-generate}/references/README.md

@@ -1,4 +1,4 @@
-# developing-datacloud-code-extension Skill
+# data360-code-extension-generate Skill
 
 ## Overview
 
@@ -17,25 +17,25 @@ This skill helps you create Data Cloud Code Extensions through a complete workfl
 ## Usage
 
 **Initialize a project:**
-```
+```text
 "Create a new Data Cloud code extension project called employee-transform"
 "Initialize a code extension to transform employee data"
 ```
 
 **Test locally:**
-```
+```text
 "Run the code extension in my-transform directory against afvibe org"
 "Test the entrypoint.py file locally"
 ```
 
 **Scan for permissions:**
-```
+```text
 "Scan the entrypoint.py to generate config"
 "Update permissions in config.json"
 ```
 
 **Deploy:**
-```
+```text
 "Deploy Employee_Upper code extension to afvibe"
 "Deploy this transform with package-version 1.0.0"
 ```
@@ -135,7 +135,7 @@ print(f"Processed {len(output)} employee records")
 
 After `init`, you'll have:
 
-```
+```text
 my-transform/
 ├── payload/
 │   ├── entrypoint.py      # Your transformation code
@@ -173,7 +173,7 @@ client.write_to_dmo('EmployeeDMO', df, 'upsert')
 | Wrong Python version | Use pyenv to install 3.11.0 |
 | Org not connected | `sf org login web --alias <alias>` |
 | Config missing | Run scan command |
-| DLO not found | Check DLO name, use getting-datacloud-schema skill |
+| DLO not found | Check DLO name, use data360-schema-get skill |
 | Docker error | Start Docker Desktop |
 
 ## CPU Size Selection

package/skills/{developing-datacloud-code-extension → data360-code-extension-generate}/references/quick-reference.md

@@ -215,7 +215,7 @@ sf data-code-extension script scan --entrypoint ./payload/entrypoint.py
 
 ## File Structure
 
-```
+```text
 my-project/
 ├── payload/
 │   ├── entrypoint.py      # Main code
@@ -248,7 +248,7 @@ my-project/
 | Wrong Python version | Use pyenv to install 3.11.0 |
 | Org not connected | `sf org login web --alias <alias>` |
 | Config missing | Run scan command |
-| DLO not found | Check DLO name, use getting-datacloud-schema skill |
+| DLO not found | Check DLO name, use data360-schema-get skill |
 | Docker error | Start Docker Desktop |
 
 ## Deployment Checklist

package/skills/{getting-datacloud-schema → data360-schema-get}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: getting-datacloud-schema
+name: data360-schema-get
 description: "Retrieve Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using REST APIs. Use this skill when you need to inspect DLO or DMO field definitions, data types, or metadata. Takes org alias and optional DLO/DMO name as parameters."
 metadata:
   version: "1.0"
 ---
 
-# getting-datacloud-schema Skill
+# data360-schema-get Skill
 
 
 ## Overview
@@ -42,7 +42,7 @@ sf org list
 ```
 
 Example output:
-```
+```text
 ┌────┬───────┬──────────────────────────┬────────────────────┬───────────┐
 │    │ Alias │ Username                 │ Org Id             │ Status    │
 ├────┼───────┼──────────────────────────┼────────────────────┼───────────┤
@@ -67,28 +67,28 @@ sf org login web --alias <org_alias>
 
 ### Step 3a: Execute DLO Schema Script
 
-The Python scripts are bundled with this skill. They live in the `scripts/` subdirectory of the same directory that contains this SKILL.md file. Use the absolute path to that directory — do NOT use `./scripts/` as that resolves relative to the current working directory, not the skill directory.
+The Python scripts are bundled with this skill in the `scripts/` subdirectory.
 
 **To list all DLOs:**
 ```bash
-python3 <skill_dir>/scripts/get_dlo_schema.py <org_alias>
+python3 ./scripts/get_dlo_schema.py <org_alias>
 ```
 
 **To get specific DLO schema:**
 ```bash
-python3 <skill_dir>/scripts/get_dlo_schema.py <org_alias> <dlo_name>
+python3 ./scripts/get_dlo_schema.py <org_alias> <dlo_name>
 ```
 
 ### Step 3b: Execute DMO Schema Script
 
 **To list all DMOs:**
 ```bash
-python3 <skill_dir>/scripts/get_dmo_schema.py <org_alias>
+python3 ./scripts/get_dmo_schema.py <org_alias>
 ```
 
 **To get specific DMO schema:**
 ```bash
-python3 <skill_dir>/scripts/get_dmo_schema.py <org_alias> <dmo_name>
+python3 ./scripts/get_dmo_schema.py <org_alias> <dmo_name>
 ```
 
 ### Step 4: Present Results
@@ -135,7 +135,7 @@ After displaying results, suggest relevant follow-up actions:
 ## API Endpoints Used
 
 ### List All DLOs
-```
+```text
 GET /services/data/v64.0/ssot/data-lake-objects
 ```
 
@@ -158,14 +158,14 @@ Response structure:
 ```
 
 ### Get DLO Schema
-```
+```text
 GET /services/data/v64.0/ssot/data-lake-objects/{dlo_name}
 ```
 
 Response structure (same as individual object in list response, but wrapped in paginated format).
 
 ### List All DMOs
-```
+```text
 GET /services/data/v64.0/ssot/data-model-objects
 ```
 
@@ -186,7 +186,7 @@ Response structure:
 ```
 
 ### Get DMO Schema
-```
+```text
 GET /services/data/v64.0/ssot/data-model-objects/{dmo_name}
 ```
 
@@ -219,29 +219,29 @@ Response structure (same as individual object in list response, but wrapped in p
 ## Example Usage
 
 **Example 1: List all DLOs**
-```
+```text
 User: "Show me all DLOs in afvibe org"
 
 Response:
 1. Run sf org list to discover connected org alias
 2. Authenticate to afvibe
-3. Run: python3 <skill_dir>/scripts/get_dlo_schema.py afvibe
+3. Run: python3 ./scripts/get_dlo_schema.py afvibe
 4. Display formatted list of DLOs
 ```
 
 **Example 2: Get specific DLO schema**
-```
+```text
 User: "Get the schema for Employee__dll in afvibe"
 
 Response:
 1. Run sf org list to discover connected org alias
 2. Authenticate to afvibe
-3. Run: python3 <skill_dir>/scripts/get_dlo_schema.py afvibe Employee__dll
+3. Run: python3 ./scripts/get_dlo_schema.py afvibe Employee__dll
 4. Display field schema with types and metadata
 ```
 
 **Example 3: Explore DLOs then get schema**
-```
+```text
 User: "What DLOs exist in myorg and show me the schema for the Employee one"
 
 Response:
@@ -253,29 +253,29 @@ Response:
 ```
 
 **Example 4: List all DMOs**
-```
+```text
 User: "Show me all DMOs in afvibe org"
 
 Response:
 1. Run sf org list to discover connected org alias
 2. Authenticate to afvibe
-3. Run: python3 <skill_dir>/scripts/get_dmo_schema.py afvibe
+3. Run: python3 ./scripts/get_dmo_schema.py afvibe
 4. Display formatted list of DMOs
 ```
 
 **Example 5: Get specific DMO schema**
-```
+```text
 User: "Get the schema for Individual__dlm in afvibe"
 
 Response:
 1. Run sf org list to discover connected org alias
 2. Authenticate to afvibe
-3. Run: python3 <skill_dir>/scripts/get_dmo_schema.py afvibe Individual__dlm
+3. Run: python3 ./scripts/get_dmo_schema.py afvibe Individual__dlm
 4. Display field schema with types and metadata
 ```
 
 **Example 6: Explore DMOs then get schema**
-```
+```text
 User: "What DMOs exist in myorg and show me the schema for the Individual one"
 
 Response:
@@ -289,7 +289,7 @@ Response:
 ## Output Format
 
 ### DLO List Output
-```
+```text
 Found 5 DLOs in org 'afvibe':
 
 1. DataCustomCodeLogs__dll
@@ -306,7 +306,7 @@ Found 5 DLOs in org 'afvibe':
 ```
 
 ### DLO Schema Output
-```
+```yaml
 DLO: Employee__dll
 Label: Employee
 Category: Profile
@@ -331,7 +331,7 @@ Next steps:
 ```
 
 ### DMO List Output
-```
+```text
 Found 10 DMOs in org 'afvibe':
 
 1. Individual__dlm
@@ -346,7 +346,7 @@ Found 10 DMOs in org 'afvibe':
 ```
 
 ### DMO Schema Output
-```
+```yaml
 DMO: Individual__dlm
 Label: Individual
 Category: Profile

package/skills/{getting-datacloud-schema → data360-schema-get}/references/README.md

@@ -1,4 +1,4 @@
-# getting-datacloud-schema Skill
+# data360-schema-get Skill
 
 ## Overview
 
@@ -7,25 +7,25 @@ A skill that retrieves Data Lake Object (DLO) and Data Model Object (DMO) schema
 ## Usage
 
 **List all DLOs:**
-```
+```text
 "Show me all DLOs in afvibe org"
 "List Data Lake Objects in myorg"
 ```
 
 **Get specific DLO schema:**
-```
+```text
 "Get the schema for Employee__dll in afvibe"
 "What fields does the Employee__dll DLO have in myorg?"
 ```
 
 **List all DMOs:**
-```
+```text
 "Show me all DMOs in afvibe org"
 "List Data Model Objects in myorg"
 ```
 
 **Get specific DMO schema:**
-```
+```text
 "Get the schema for Individual__dlm in afvibe"
 "What fields does the Individual__dlm DMO have in myorg?"
 ```
@@ -116,7 +116,7 @@ python3 scripts/get_dmo_schema.py afvibe Individual__dlm
 ## Output Format
 
 ### DLO List
-```
+```text
 Found 5 DLOs in org 'afvibe':
 
 1. DataCustomCodeLogs__dll
@@ -131,7 +131,7 @@ Found 5 DLOs in org 'afvibe':
 ```
 
 ### DLO Schema
-```
+```text
 DLO: Employee__dll
 Label: Employee
 Category: Profile
@@ -148,7 +148,7 @@ Fields (9 total):
 ```
 
 ### DMO List
-```
+```text
 Found 10 DMOs in org 'afvibe':
 
 1. Individual__dlm
@@ -161,7 +161,7 @@ Found 10 DMOs in org 'afvibe':
 ```
 
 ### DMO Schema
-```
+```text
 DMO: Individual__dlm
 Label: Individual
 Category: Profile

package/skills/activating-datacloud/README.md

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

package/skills/activating-datacloud/SKILL.md

@@ -1,117 +0,0 @@
----
-name: activating-datacloud
-description: "Salesforce Data Cloud Act phase. Use this skill when the user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. TRIGGER when: user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. DO NOT TRIGGER when: the task is segment creation (use segmenting-datacloud), data retrieval/search work (use retrieving-datacloud), or STDM/session tracing (use observing-agentforce)."
-compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
-metadata:
-  version: "1.0"
----
-
-# activating-datacloud: Data Cloud Act Phase
-
-Use this skill when the user needs **downstream delivery work**: activations, activation targets, data actions, or pushing Data Cloud outputs into other systems.
-
-## When This Skill Owns the Task
-
-Use `activating-datacloud` when the work involves:
-- `sf data360 activation *`
-- `sf data360 activation-target *`
-- `sf data360 data-action *`
-- `sf data360 data-action-target *`
-- verifying downstream delivery setup
-
-Delegate elsewhere when the user is:
-- still building the audience or insight → [segmenting-datacloud](../segmenting-datacloud/SKILL.md)
-- exploring query/search or search indexes → [retrieving-datacloud](../retrieving-datacloud/SKILL.md)
-- setting up base connections or ingestion → [connecting-datacloud](../connecting-datacloud/SKILL.md), [preparing-datacloud](../preparing-datacloud/SKILL.md)
-
----
-
-## Required Context to Gather First
-
-Ask for or infer:
-- target org alias
-- destination platform or downstream system
-- whether the segment already exists and is published
-- whether the user needs create, inspect, update, or delete
-- whether the task is activation-focused or data-action-focused
-
----
-
-## Core Operating Rules
-
-- Verify the upstream segment or insight is healthy before creating downstream delivery assets.
-- Run the shared readiness classifier before mutating activation assets: `node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json`.
-- Inspect available platforms and targets before mutating activation setup.
-- Keep destination definitions deterministic and reusable where possible.
-- Treat downstream credential and platform constraints as separate validation concerns.
-- Prefer read-only inspection first when the destination state is unclear.
-
----
-
-## Recommended Workflow
-
-### 1. Classify readiness for act work
-```bash
-node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json
-```
-
-### 2. Inspect destinations first
-```bash
-sf data360 activation platforms -o <org> 2>/dev/null
-sf data360 activation-target list -o <org> 2>/dev/null
-sf data360 data-action-target list -o <org> 2>/dev/null
-```
-
-### 3. Create the destination before the activation
-```bash
-sf data360 activation-target create -o <org> -f target.json 2>/dev/null
-sf data360 data-action-target create -o <org> -f target.json 2>/dev/null
-```
-
-### 4. Create the activation or data action
-```bash
-sf data360 activation create -o <org> -f activation.json 2>/dev/null
-sf data360 data-action create -o <org> -f action.json 2>/dev/null
-```
-
-### 5. Verify downstream readiness
-```bash
-sf data360 activation list -o <org> 2>/dev/null
-sf data360 activation data -o <org> --name <activation> 2>/dev/null
-```
-
----
-
-## High-Signal Gotchas
-
-- Activation design depends on a healthy published upstream segment.
-- Destination configuration usually comes before activation creation.
-- Downstream credential and platform constraints may live outside the Data Cloud CLI alone.
-- Read-only inspection is the safest first move when the destination setup is unclear.
-- `CdpActivationTarget` or `CdpActivationExternalPlatform` means the activation surface is gated for the current org/user; guide the user toward activation setup, permissions, and destination configuration instead of retrying blindly.
-
----
-
-## Output Format
-
-```text
-Act task: <activation / activation-target / data-action / data-action-target>
-Destination: <platform or target>
-Target org: <alias>
-Artifacts: <definition files / commands>
-Verification: <listed / created / blocked>
-Next step: <destination validation or downstream testing>
-```
-
----
-
-## References
-
-- [README.md](README.md)
-- [../orchestrating-datacloud/assets/definitions/activation-target.template.json](../orchestrating-datacloud/assets/definitions/activation-target.template.json)
-- [../orchestrating-datacloud/assets/definitions/activation.template.json](../orchestrating-datacloud/assets/definitions/activation.template.json)
-- [../orchestrating-datacloud/assets/definitions/data-action-target.template.json](../orchestrating-datacloud/assets/definitions/data-action-target.template.json)
-- [../orchestrating-datacloud/assets/definitions/data-action.template.json](../orchestrating-datacloud/assets/definitions/data-action.template.json)
-- [../orchestrating-datacloud/UPSTREAM.md](../orchestrating-datacloud/UPSTREAM.md)
-- [../orchestrating-datacloud/references/plugin-setup.md](../orchestrating-datacloud/references/plugin-setup.md)
-- [../orchestrating-datacloud/references/feature-readiness.md](../orchestrating-datacloud/references/feature-readiness.md)

package/skills/analyzing-omnistudio-dependencies/CREDITS.md

@@ -1,5 +0,0 @@
-# Credits & Acknowledgments
-
-This skill draws on established patterns and platform knowledge from the broader OmniStudio ecosystem.
-
----