@salesforce/afv-skills 1.58.0 → 1.60.0

package/skills/omnistudio-dependencies-analyze/SKILL.md

@@ -2,9 +2,8 @@
 name: omnistudio-dependencies-analyze
 description: "Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, requests dependency graphs or Mermaid diagrams, or asks which components are affected by a change. DO NOT TRIGGER when: authoring OmniScripts (use omnistudio-omniscript-generate), building FlexCards (use omnistudio-flexcard-generate), creating Integration Procedures (use omnistudio-integration-procedure-generate), or configuring Data Mappers (use omnistudio-datamapper-generate)."
 metadata:
-  cliTools:
-    - tool: ["sf"]
-      semver: ">=2.0.0"
+  version: "1.0"
+  domains: ["OmniStudio"]
   relatedSkills:
     - "external-diagram-mermaid-generate"
     - "omnistudio-datamapper-generate"
@@ -14,8 +13,9 @@ metadata:
     - "platform-custom-field-generate"
     - "platform-custom-object-generate"
     - "platform-metadata-deploy"
-  version: "1.0"
-  domains: ["OmniStudio"]
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
 ---
 
 # omnistudio-dependencies-analyze: OmniStudio Cross-Component Analysis

package/skills/omnistudio-epc-catalog-generate/SKILL.md

@@ -2,9 +2,9 @@
 name: omnistudio-epc-catalog-generate
 description: "Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use omnistudio-omniscript-generate, omnistudio-flexcard-generate, or omnistudio-integration-procedure-generate), implementing Apex business logic (use platform-apex-generate), or troubleshooting deployment pipelines (use platform-metadata-deploy)."
 metadata:
-  cliTools:
-    - tool: ["sf"]
-      semver: ">=2.0.0"
+  version: "1.0"
+  domains: ["OmniStudio"]
+  minApiVersion: "60.0"
   relatedSkills:
     - "omnistudio-callable-apex-generate"
     - "omnistudio-dependencies-analyze"
@@ -16,9 +16,9 @@ metadata:
     - "platform-custom-object-generate"
     - "platform-metadata-deploy"
     - "platform-soql-query"
-  version: "1.0"
-  domains: ["OmniStudio"]
-  minApiVersion: "60.0"
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
 ---
 
 # omnistudio-epc-catalog-generate: CME EPC Product and Offer Modeling

package/skills/omnistudio-flexcard-generate/SKILL.md

@@ -2,9 +2,9 @@
 name: omnistudio-flexcard-generate
 description: "OmniStudio FlexCard creation and validation with 130-point scoring. Use when building at-a-glance UI cards, configuring data source bindings to Integration Procedures, or reviewing existing FlexCard definitions for accessibility and performance. TRIGGER when: user creates FlexCards, configures data sources, designs card layouts, or asks about OmniUiCard metadata. DO NOT TRIGGER when: building OmniScripts (use omnistudio-omniscript-generate), creating Integration Procedures (use omnistudio-integration-procedure-generate), or analyzing dependencies (use omnistudio-dependencies-analyze)."
 metadata:
-  cliTools:
-    - tool: ["sf"]
-      semver: ">=2.0.0"
+  version: "1.0"
+  domains: ["OmniStudio"]
+  minApiVersion: "60.0"
   relatedSkills:
     - "experience-lwc-generate"
     - "omnistudio-datamapper-generate"
@@ -12,9 +12,9 @@ metadata:
     - "omnistudio-integration-procedure-generate"
     - "omnistudio-omniscript-generate"
     - "platform-metadata-deploy"
-  version: "1.0"
-  domains: ["OmniStudio"]
-  minApiVersion: "60.0"
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
 ---
 
 # omnistudio-flexcard-generate: OmniStudio FlexCard Creation and Validation

package/skills/omnistudio-integration-procedure-generate/SKILL.md

@@ -2,9 +2,9 @@
 name: omnistudio-integration-procedure-generate
 description: "OmniStudio Integration Procedure creation and validation with 110-point scoring. Use this skill when building server-side process orchestrations that combine Data Mapper actions, Apex Remote Actions, HTTP callouts, and conditional logic. TRIGGER when: user creates Integration Procedures, adds Data Mapper steps, configures Remote Actions, or reviews existing IP configurations. DO NOT TRIGGER when: building OmniScripts (use omnistudio-omniscript-generate), creating Data Mappers directly (use omnistudio-datamapper-generate), or analyzing cross-component dependencies (use omnistudio-dependencies-analyze)."
 metadata:
-  cliTools:
-    - tool: ["sf"]
-      semver: ">=2.0.0"
+  version: "1.0"
+  domains: ["OmniStudio"]
+  minApiVersion: "60.0"
   relatedSkills:
     - "omnistudio-datamapper-generate"
     - "omnistudio-dependencies-analyze"
@@ -12,9 +12,9 @@ metadata:
     - "omnistudio-omniscript-generate"
     - "platform-apex-generate"
     - "platform-metadata-deploy"
-  version: "1.0"
-  domains: ["OmniStudio"]
-  minApiVersion: "60.0"
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
 ---
 
 # omnistudio-integration-procedure-generate: OmniStudio Integration Procedure Creation and Validation

package/skills/omnistudio-omniscript-generate/SKILL.md

@@ -2,17 +2,18 @@
 name: omnistudio-omniscript-generate
 description: "OmniStudio OmniScript creation and validation with 120-point scoring. Use when building guided digital experiences, multi-step forms, or interactive processes that orchestrate Integration Procedures and Data Mappers. TRIGGER when: user creates OmniScripts, designs step flows, configures element types, or reviews existing OmniScript configurations. DO NOT TRIGGER when: building FlexCards (use omnistudio-flexcard-generate), creating Integration Procedures directly (use omnistudio-integration-procedure-generate), or analyzing dependencies (use omnistudio-dependencies-analyze)."
 metadata:
-  cliTools:
-    - tool: ["sf"]
-      semver: ">=2.0.0"
+  version: "1.0"
+  domains: ["OmniStudio"]
+  minApiVersion: "66.0"
   relatedSkills:
     - "omnistudio-datamapper-generate"
     - "omnistudio-dependencies-analyze"
     - "omnistudio-flexcard-generate"
     - "omnistudio-integration-procedure-generate"
     - "platform-metadata-deploy"
-  version: "1.0"
-  domains: ["OmniStudio"]
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
 ---
 
 # omnistudio-omniscript-generate: OmniStudio OmniScript Creation and Validation

package/skills/platform-apex-logs-debug/SKILL.md

@@ -151,6 +151,7 @@ Verify: <test or rerun step>
 | Reproduce via tests | [platform-apex-test-run](../platform-apex-test-run/SKILL.md) | test execution and coverage loop |
 | Deploy fix | [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md) | deployment orchestration |
 | Create debugging data | [platform-data-manage](../platform-data-manage/SKILL.md) | targeted seed / repro data |
+| Optimize slow SOQL queries | [platform-soql-query](../platform-soql-query/SKILL.md) | query shape / performance tuning |
 
 ---
 

package/skills/platform-metadata-deploy/SKILL.md

@@ -188,6 +188,7 @@ For full agent DevOps details, including `Agent:` pseudo metadata, publish/activ
 | custom object creation | [platform-custom-object-generate](../platform-custom-object-generate/SKILL.md) | define objects before deploy |
 | custom field creation | [platform-custom-field-generate](../platform-custom-field-generate/SKILL.md) | define fields before deploy |
 | Apex authoring / fixes | [platform-apex-generate](../platform-apex-generate/SKILL.md) | code authoring and repair |
+| run tests after deployment | [platform-apex-test-run](../platform-apex-test-run/SKILL.md) | post-deploy test execution and coverage |
 | Flow creation / repair | [automation-flow-generate](../automation-flow-generate/SKILL.md) | Flow authoring and activation guidance |
 | test data or seed records | [platform-data-manage](../platform-data-manage/SKILL.md) | describe-first data setup and cleanup |
 | Agent authoring and publish readiness | [agentforce-generate](../agentforce-generate/SKILL.md) | agent-specific correctness |

package/skills/platform-models-api-configure/SKILL.md

@@ -2,6 +2,11 @@
 name: platform-models-api-configure
 description: "Configure (or troubleshoot) an AI coding agent or CLI to route through the Salesforce Models API using a signed OrgJWT. Use this skill when pointing an agent at the Salesforce model endpoint (api.salesforce.com/ai/gpt/v1), setting up OrgJWT / Bedrock-mode auth, wiring the agent's settings, API-key helper, and credentials file for the Salesforce endpoint, or fixing Models API 401 / 404 / \"model not available\" errors. DO NOT TRIGGER when the user needs to create or configure the Salesforce Connected App itself (use integration-connectivity-connected-app-configure) or set up Named Credentials / callout auth (use integration-connectivity-generate)."
 metadata:
+  version: "1.0"
+  domains: ["Platform", "Agentforce"]
+  relatedSkills:
+    - "integration-connectivity-connected-app-configure"
+    - "integration-connectivity-generate"
   cliTools:
     - tool: ["curl"]
       semver: ">=7.29.0"
@@ -9,11 +14,6 @@ metadata:
       semver: ">=1.6.0"
     - tool: ["sf"]
       semver: ">=2.0.0"
-  relatedSkills:
-    - "integration-connectivity-connected-app-configure"
-    - "integration-connectivity-generate"
-  version: "1.0"
-  domains: ["Platform", "Agentforce"]
 ---
 
 # Salesforce Models API setup for an AI coding agent

package/skills/platform-soql-query/SKILL.md

@@ -122,6 +122,7 @@ Next step: <run in platform-data-manage or embed in Apex>
 | embed the query in services/selectors | [platform-apex-generate](../platform-apex-generate/SKILL.md) | implementation context |
 | analyze slow-query symptoms from logs | [platform-apex-logs-debug](../platform-apex-logs-debug/SKILL.md) | runtime evidence |
 | wire query-backed UI | [experience-lwc-generate](../experience-lwc-generate/SKILL.md) | frontend integration |
+| validate query behavior in tests | [platform-apex-test-run](../platform-apex-test-run/SKILL.md) | test coverage for query logic |
 
 ---
 

package/skills/service-itsm-agentic-setup-cmdb-coordinate/SKILL.md

@@ -2,7 +2,7 @@
 name: service-itsm-agentic-setup-cmdb-coordinate
 description: "Orchestrator skill for enabling CMDB (Configuration Management Database) end-to-end in Service Cloud ITSM against a production or sandbox org. Use when the user asks to set up CMDB, enable Configuration Management Database, configure the ITSM CMDB, onboard CMDB from scratch, wants a guided walkthrough of CMDB enablement, or asks what CMDB setup steps are available. Triggers on: set up CMDB, enable CMDB, configure CMDB, CMDB onboarding, Configuration Management Database setup, ITSM CMDB walkthrough. DO NOT TRIGGER when: the user asks about a specific CMDB sub-step directly (e.g. only installing a bundle, only assigning permission sets), CMDB record CRUD (creating CIs, relationships), Discovery/Service Graph Connector configuration, or general ITSM queries without CMDB setup intent."
 metadata:
-  version: "1.0"
+  version: "1.1"
   domains: ["Service"]
   relatedSkills:
     - "service-itsm-agentic-setup-cmdb-access-assign"
@@ -45,7 +45,10 @@ Layer 3  User access            Assign the PSL + CMDB permission sets to the use
 Layer 4  Content bundles        Install the CMDB Foundation (base) content bundle.
 Layer 5  Asset Discovery        Enable feature service-cloud-itsm-discovery-integration and grant
                                 Discovery page access (IT Service Discovery Manager permission set).
-                                Runs last — depends on the base CMDB feature and earlier layers.
+                                Recommended last, but a direct enable CASCADE-ENABLES the base CMDB
+                                feature — it needs only Layer 0 (license) + Layer 1 (provisioned
+                                tenant), NOT Layers 2–4 done first. Never claim a direct enable
+                                "will fail"; only a genuine blocker (e.g. tenant not provisioned) stops it.
 ```
 
 Layer 0 is a hard prerequisite: if the org was not born with the CMDB SKU, **no API can grant it**
@@ -79,7 +82,8 @@ CMDB Setup (via service-itsm-agentic-setup-cmdb-coordinate)
 
 Target org: <org>   (all steps below run against this org)
 
-CMDB is enabled in ordered layers. Each must succeed before the next:
+CMDB is set up in ordered layers, each building on the earlier ones (Asset Discovery is the
+exception — see its note below):
 ```
 
 | #   | Layer                    | What it does                                                 | Status  |
@@ -88,7 +92,7 @@ CMDB is enabled in ordered layers. Each must succeed before the next:
 | 1–2 | Provision & enable CMDB  | Set up the CMDB tenant, then turn on the CMDB feature so it's available to use | Pending |
 | 3   | Assign user access       | Grant CMDB access to the chosen users                        | Pending |
 | 4   | Install content bundle   | Install the CMDB Foundation (base) content                   | Pending |
-| 5   | Enable Asset Discovery   | Turn on asset discovery and grant Discovery page access (final step — needs the steps above done first) | Pending |
+| 5   | Enable Asset Discovery   | Turn on asset discovery and grant Discovery page access (recommended last; enabling it directly turns the base CMDB feature on too — needs only the license and a provisioned tenant, not the other layers first) | Pending |
 
 ```text
 I recommend running these in order. Where would you like to start (or shall I run 1 → 5)?
@@ -154,8 +158,10 @@ Configuration Items. Next, you can model CIs, identification rules, and relation
 3. User access             (PSL + permission sets; without these users can't see CMDB)
 4. Content bundle          (CMDB Foundation base; requires Layer 2 — bundle APIs 403 until enabled)
 5. Asset Discovery         (enable service-cloud-itsm-discovery-integration and grant Discovery page
-                           access via the IT Service Discovery Manager permission set; final layer —
-                           requires the base CMDB feature and earlier layers; blocked until done)
+                           access via the IT Service Discovery Manager permission set; recommended
+                           last, but a direct enable CASCADE-ENABLES the base CMDB feature — needs
+                           only Layer 0 license + Layer 1 provisioned tenant, not Layers 2–4; never
+                           tell the user a direct enable "will fail")
 ```
 
 Layers 1 and 2 are handled together by `service-itsm-agentic-setup-cmdb-configure` because Layer 2
@@ -174,6 +180,11 @@ cannot succeed until Layer 1 reaches `PROVISIONED`. Present them as one step.
   license/edition prerequisite that no API can grant
 - If a child skill reports a prerequisite gap or a failure, relay it to the user in friendly,
   actionable terms — do not bury the error
+- When the user asks to run **Layer 5 (Asset Discovery) directly**, do NOT warn that it "will fail"
+  or "error out" without the earlier layers, and do NOT push "run the full flow" as a precondition.
+  Enabling Discovery **cascade-enables** the base CMDB feature; it needs only Layer 0 (license) and a
+  Layer 1 provisioned tenant. Delegate straight to `service-itsm-agentic-setup-cmdb-discovery-configure`,
+  which reads the feature status first and stops only on a genuine blocker (e.g. tenant not provisioned)
 - Track progress across the conversation — do not re-present completed layers as "Pending". Re-derive the current layer from the latest child-skill activity, not from a previously rendered highlight; on a resumed or long conversation, do not assume the last-highlighted layer is still current — if ambiguous, re-confirm with the user
 - Do NOT expose internal technical jargon in user-facing output. This includes Salesforce record
   IDs and org IDs, raw HTTP status codes (403, 500, …), API error codes (`FUNCTIONALITY_NOT_ENABLED`,