@salesforce/afv-skills 1.33.0 → 1.34.0

package/package.json

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

package/skills/agentforce-architecture-analyze/SKILL.md

@@ -3,6 +3,14 @@ name: agentforce-architecture-analyze
 description: "Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins. Renders a human-readable architecture document and Mermaid invocation graph from design-time metadata (not runtime audit rows). TRIGGER when user asks to describe, diagram, inventory, audit, document, or diff (e.g. v3 vs v5) the architecture / action tree / topic structure / tool inventory of a specific agent by agent API name in a specific org. DO NOT TRIGGER for runtime session traces, conversation transcripts, generation timings, or gateway audit chains — this skill reads design-time metadata only (use agentforce-d360-analyze for session traces)."
 metadata:
   version: "1.0"
+  minApiVersion: "64.0"
+  relatedSkills:
+    - "agentforce-d360-analyze"
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.136.8"
+    - tool: ["python3"]
+      semver: ">=3.10.0"
 ---
 
 # agentforce-architecture-analyze — declared architecture snapshot

package/skills/agentforce-bot-upgrade/SKILL.md

@@ -7,8 +7,6 @@ metadata:
   minApiVersion: "63.0"
   relatedSkills:
     - "agentforce-generate"
-    - "agentforce-test"
-    - "agentforce-observe"
   cliTools:
     - tool: ["sf"]
       semver: ">=2.0.0"

package/skills/agentforce-d360-analyze/SKILL.md

@@ -2,7 +2,15 @@
 name: agentforce-d360-analyze
 description: "Data Cloud 360° view of a single Agentforce session. TRIGGER when user asks to trace, inspect, summarize, or describe a specific Agentforce session by session id (Agent Session UUID `019d…` or MessagingSession id `0Mw…`). Also triggers on session discovery — find/list/search sessions by time, agent, channel, outcome, or conversation text — when the user has no session id yet. DO NOT TRIGGER for design-time architecture questions (use agentforce-architecture-analyze instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud."
 metadata:
+  cliTools:
+    - tool: ["python3"]
+      semver: ">=3.10.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "agentforce-architecture-analyze"
   version: "1.0"
+  minApiVersion: "66.0"
 ---
 
 # agentforce-d360-analyze — Data Cloud 360° session view

package/skills/agentforce-observe/SKILL.md

@@ -3,6 +3,9 @@ name: agentforce-observe
 description: "Analyze production Agentforce agent behavior using session traces and Data Cloud. TRIGGER when: user queries STDM session data or Data Cloud trace records; investigates production agent failures, regressions, or performance issues; asks about session traces, conversation logs, or agent metrics; wants to reproduce a reported production issue in preview; runs findSessions or trace analysis queries. DO NOT TRIGGER when: user creates, modifies, or debugs .agent files during development (use agentforce-generate); writes or runs test specs (use agentforce-test); uses sf agent preview for local development iteration; deploys or publishes agents."
 allowed-tools: Bash Read Write Edit Glob Grep
 metadata:
+  relatedSkills:
+    - "agentforce-generate"
+    - "agentforce-test"
   version: "0.8"
   cliTools:
     - tool: ["git"]

package/skills/agentforce-test/SKILL.md

@@ -3,6 +3,9 @@ name: agentforce-test
 description: "Write, run, and analyze structured test suites for Agentforce agents — functional AND security. TRIGGER when: user writes or modifies test spec YAML (AiEvaluationDefinition); runs sf agent test create, run, run-eval, or results commands; asks about test coverage strategy, metric selection, or custom evaluations; interprets test results or diagnoses test failures; asks about batch testing, regression suites, or CI/CD test integration; requests security testing, OWASP LLM Top 10, red-teaming, penetration testing, prompt-injection tests, a security grade, or a vulnerability assessment of an agent. DO NOT TRIGGER when: user creates, modifies, previews, or debugs .agent files (use agentforce-generate); deploys or publishes agents; writes Agent Script code; uses sf agent preview for development iteration; analyzes production session traces (use agentforce-observe); performs a static safety review of .agent file content (use agentforce-generate Section 15)."
 allowed-tools: Bash Read Write Edit Glob Grep
 metadata:
+  relatedSkills:
+    - "agentforce-generate"
+    - "agentforce-observe"
   version: "0.8"
   cliTools:
     - tool: ["curl"]

package/skills/automation-flow-generate/SKILL.md

@@ -3,6 +3,7 @@ name: automation-flow-generate
 description: "Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled. Also trigger for flow-like requests such as \"when a record is created\", \"trigger daily at\", \"send an email when\", \"update the field when\", \"automate\", \"workflow\", or \"flow XML/metadata\". This is the only skill for Salesforce Flow generation."
 metadata:
   version: "1.0"
+  minApiVersion: "60.0"
 ---
 
 ## Goal

package/skills/commerce-b2b-open-code-components-integrate/SKILL.md

@@ -3,7 +3,15 @@ name: commerce-b2b-open-code-components-integrate
 description: "Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores. Use when users mention \"integrate open code components\", \"open source B2B commerce\", \"add open code components\", \"forcedotcom/b2b-commerce-open-source-components\", or want to add open source commerce components to their store. Copies all components and labels so they become available in Experience Builder."
 allowed-tools: Bash(git clone:*) Bash(cp:*) Read
 metadata:
+  cliTools:
+    - tool: ["git"]
+      semver: ">=2.0.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "commerce-b2b-store-create"
   version: "1.0"
+  minApiVersion: "56.0"
 ---
 
 ## When to Use This Skill

package/skills/commerce-b2b-open-code-components-replace/SKILL.md

@@ -3,6 +3,8 @@ name: commerce-b2b-open-code-components-replace
 description: "Replace OOTB (out-of-the-box) B2B Commerce components with open source equivalents in site metadata content.json files, or look up the equivalent open code `site:` component for OOTB definitions. Use when users mention \"replace OOTB components\", \"replace commerce components with open code\", \"swap OOTB for open source\", \"replace commerce_builder:\", \"replace OOTB in site\", \"replace component in site metadata\", \"replace component definition\", \"find open code equivalent\", \"equivalent open code component\", \"OOTB to open code mapping\", \"what is the site component for\", components \"in this view\" or \"for a given view\", or a specific list of component names — and want to update or only discover mappings in their store metadata."
 allowed-tools: Bash(grep:*) Bash(ls:*) Read Write
 metadata:
+  relatedSkills:
+    - "commerce-b2b-open-code-components-integrate"
   version: "1.0"
 ---
 

package/skills/commerce-b2b-store-create/SKILL.md

@@ -4,7 +4,10 @@ description: "Interactive workflow to create Commerce B2B Stores and retrieve st
 compatibility: "Requires Commerce licenses, Experience Cloud, Salesforce CLI"
 metadata:
   version: "1.0"
-  category: "commerce"
+  minApiVersion: "56.0"
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
 ---
 
 # Commerce B2B Storefront Creation

package/skills/data360-activate/SKILL.md

@@ -3,6 +3,18 @@ name: data360-activate
 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 data360-segment), data retrieval/search work (use data360-query), or STDM/session tracing (use agentforce-observe)."
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
+  cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "agentforce-observe"
+    - "data360-connect"
+    - "data360-orchestrate"
+    - "data360-prepare"
+    - "data360-query"
+    - "data360-segment"
   version: "1.0"
 ---
 

package/skills/data360-code-extension-generate/SKILL.md

@@ -6,15 +6,15 @@ metadata:
   relatedSkills:
     - "data360-schema-get"
   cliTools:
-    - tool: ["sf"]
-      semver: ">=2.0.0"
+    - tool: ["docker"]
+      semver: ">=20.0.0"
     - tool: ["pip"]
-      semver: ">=21.0.0"
+      semver: ">=23.0.0"
+    - tool: ["python"]
+      semver: ">=3.11.0"
     - tool: ["python3"]
       semver: ">=3.11.0"
-    - tool: ["docker"]
-      semver: ">=20.0.0"
-    - tool: ["git"]
+    - tool: ["sf"]
       semver: ">=2.0.0"
 ---
 

package/skills/data360-connect/SKILL.md

@@ -3,6 +3,17 @@ name: data360-connect
 description: "Salesforce Data Cloud Connect phase. Use this skill when the user manages Data Cloud connections, connectors, or sets up a new source system. TRIGGER when: user manages Data Cloud connections, connectors, connector metadata, tests a connection, browses source objects or databases, or sets up a new source system. DO NOT TRIGGER when: the task is about data streams or DLOs (use data360-prepare), DMOs or identity resolution (use data360-harmonize), retrieval/search (use data360-query), or STDM telemetry (use agentforce-observe)."
 compatibility: "Requires the sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
+  cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "agentforce-observe"
+    - "data360-harmonize"
+    - "data360-orchestrate"
+    - "data360-prepare"
+    - "data360-query"
   version: "1.0"
 ---
 

package/skills/data360-harmonize/SKILL.md

@@ -3,6 +3,17 @@ name: data360-harmonize
 description: "Salesforce Data Cloud Harmonize phase. Use this skill when the user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. TRIGGER when: user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. DO NOT TRIGGER when: the task is only about streams/DLOs (use data360-prepare), segments/insights (use data360-segment), retrieval/search (use data360-query), or STDM/session tracing (use agentforce-observe)."
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
+  cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "agentforce-observe"
+    - "data360-orchestrate"
+    - "data360-prepare"
+    - "data360-query"
+    - "data360-segment"
   version: "1.0"
 ---
 

package/skills/data360-orchestrate/SKILL.md

@@ -3,6 +3,36 @@ name: data360-orchestrate
 description: "Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use agentforce-observe), standard CRM SOQL (use platform-soql-query), or Apex implementation (use platform-apex-generate)."
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
+  cliTools:
+    - tool: ["curl"]
+      semver: ">=7.0.0"
+    - tool: ["git"]
+      semver: ">=2.0.0"
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["npx"]
+      semver: ">=9.0.0"
+    - tool: ["python3"]
+      semver: ">=3.10.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+    - tool: ["yarn"]
+      semver: ">=1.22.0"
+  relatedSkills:
+    - "agentforce-observe"
+    - "automation-flow-generate"
+    - "data360-activate"
+    - "data360-connect"
+    - "data360-harmonize"
+    - "data360-prepare"
+    - "data360-query"
+    - "data360-segment"
+    - "platform-apex-generate"
+    - "platform-custom-field-generate"
+    - "platform-custom-object-generate"
+    - "platform-data-manage"
+    - "platform-metadata-deploy"
+    - "platform-soql-query"
   version: "1.0"
 ---
 

package/skills/data360-prepare/SKILL.md

@@ -3,6 +3,20 @@ name: data360-prepare
 description: "Salesforce Data Cloud Prepare phase. Use this skill when the user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations. TRIGGER when: user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations, or asks about ingestion into Data Cloud. DO NOT TRIGGER when: the task is connection setup only (use data360-connect), DMOs and identity resolution (use data360-harmonize), or query/search work (use data360-query)."
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
+  cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["pip"]
+      semver: ">=21.0"
+    - tool: ["python3"]
+      semver: ">=3.10.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "data360-connect"
+    - "data360-harmonize"
+    - "data360-orchestrate"
+    - "data360-query"
   version: "1.0"
 ---
 

package/skills/data360-query/SKILL.md

@@ -3,6 +3,16 @@ name: data360-query
 description: "Salesforce Data Cloud Retrieve phase. Use this skill when the user runs Data Cloud SQL, async queries, vector search, search-index workflows, or metadata introspection for Data Cloud objects. TRIGGER when: user runs Data Cloud SQL, describe, async queries, vector search, search-index workflows, or metadata introspection for Data Cloud objects. DO NOT TRIGGER when: the task is standard CRM SOQL (use platform-soql-query), segment creation or calculated insight design (use data360-segment), or STDM/session tracing/parquet analysis (use agentforce-observe)."
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
+  cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "agentforce-observe"
+    - "data360-orchestrate"
+    - "data360-segment"
+    - "platform-soql-query"
   version: "1.0"
 ---
 

package/skills/data360-schema-get/SKILL.md

@@ -2,6 +2,13 @@
 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:
+  cliTools:
+    - tool: ["pip"]
+      semver: ">=23.0.0"
+    - tool: ["python3"]
+      semver: ">=3.10.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
   version: "1.0"
 ---
 

package/skills/data360-segment/SKILL.md

@@ -3,6 +3,17 @@ name: data360-segment
 description: "Salesforce Data Cloud Segment phase. Use this skill when the user creates or publishes segments, manages calculated insights, or troubleshoots audience SQL in Data Cloud. TRIGGER when: user creates or publishes segments, manages calculated insights, inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud. DO NOT TRIGGER when: the task is DMO/mapping/identity-resolution work (use data360-harmonize), activation work (use data360-activate), query/search-index work (use data360-query), or Standard Data Model (STDM)/session tracing (use agentforce-observe)."
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
+  cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "agentforce-observe"
+    - "data360-activate"
+    - "data360-harmonize"
+    - "data360-orchestrate"
+    - "data360-query"
   version: "1.0"
 ---
 

package/skills/design-systems-slds-validate/SKILL.md

@@ -2,6 +2,14 @@
 name: design-systems-slds-validate
 description: "Audit Lightning Web Components for SLDS compliance and produce a scored quality report. Runs the SLDS linter, analyzes CSS for theming hook usage and pairing, checks HTML for accessibility attributes, and scores findings across categories into an overall grade. Use when asked to \"score my component\", \"SLDS scorecard\", \"quality report\", \"audit SLDS compliance\", \"how good is my SLDS\", \"check component quality\", \"rate my component\", \"evaluate my component\", \"is this component ready to ship?\", \"look at my LWC for issues\", \"audit this before I submit\", \"review my component before code review\", or any time a user wants a quality assessment or production-readiness check on an LWC or SLDS component. Not for fixing violations (use design-systems-slds2-migrate) or building new components (use design-systems-slds-apply)."
 metadata:
+  cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["npx"]
+      semver: ">=7.0.0"
+  relatedSkills:
+    - "design-systems-slds-apply"
+    - "design-systems-slds2-migrate"
   version: "1.0"
 ---
 

package/skills/design-systems-slds2-migrate/SKILL.md

@@ -2,6 +2,9 @@
 name: design-systems-slds2-migrate
 description: "Migrate Lightning Web Components from SLDS 1 to SLDS 2 by running the SLDS linter and fixing violations. Use this skill whenever users mention SLDS 2, SLDS uplift, linter violations, LWC token migration, class overrides, hardcoded CSS values that need SLDS hook replacement, or styling hook selection. Covers all styling hook categories — color, spacing, sizing, typography, borders, radius, and shadows. Also use when users mention no-hardcoded-values, no-slds-class-overrides, lwc-to-slds-hooks, no-deprecated-tokens-slds1, or ask about SLDS component migration — even if they don't explicitly say \"uplift\" or \"migration\"."
 metadata:
+  cliTools:
+    - tool: ["npx"]
+      semver: ">=7.0.0"
   version: "1.0"
 ---
 

package/skills/dx-app-analytics-query/SKILL.md

@@ -2,6 +2,11 @@
 name: dx-app-analytics-query
 description: "ISV App Analytics metadata types — AppAnalyticsQueryRequest and AppAnalyticsSettings. Use this skill when the user asks about retrieving managed package usage data, configuring App Analytics simulation mode, querying subscriber snapshots, or understanding the AppAnalyticsQueryRequest lifecycle (New → Pending → Complete → Expired). TRIGGER when: user mentions App Analytics, AppAnalyticsQueryRequest, AppAnalyticsSettings, package usage data, subscriber analytics, ISV analytics, or simulation mode for app analytics. DO NOT TRIGGER when: the task is about standard Salesforce reports/dashboards (use reporting skills), custom SOQL on Account/Contact (use platform-soql-query), or Data Cloud query/search (use data360-query)."
 metadata:
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "platform-soql-query"
   version: "1.0"
   minApiVersion: "56.0"
 ---

package/skills/dx-code-analyzer-configure/SKILL.md

@@ -7,18 +7,18 @@ metadata:
     - "dx-code-analyzer-run"
     - "dx-code-analyzer-custom-rule-create"
   cliTools:
-    - tool: ["sf"]
-      semver: ">=2.0.0"
+    - tool: ["curl"]
+      semver: ">=7.0.0"
     - tool: ["java"]
       semver: ">=11.0.0"
     - tool: ["node"]
       semver: ">=18.0.0"
+    - tool: ["npm"]
+      semver: ">=9.0.0"
     - tool: ["python3"]
       semver: ">=3.10.0"
-    - tool: ["git"]
+    - tool: ["sf"]
       semver: ">=2.0.0"
-    - tool: ["npm"]
-      semver: ">=9.0.0"
 ---
 
 # Configuring Code Analyzer Skill

package/skills/dx-code-analyzer-custom-rule-create/SKILL.md

@@ -7,12 +7,14 @@ metadata:
     - "dx-code-analyzer-run"
     - "dx-code-analyzer-configure"
   cliTools:
-    - tool: ["sf"]
+    - tool: ["git"]
       semver: ">=2.0.0"
     - tool: ["node"]
       semver: ">=18.0.0"
     - tool: ["npm"]
       semver: ">=9.0.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
 ---
 
 # dx-code-analyzer-custom-rule-create: Custom Code Analyzer Rule Authoring

package/skills/dx-code-analyzer-run/SKILL.md

@@ -7,11 +7,19 @@ metadata:
     - "dx-code-analyzer-configure"
     - "dx-code-analyzer-custom-rule-create"
   cliTools:
-    - tool: ["sf"]
+    - tool: ["git"]
       semver: ">=2.0.0"
+    - tool: ["java"]
+      semver: ">=11.0.0"
+    - tool: ["jq"]
+      semver: ">=1.6.0"
     - tool: ["node"]
       semver: ">=18.0.0"
-    - tool: ["git"]
+    - tool: ["npm"]
+      semver: ">=9.0.0"
+    - tool: ["python3"]
+      semver: ">=3.9.0"
+    - tool: ["sf"]
       semver: ">=2.0.0"
 ---
 

package/skills/dx-devops-test-failures-analyze/SKILL.md

@@ -2,6 +2,14 @@
 name: dx-devops-test-failures-analyze
 description: "Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement suggestions (test-code vs production-code) — then optionally creates a tracked fix WorkItem on explicit request. Analysis is pure reasoning; work-item creation is a confirmation-gated write. Use this skill to explain failures or improvement suggestions, translate Code Analyzer violations, or track a fix as a work item. TRIGGER when: a run failed and the user wants root cause; a quality gate failure needs explaining; violations need translating; the user shares a failure payload and asks how to address it; wants to strengthen tests; or wants to create a fix work item, log a remediation, or assign a failure. DO NOT TRIGGER when: the user wants fix code written (use platform-apex-generate) or new test classes authored (use platform-apex-test-generate)."
 metadata:
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.67.0"
+  relatedSkills:
+    - "dx-devops-test-suite-assignments-configure"
+    - "dx-devops-test-suite-run"
+    - "platform-apex-generate"
+    - "platform-apex-test-generate"
   version: "1.0"
   minApiVersion: "67.0"
 ---

package/skills/dx-devops-test-pipeline-configure/SKILL.md

@@ -2,6 +2,13 @@
 name: dx-devops-test-pipeline-configure
 description: "Configures DevOps Center pipeline testing infrastructure: enables a test provider so its suites become available, re-syncs a configured provider to pull in new suites, or creates a quality gate with rules on a stage. Routes by intent across three modes after running shared prerequisite checks and an explicit confirmation gate. Use this skill when a user wants to set up, configure, enable, sync, or refresh a test provider, or set/configure a quality gate or coverage threshold on a DevOps Center pipeline stage. TRIGGER when: the user wants to configure/enable/add/set up a test provider, re-sync or refresh a provider's suite list, pull in new suites, or set/configure a quality gate, coverage threshold, or testing benchmark on a stage. DO NOT TRIGGER when: assigning existing suites to a stage (use dx-devops-test-suite-assignments-configure), running or retriggering a suite (use dx-devops-test-suite-run), or non-DevOps-Center work."
 metadata:
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.67.0"
+  relatedSkills:
+    - "dx-devops-test-failures-analyze"
+    - "dx-devops-test-suite-assignments-configure"
+    - "dx-devops-test-suite-run"
   version: "1.0"
   minApiVersion: "67.0"
 ---

package/skills/dx-devops-test-suite-assignments-configure/SKILL.md

@@ -2,6 +2,15 @@
 name: dx-devops-test-suite-assignments-configure
 description: "Recommends and manages DevOps Center test suite assignments for pipeline stages. Mode A analyzes a commit diff against assigned suite metadata to recommend relevant existing suites and flag coverage gaps (pure reasoning). Modes B-D assign a single suite, bulk-map multiple suites with a mandatory impact preview, or add/remove test classes with governance rules, via the testSuiteStages Connect API. Use this skill to recommend suites for a commit, assign or map suites to stages, or add/remove tests in a suite. TRIGGER when: the user asks which suites to run for a commit/diff or what covers their changes; a suite is unlinked and the user wants it assigned; the user wants to configure suite-to-stage mappings, assign multiple suites, or add/remove/sync tests in a suite. DO NOT TRIGGER when: configuring or syncing a test provider (use dx-devops-test-pipeline-configure), running suites (use dx-devops-test-suite-run), or authoring/running tests directly (use platform-apex-test-generate or platform-apex-test-run)."
 metadata:
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.67.0"
+  relatedSkills:
+    - "dx-devops-test-failures-analyze"
+    - "dx-devops-test-pipeline-configure"
+    - "dx-devops-test-suite-run"
+    - "platform-apex-test-generate"
+    - "platform-apex-test-run"
   version: "1.0"
   minApiVersion: "67.0"
 ---

package/skills/dx-devops-test-suite-run/SKILL.md

@@ -2,6 +2,14 @@
 name: dx-devops-test-suite-run
 description: "Runs DevOps Center test suites on a pipeline stage (Pre-Promote, Post-Promote, or Review event) end to end: triggers async execution via the Connect API after an explicit confirmation gate, then polls by runId at provider-specific intervals until it completes, fails, or times out, and hands results to failure analysis. Also retriggers a quality gate after fixes, but only once coverage meets the threshold. Use this skill when a user wants to run, kick off, or launch test suites on a stage, re-run a quality gate, or watch an in-progress run to completion. TRIGGER when: the user wants to run/launch suites on a stage, execute tests before or after promotion, re-run a quality gate after fixing failures, unblock a blocked promotion after adding tests, or poll/watch an in-progress run. DO NOT TRIGGER when: running sf apex run test directly (use platform-apex-test-run), or configuring a NEW gate or threshold (use dx-devops-test-pipeline-configure)."
 metadata:
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.67.0"
+  relatedSkills:
+    - "dx-devops-test-failures-analyze"
+    - "dx-devops-test-pipeline-configure"
+    - "dx-devops-test-suite-assignments-configure"
+    - "platform-apex-test-run"
   version: "1.0"
   minApiVersion: "67.0"
 ---

package/skills/dx-org-switch/SKILL.md

@@ -3,6 +3,9 @@ name: dx-org-switch
 description: "Switches the active Salesforce org (default target-org) using the Salesforce CLI. Use whenever someone wants to change which org CLI commands run against — whether they say \"switch org\", \"change default org\", \"set my org to\", \"use alias\", \"point to\", or describe wanting to work against a specific org, scratch org, sandbox, or production."
 compatibility: Salesforce CLI (sf) v2+
 metadata:
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
   version: "1.0"
 ---
 

package/skills/experience-lwc-generate/SKILL.md

@@ -2,6 +2,24 @@
 name: experience-lwc-generate
 description: "Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use platform-apex-generate), Aura components, or Visualforce."
 metadata:
+  cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["npm"]
+      semver: ">=9.0.0"
+    - tool: ["npx"]
+      semver: ">=9.0.0"
+    - tool: ["python3"]
+      semver: ">=3.9.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "agentforce-generate"
+    - "automation-flow-generate"
+    - "integration-connectivity-generate"
+    - "platform-apex-generate"
+    - "platform-apex-test-run"
+    - "platform-metadata-deploy"
   version: "1.1"
 ---
 

package/skills/experience-lwr-site-generate/SKILL.md

@@ -3,7 +3,7 @@ name: experience-lwr-site-generate
 description: "Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata. Always trigger when the tasks involve LWR sites configurations, e.g. creating/modifying pages/routes/views/theme layouts/branding sets, previewing sites, or creating/modifying guest sharing rule (metadata type sharingGuestRules)/guest user access/sharing records to guest users, or when user provides a guest user ID (15 or 18 characters starting with 005). NEVER trigger for React or any other ui bundle framework. LWR sites ONLY."
 metadata:
   version: "1.0"
-  minApiVersion: "51.0"
+  minApiVersion: "56.0"
   cliTools:
     - tool: ["node"]
       semver: ">=18.0.0"

package/skills/experience-ui-bundle-agentforce-client-generate/SKILL.md

@@ -3,8 +3,11 @@ name: experience-ui-bundle-agentforce-client-generate
 description: "Use this skill when the user asks to add, embed, integrate, configure, style, or remove an agent, chatbot, chat widget, conversation client, or AI assistant in a UI Bundle project. TRIGGER when: project contains a uiBundles/*/src/ directory and the task involves adding or modifying a chat widget, chatbot, or conversational AI; files under uiBundles/*/src/ import AgentforceConversationClient; user asks to add any chat or agent functionality to a page. DO NOT TRIGGER when: user wants to create a custom agent, chatbot, or chat widget component from scratch; the project has no uiBundles directory."
 metadata:
   version: "1.1"
-  package: "@salesforce/ui-bundle-template-feature-react-agentforce-conversation-client"
-  sdk-package: "@salesforce/agentforce-conversation-client"
+  cliTools:
+    - tool: ["npm"]
+      semver: ">=9.0.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
 ---
 
 # Managing Agentforce Conversation Client

package/skills/experience-ui-bundle-custom-app-generate/SKILL.md

@@ -3,7 +3,7 @@ name: experience-ui-bundle-custom-app-generate
 description: "MUST activate when the project contains a uiBundles/*/src/ directory and the task involves creating or configuring a Custom Application for hosting a UI bundle in Lightning Experience. Use this skill when creating a CustomApplication metadata record to surface the UI bundle in the App Launcher. Activate when files matching applications/*.app-meta.xml exist and need modification, or when the user wants to expose their app via the Lightning App Launcher without a Digital Experience Site. Do NOT use platform-custom-application-generate for this — UI bundle apps do not use tabs, action overrides, or flexipages."
 metadata:
   version: "1.0"
-  minApiVersion: "51.0"
+  minApiVersion: "65.0"
   relatedSkills:
     - "platform-custom-application-generate"
   cliTools:

package/skills/experience-ui-bundle-file-upload-generate/SKILL.md

@@ -3,6 +3,11 @@ name: experience-ui-bundle-file-upload-generate
 description: "MUST activate when the project contains a uiBundles/*/src/ directory and the task involves uploading, attaching, or dropping files. Use this skill when adding file upload functionality to a UI bundle app. Provides progress tracking and Salesforce ContentVersion integration. This feature provides programmatic APIs ONLY — build custom UI using the upload() API. ALWAYS use this instead of building file upload from scratch with FormData or XHR."
 metadata:
   version: "1.0"
+  relatedSkills:
+    - "experience-ui-bundle-salesforce-data-access"
+  cliTools:
+    - tool: ["npm"]
+      semver: ">=7.0.0"
 ---
 
 # File Upload API (workflow)

package/skills/experience-ui-bundle-metadata-generate/SKILL.md

@@ -3,7 +3,7 @@ name: experience-ui-bundle-metadata-generate
 description: "Use this skill when adding a front-end React UI bundle to an existing project or configuring UI bundle metadata and config files. TRIGGER when: adding or scaffolding a new UI bundle inside a project that already exists; running sf template generate ui-bundle; editing ui-bundle.json routing, headers, or output directory; working with *.uibundle-meta.xml files; or registering CSP Trusted Sites, resolving blocked images or fonts or external API calls, or editing cspTrustedSites/*.cspTrustedSite-meta.xml files. DO NOT TRIGGER when: creating a brand-new Salesforce project from scratch, where the whole SFDX starter project (UI bundle plus Experience Site metadata and toolchain) is generated together (use experience-ui-bundle-project-generate)."
 metadata:
   version: "1.2"
-  minApiVersion: "51.0"
+  minApiVersion: "67.0"
   relatedSkills:
     - "experience-ui-bundle-custom-app-generate"
     - "experience-ui-bundle-frontend-generate"

package/skills/experience-ui-bundle-project-generate/SKILL.md

@@ -10,12 +10,12 @@ metadata:
     - "experience-ui-bundle-salesforce-data-access"
     - "experience-ui-bundle-deploy"
   cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["npm"]
+      semver: ">=9.0.0"
     - tool: ["sf"]
       semver: ">=2.0.0"
-    - tool: ["npm"]
-      semver: ">=7.0.0"
-    - tool: ["node"]
-      semver: ">=16.7.0"
 ---
 
 # Using a UI Bundle Template

package/skills/experience-ui-bundle-salesforce-data-access/SKILL.md

@@ -2,6 +2,17 @@
 name: experience-ui-bundle-salesforce-data-access
 description: "MUST activate when a uiBundles/*/src/ project does ANY Salesforce record operation — reading, creating, updating, deleting, or caching/refreshing query results. Triggers: code importing @salesforce/platform-sdk, calls to sdk.graphql.query / sdk.graphql.mutate / sdk.fetch, *.graphql files, stale data needing a force-refresh, or wiring up a UI bundle's data layer to read, write, or refresh Salesforce records. The default for new read/write work is the Read/Write workflow with the current @salesforce/platform-sdk API; only follow the migration path when EXISTING code already uses the old @salesforce/sdk-data callable form. Not for building app shell/UI, styling, file upload, or auth/search scaffolding — use the other ui-bundle-* skills. DO NOT TRIGGER when: OAuth setup, schema changes, Bulk/Tooling/Metadata API, or declarative automation."
 metadata:
+  cliTools:
+    - tool: ["node"]
+      semver: ">=18.0.0"
+    - tool: ["npm"]
+      semver: ">=9.0.0"
+    - tool: ["npx"]
+      semver: ">=9.0.0"
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+  relatedSkills:
+    - "platform-metadata-deploy"
   version: "2.1"
 ---