@salesforce/afv-skills 1.35.0 → 1.37.0

package/package.json

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

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

@@ -6,6 +6,8 @@ metadata:
     - tool: ["sf"]
       semver: ">=2.0.0"
   relatedSkills:
+    - "data360-query"
+    - "platform-metadata-deploy"
     - "platform-soql-query"
   version: "1.0"
   minApiVersion: "56.0"

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

@@ -11,8 +11,7 @@ metadata:
       semver: ">=2.0.0"
   mcpTools:
     metadata-experts:
-      tools:
-        - "execute_metadata_action"
+      tools: ["execute_metadata_action"]
       semver: ">=1.0.0"
 ---
 

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

@@ -3,6 +3,9 @@ name: experience-ui-bundle-site-generate
 description: "MUST activate when the project contains a uiBundles/*/src/ directory and the task involves creating or configuring site infrastructure. Use this skill when creating or configuring a Salesforce Digital Experience Site for hosting a UI bundle. Activate when files matching digitalExperiences/, networks/, customSite/, or DigitalExperienceBundle exist and need modification, or when the user wants to publish, host, or configure guest access for their app."
 metadata:
   version: "1.0"
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
 ---
 
 # Digital Experience Site for React UI Bundles

package/skills/mobile-apps-create/SKILL.md

@@ -2,12 +2,10 @@
 name: mobile-apps-create
 description: "The entry point for building any Salesforce native mobile app on iOS or Android. TRIGGER when the user says: \"build a Salesforce iOS app\", \"add Salesforce login to my Android app\", \"set up Mobile SDK\", \"add MobileSync / SmartStore offline storage\", \"embed an Agentforce agent in my mobile app\", \"add Agentforce chat to iOS/Android\", or otherwise asks to create, extend, or integrate a Salesforce mobile experience in Swift or Kotlin (MSDK, Agentforce SDK, or both). SKIP when the user is building a non-Salesforce mobile app, using React Native / Flutter / Ionic without Salesforce integration, asking about generic mobile UI design, or working on a Salesforce-adjacent web/desktop surface (LWC, Experience Cloud, Mobile Publisher branding-only)."
 metadata:
+  version: "1.0"
   cliTools:
     - tool: ["npx"]
       semver: ">=9.0.0"
-  relatedSkills:
-    - "mobile-platform-native-capabilities-integrate"
-  version: "1.0"
 ---
 
 # Salesforce Mobile

package/skills/platform-custom-field-generate/SKILL.md

@@ -4,7 +4,13 @@ description: "Use this skill when users need to create, generate, or validate Sa
 metadata:
   version: "1.0"
   minApiVersion: "60.0"
-  relatedSkills: ["platform-value-set-generate", "platform-validation-rule-generate"]
+  relatedSkills:
+    - "platform-validation-rule-generate"
+    - "platform-value-set-generate"
+  mcpTools:
+    metadata-grounding:
+      tools: ["search_metadata"]
+      semver: ">=1.0.0"
 ---
 
 # Salesforce Custom Field Generator and Validator

package/skills/platform-lightning-app-coordinate/SKILL.md

@@ -15,12 +15,12 @@ metadata:
     - "platform-permission-set-generate"
     - "platform-validation-rule-generate"
   mcpTools:
-    salesforce-api-context:
-      tools: ["get_metadata_type_sections", "get_metadata_type_context", "get_metadata_type_fields", "get_metadata_type_fields_properties", "search_metadata_types"]
-      semver: ">=1.0.0"
     metadata-experts:
       tools: ["execute_metadata_action"]
       semver: ">=1.0.0"
+    salesforce-api-context:
+      tools: ["get_metadata_type_context", "get_metadata_type_fields", "get_metadata_type_fields_properties", "get_metadata_type_sections", "search_metadata_types"]
+      semver: ">=1.0.0"
 ---
 
 # Generating Lightning App

package/skills/platform-report-generate/SKILL.md

@@ -8,7 +8,7 @@ metadata:
     - "platform-custom-report-type-generate"
   mcpTools:
     salesforce-api-context:
-      tools: ["get_metadata_type_sections", "get_metadata_type_context", "get_metadata_type_shape"]
+      tools: ["get_metadata_type_context", "get_metadata_type_sections", "get_metadata_type_shape"]
       semver: ">=1.0.0"
 ---
 

package/skills/platform-value-set-generate/SKILL.md

@@ -7,6 +7,10 @@ metadata:
   cliTools:
     - tool: ["sf"]
       semver: ">=2.0.0"
+  mcpTools:
+    metadata-grounding:
+      tools: ["query_metadata", "search_metadata"]
+      semver: ">=1.0.0"
 ---
 
 ## Overview
@@ -198,7 +202,7 @@ When customizing a **StandardValueSet** (or extending a shared GlobalValueSet),
 
 For well-known standard picklists you already know the canonical values (e.g. `Industry`, `LeadSource`, `OpportunityStage`). When you are unsure a named value exists, you can confirm it against the live org — but treat lookup as a *confirmation* step, not a required first call:
 
-- **Grounding MCP** (if available) exposes `search_metadata` and `query-metadata` to look up live metadata. Use them only to confirm a named value's exact `<fullName>`/`<label>` — not to pull the full list to reproduce.
+- **Grounding MCP** (if available) exposes `search_metadata` and `query_metadata` to look up live metadata. Use them only to confirm a named value's exact `<fullName>`/`<label>` — not to pull the full list to reproduce.
 - **CLI fallback** — query the Tooling API directly:
 
 ```bash
@@ -291,7 +295,7 @@ Before generating value-set XML, verify:
 - [ ] When referencing from a field, is `<valueSetName>` the **bare** developer name with NO `__gvs` suffix?
 
 ### StandardValueSet Checks CRITICAL
-- [ ] Are you emitting modifications ONLY to values you know exist (confirmed from known standard catalogs, or via grounding `search_metadata`/`query-metadata` / Tooling API if unsure) — never invented values?
+- [ ] Are you emitting modifications ONLY to values you know exist (confirmed from known standard catalogs, or via grounding `search_metadata`/`query_metadata` / Tooling API if unsure) — never invented values?
 - [ ] Is the root `<StandardValueSet>` with the correct namespace?
 - [ ] Does the root use `<fullName>` set to the fixed catalog name (NOT `masterLabel`)?
 - [ ] Are values `<standardValue>` entries (NOT `customValue`)?