@salesforce/afv-skills 1.55.0 → 1.57.0

package/skills/integration-connectivity-connected-app-configure/SKILL.md

@@ -38,8 +38,8 @@ Use this skill when the user needs **OAuth app configuration** in Salesforce: Co
 
 **Out of scope — delegate elsewhere:**
 - Configuring Named Credentials or runtime callouts → [integration-connectivity-generate](../integration-connectivity-generate/SKILL.md)
-- Deploying metadata to orgs → [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md)
-- Writing Apex token-handling code → [platform-apex-generate](../platform-apex-generate/SKILL.md)
+- Deploying metadata to orgs → the `platform-metadata-deploy` skill
+- Writing Apex token-handling code → the `platform-apex-generate` skill
 
 ---
 
@@ -206,8 +206,8 @@ Score: <x>/120
 | Need | Delegate to | Reason |
 |---|---|---|
 | Named Credential / callout runtime config | [integration-connectivity-generate](../integration-connectivity-generate/SKILL.md) | runtime integration setup |
-| Deploy app metadata | [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md) | org validation and deployment |
-| Apex token or refresh handling | [platform-apex-generate](../platform-apex-generate/SKILL.md) | implementation logic |
+| Deploy app metadata | `platform-metadata-deploy` skill | org validation and deployment |
+| Apex token or refresh handling | `platform-apex-generate` skill | implementation logic |
 
 ---
 
@@ -237,4 +237,4 @@ Score: <x>/120
 | `references/security-checklist.md` | Step 4 — full 120-point security scoring checklist |
 | `references/testing-validation-guide.md` | Step 5 — pre-deployment validation and testing guide |
 | `references/migration-guide.md` | When migrating from Connected App to ECA patterns |
-| `references/example-usage.md` | Full end-to-end examples for common OAuth scenarios |
+| `references/example-usage.md` | Full end-to-end examples for common OAuth scenarios |

package/skills/integration-connectivity-generate/SKILL.md

@@ -39,9 +39,9 @@ Use `integration-connectivity-generate` when the work involves:
 
 Delegate elsewhere when the user is:
 - configuring the OAuth app itself → [integration-connectivity-connected-app-configure](../integration-connectivity-connected-app-configure/SKILL.md)
-- writing Apex-only business logic → [platform-apex-generate](../platform-apex-generate/SKILL.md)
-- deploying metadata → [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md)
-- importing/exporting data → [platform-data-manage](../platform-data-manage/SKILL.md)
+- writing Apex-only business logic → the `platform-apex-generate` skill
+- deploying metadata → the `platform-metadata-deploy` skill
+- importing/exporting data → the `platform-data-manage` skill
 
 ---
 
@@ -93,9 +93,9 @@ Check:
 
 ### 5. Hand off deployment or implementation details
 Use:
-- [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md) for deployment
-- [platform-apex-generate](../platform-apex-generate/SKILL.md) for deeper service / retry code
-- [automation-flow-generate](../automation-flow-generate/SKILL.md) for declarative HTTP callout orchestration
+- the `platform-metadata-deploy` skill for deployment
+- the `platform-apex-generate` skill for deeper service / retry code
+- the `automation-flow-generate` skill for declarative HTTP callout orchestration
 
 ---
 
@@ -142,10 +142,10 @@ Next step: <deploy, register, test, or implement>
 | Need | Delegate to | Reason |
 |---|---|---|
 | OAuth app setup | [integration-connectivity-connected-app-configure](../integration-connectivity-connected-app-configure/SKILL.md) | consumer key / cert / app config |
-| advanced callout service code | [platform-apex-generate](../platform-apex-generate/SKILL.md) | Apex implementation |
-| declarative HTTP callout / Flow wrapper | [automation-flow-generate](../automation-flow-generate/SKILL.md) | Flow orchestration |
-| deploy integration metadata | [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md) | validation and rollout |
-| use integration from Agentforce | [agentforce-generate](../agentforce-generate/SKILL.md) | agent action composition |
+| advanced callout service code | `platform-apex-generate` skill | Apex implementation |
+| declarative HTTP callout / Flow wrapper | `automation-flow-generate` skill | Flow orchestration |
+| deploy integration metadata | `platform-metadata-deploy` skill | validation and rollout |
+| use integration from Agentforce | `agentforce-generate` skill | agent action composition |
 
 ---
 

package/skills/integration-connectivity-generate/scripts/configure-named-credential.sh

@@ -190,14 +190,14 @@ try {
     // Create the credential (first-time setup)
     ConnectApi.NamedCredentials.createCredential(newCredentials);
     System.debug('✓ External Credential configured successfully!');
-    System.debug('Principal: $PRINCIPAL_NAME');
+    System.debug('Principal: $PRINCIPAL_NAME_ESCAPED');
 } catch (Exception e) {
     // If already exists, try patching instead
     if (e.getMessage().contains('already exists')) {
         try {
             ConnectApi.NamedCredentials.patchCredential(newCredentials);
             System.debug('✓ External Credential updated successfully!');
-            System.debug('Principal: $PRINCIPAL_NAME');
+            System.debug('Principal: $PRINCIPAL_NAME_ESCAPED');
         } catch (Exception e2) {
             System.debug('✗ Error updating credential: ' + e2.getMessage());
             throw e2;

package/skills/life-sciences-fieldsalesrep-coordinate/SKILL.md

@@ -236,7 +236,7 @@ Before presenting the workflow, establish which org to use. Do this **every time
     - **Stage 2**: objects/profiles/config records deployed, `<N>` layouts + `<N>` flexipages deployed, 28 trigger handlers activated.
     - **Stage 3**: Territory Model `<model name>` (Active); Level-3 Territory `<territory name>`.
     - **Stage 4**: User `<firstName> <lastName>` (`<username>`); Profile `LSC Custom Profile`; permission sets Life Sciences Core, Life Sciences Field Sales Representative, Health Cloud Starter, Life Sciences Key Account Management; Territory `<territory name>`; admin also assigned to the territory.
-    - **Stage 5**: Account + Healthcare Provider created; Visit `<subject>` (Territory `<territory name>`); product detailing/discussion records; mobile metadata cache generated (Connect API).
+    - **Stage 5**: Account + Healthcare Provider created; Visit `<name>` (Territory `<territory name>`); product detailing/discussion records; mobile metadata cache generated (Connect API).
 
     Close with: "The org is ready for Life Sciences Cloud field sales workflows."
 

package/skills/life-sciences-fieldsalesrep-coordinate/references/orchestration-flow.md

@@ -100,7 +100,7 @@ Expected: at least 2 records (new user + admin).
 ### After Stage 5 — Visit Creation
 
 ```bash
-sf data query --query "SELECT Id, Subject, TerritoryId FROM Visit ORDER BY CreatedDate DESC LIMIT 1" --target-org <org> --json
+sf data query --query "SELECT Id, Name, TerritoryId FROM Visit ORDER BY CreatedDate DESC LIMIT 1" --target-org <org> --json
 ```
 
 Expected: at least 1 Visit record (created against the level-3 territory).

package/skills/life-sciences-kam-coordinate/references/stage-5-data-and-plan-templates-overview.md

@@ -84,7 +84,20 @@ All three must return a record, and the `ProductTerritoryAvailability.TerritoryI
 
 Creates the goal definitions, the goal-product link, and the action-plan template (with its items) that back the KAM account plan, then publishes it (by setting its version to `Final`) and assigns it. Run entirely as the **admin** (`--target-org <admin>`), immediately after Part A — Part B links to the Part A `LifeSciMarketableProduct`.
 
-Only the record **names** are confirmed with the admin. All other fields are auto-derived from this reference and shown for confirmation.
+Only the record **names** are the user-supplied values; all other fields are auto-derived from this reference. The names must be confirmed with the admin **before any record is created**.
+
+> **STOP-GATE (confirm names — MANDATORY, do this FIRST).** Before running any `sf data create record` in Part B, **present the full set of proposed names below and WAIT for the admin to confirm or edit them.** Do **not** create any record until the admin explicitly responds. Present them as an editable list:
+>
+> | # | Record | Proposed name |
+> |---|--------|----------------|
+> | 1 | GoalDefinition (Strategic) | `Immunexis: Secure Q3 Formulary Position` |
+> | 2 | GoalDefinition (Individual) | `Immunexis: Prepare Pharmacy & Therapeutics (P&T) Strategy` |
+> | 3 | ActionPlanTemplate | `Immunexis: Formulary Submission & Review Prep` |
+> | 4 | Template item 1 | `Identify key P&T committee members and influencers` |
+> | 5 | Template item 2 | `Gather HEOR data supporting our value proposition` |
+> | 6 | Template item 3 | `Compile the competitive landscape and formulary access gaps` |
+>
+> Ask: *"These are the goal, action-plan-template, and item names I'll create. Confirm as-is, or tell me which to change."* Apply any edits the admin gives, then use the confirmed names verbatim in every step below. **Only the names are editable** — `ActionPlanType`, `TargetEntityType`, goal types, categories, and other fields are auto-derived and are not changed here. Never skip this gate or assume the defaults are accepted.
 
 ## Step 1 — Two GoalDefinition records
 

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

@@ -54,7 +54,7 @@ If the user wants both platforms, route to each child skill separately — they
 When an app needs both:
 
 1. Route to the Mobile SDK platform skill first to scaffold and authenticate.
-2. Route to the Agentforce SDK platform skill to layer the agent surface.
+2. Then you **MUST** load the Agentforce SDK platform skill (`integrate-agentforce-ios` or `integrate-agentforce-android`) to layer the agent surface. Do not hand-write the Agentforce integration — the SDK's dependencies, products, and APIs are not guessable and hand-rolled code will not compile.
 3. Treat each child skill's instructions as authoritative for its SDK; do not merge their steps. Each SDK owns its own auth setup, dependency installation order, and initialization sequence — interleaving them produces conflicting config and broken init order.
 
 This sequencing is the only multi-skill logic this skill owns. Everything else lives inside the child skills.

package/skills/{platform-agentsetup-categories-fetch → platform-agenticsetup-categories-get}/SKILL.md

@@ -1,19 +1,19 @@
 ---
-name: platform-agentsetup-categories-fetch
-description: "Fetch agentic setup prompt categories from a connected Salesforce org using the Connect API. Use this skill to call GET /agenticsetup/categories and return the list of prompt categories, optionally with their nested prompts. TRIGGER when: user asks to get, fetch, list, or show agentic setup categories, prompt categories, setup copilot categories, prompt library categories, available setup prompts, Agentforce prompt library, or copilot prompts. DO NOT TRIGGER when: user wants to create new categories, work with non-categories endpoints, or generate OpenAPI specs."
+name: platform-agenticsetup-categories-get
+description: "Get agentic setup prompt categories from a connected Salesforce org using the Connect API via sf api request rest. Use this skill to call GET /services/data/vXX.0/agenticsetup/categories and return the list of prompt categories, optionally with their nested prompts using fetchPrompts=true. TRIGGER when: user asks to get, fetch, retrieve, list, or show agentic setup categories, prompt categories, setup copilot categories, prompt library categories, available setup prompts, Agentforce prompt library, copilot prompts, or calls the agenticsetup categories Connect REST API. DO NOT TRIGGER when: user wants to create new categories, work with non-categories endpoints, or generate OpenAPI specs."
 allowed-tools: Bash Read
 metadata:
+  version: "1.1"
+  domains: ["Platform", "Agentforce"]
+  minApiVersion: "67.0"
   cliTools:
     - tool: ["sf"]
       semver: ">=2.0.0"
-  version: "1.0"
-  domains: ["Platform", "Agentforce"]
-  minApiVersion: "67.0"
 ---
 
-# platform-agentsetup-categories-fetch
+# platform-agenticsetup-categories-get
 
-Fetch prompt categories from the Agentic Setup Categories Connect API on a connected Salesforce org.
+Get prompt categories from the Agentic Setup Categories Connect API on a connected Salesforce org.
 
 ## Scope
 

package/skills/platform-apex-test-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-apex-test-generate
-description: "Generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking strategies, assertion best practices, and disciplined test-fix loops. Use this skill when creating new Apex test classes, improving test coverage, debugging and fixing failing Apex tests, running test execution and coverage analysis, or implementing testing patterns for triggers, services, controllers, batch jobs, queueables, and integrations. Triggers on *Test.cls, *_Test.cls files, sf apex run test workflows, coverage reports, test-fix loops. Do NOT trigger for production Apex code (use platform-apex-generate) or Jest/LWC tests."
+description: "Use to generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking, assertions, and disciplined test-fix loops. Use when creating Apex test classes (for triggers, services, controllers, batch jobs, queueables, and callouts), improving coverage, debugging or fixing failing Apex tests, or running test/coverage analysis. Triggers on *Test.cls files, sf apex run test, coverage reports. Do NOT trigger for production Apex (use platform-apex-generate) or Jest/LWC tests."
 metadata:
   version: "1.1"
   domains: ["Platform"]

package/skills/platform-apex-test-run/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-apex-test-run
-description: "Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user needs to run Apex tests, check code coverage, fix failing tests, or work with *Test.cls / *_Test.cls files. TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when: writing Apex production code (use platform-apex-generate), Agentforce agent testing (use agentforce-test), or Jest/LWC tests (use experience-lwc-generate)."
+description: "Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when writing Apex production code (use platform-apex-generate), Agentforce agent testing (use agentforce-test), or Jest/LWC tests (use experience-lwc-generate)."
 metadata:
   version: "1.2"
   domains: ["Platform"]

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

@@ -1,6 +1,6 @@
 ---
 name: platform-custom-field-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping/limiting picklist values for a specific record type. Also use when users encounter field deployment errors, especially around Roll-up Summary format, Master-Detail constraints, formula issues, or a record type that won't deploy without a business process. Use this skill for custom field metadata work, field generation, and field troubleshooting. DO NOT TRIGGER for creating or customizing the value set itself — defining a new GlobalValueSet, or modifying a StandardValueSet catalog like Industry or Lead Source — use platform-value-set-generate instead; this skill covers the field that references a value set, not the value set definition."
+description: "Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values per record type; also field deployment errors, including a record type that won't deploy without a business process. DO NOT TRIGGER for creating/customizing the value set itself — a new GlobalValueSet or a StandardValueSet catalog like Industry — use platform-value-set-generate; this skill covers the field that references a value set, not the value set definition."
 metadata:
   version: "1.0"
   domains: ["Platform"]

package/skills/platform-custom-lightning-type-generate/SKILL.md

@@ -178,4 +178,4 @@ When you need the full list of supported primitive `lightning:type` identifiers,
 - [ ] Layout configurations use `lightning/propertyLayout` with ONLY the `property` attribute (no `label`, `title`, or other attributes)
 - [ ] All attribute mappings (`{!$attrs.propertyName}`) reference properties that exist in the type schema
 - [ ] Custom LWC components have correct targets in `-meta.xml`: `lightning__AgentforceInput` for editors, `lightning__AgentforceOutput` for renderers
-- [ ] Root schema does NOT include `"$schema"` field
+- [ ] Root schema does NOT include `"$schema"` field

package/skills/platform-custom-metadata-type-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-custom-metadata-type-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Custom Metadata Type metadata — the __mdt object, its fields, and its deployable records. Trigger when users mention custom metadata types, CMDT, __mdt objects, custom metadata records, .md-meta.xml files, or reference/config data that must ship between orgs. Also trigger for admin-maintained mapping, lookup, or crosswalk tables and field mappings (\"map fields from A to B\", code lookups) — config admins change without a code deploy belongs in a CMDT, never hardcoded in Apex or Flow — and when troubleshooting CMDT record/type deploy errors. DO NOT TRIGGER for Custom Settings — route to platform-custom-setting-generate; for regular custom objects holding business records — use platform-custom-object-generate; or for secrets and API keys — recommend a Named Credential, which this skill never generates."
+description: "Use to create, generate, or validate Salesforce Custom Metadata Type metadata — the __mdt object, fields, and deployable records. Trigger on custom metadata types, CMDT, __mdt objects, .md-meta.xml files, or cross-org reference/config data; also admin-maintained mapping/lookup/crosswalk tables (config that changes without a deploy belongs in a CMDT, never hardcoded in Apex/Flow), and CMDT deploy errors. DO NOT TRIGGER for Custom Settings (use platform-custom-setting-generate), business-record objects (use platform-custom-object-generate), or secrets/API keys (use a Named Credential)."
 metadata:
   version: "1.0"
   minApiVersion: "60.0"

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

@@ -1,6 +1,6 @@
 ---
 name: platform-custom-object-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Custom Object metadata. Trigger when users mention custom objects, creating objects, object metadata, .object files, sharing models, name fields, or validation rules on objects. Also use when users say things like \"create a custom object\", \"generate object metadata\", \"set up an object for...\", or when they're troubleshooting object deployment errors especially around sharing models and Master-Detail relationships. Always use this skill for any custom object metadata work, including enriching and keeping the object's description current whenever its fields or validation rules change. Do NOT use this skill for non-Custom-Object metadata (Apex, Flows, LWC, Permission Sets, Custom Metadata Types) or for standard Salesforce objects."
+description: "Use when users create, generate, or validate Salesforce Custom Object metadata. Trigger on custom objects, .object files, sharing models, name fields, or validation rules — e.g. \"create a custom object\" — and deployment errors around sharing models and Master-Detail relationships. Also keep the object's <description> current when its fields or validation rules change. Do NOT use for non-Custom-Object metadata (Apex, Flows, LWC, Permission Sets, Custom Metadata Types) or standard objects."
 metadata:
   version: "1.1"
   domains: ["Platform"]

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

@@ -1,6 +1,6 @@
 ---
 name: platform-custom-report-type-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Custom Report Type metadata. Trigger when users mention custom report types, report types, CRTs, reporting frameworks, cross-object reports, report builder data sources, or ask to expose fields for reporting across related objects. Also use when users mention primary and related objects for reports, inner vs outer joins in reports, report type categories, or encounter deployment errors for .reportType-meta.xml files. Do NOT trigger for: running, editing, or filtering existing reports; creating report folders, dashboards, or list views; or general reporting questions that don't involve authoring a .reportType-meta.xml file."
+description: "Use to create, generate, or validate Salesforce Custom Report Type metadata. Trigger on custom report types, CRTs, cross-object reports, report builder data sources, exposing fields for reporting across related objects, inner vs outer joins in reports, report type categories, or deployment errors for .reportType-meta.xml files. Do NOT trigger for running, editing, or filtering existing reports; creating report folders, dashboards, or list views; or non-authoring reporting questions."
 metadata:
   version: "1.0"
   domains: ["Platform"]

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

@@ -1,6 +1,6 @@
 ---
 name: platform-custom-setting-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Custom Setting metadata. Trigger when users mention custom settings (hierarchy or list), customSettingsType, SetupOwnerId, per-profile/per-user config overrides, feature flags, feature toggles, kill switches, or on/off switches admins flip to enable/disable behavior, e.g. bypass triggers/automation during a data load. Also use for \"create a custom setting\" or errors like \"Cannot specify: pluralLabel for CustomSettings\" or a setting that silently deployed as a regular custom object. A trigger bypass or kill switch is just a checkbox on a hierarchy custom setting — generate ONLY the setting, never an Apex trigger/handler. DO NOT TRIGGER for Custom Metadata Types or __mdt objects — route to platform-custom-metadata-type-generate; for business-record objects — use platform-custom-object-generate; for secrets, API keys, passwords, or tokens — recommend a Named Credential, never generated here."
+description: "Use to create, generate, or validate Salesforce Custom Setting metadata. Trigger on custom settings (hierarchy/list), customSettingsType, SetupOwnerId, per-profile/per-user config overrides, feature flags/toggles, kill switches, or admin on/off switches (e.g. bypass triggers during a data load); also \"create a custom setting\" or a setting that silently deployed as a regular object. A kill switch is just a checkbox on a hierarchy setting — generate ONLY the setting, never an Apex trigger/handler. DO NOT TRIGGER for Custom Metadata Types (use platform-custom-metadata-type-generate), business-record objects (use platform-custom-object-generate), or secrets/tokens (use a Named Credential)."
 metadata:
   version: "1.0"
   minApiVersion: "60.0"

package/skills/platform-data-and-tooling-api-context-get/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-data-and-tooling-api-context-get
-description: "Authoritative field/schema reference for 2130 STANDARD Salesforce objects — use to look up standard sObject and Tooling field API names, types, properties (filterable/sortable/groupable/updateable), and relationship names for Account, Contact, Opportunity, Lead, Case, ApexClass, ApexCodeCoverage, TraceFlag, and more. Load this alongside a SOQL/query/Apex skill when the field names, types, or Filter/Sort/Group capabilities are unverified — not when the fields are already known and only query syntax or optimization is needed. TRIGGER when verifying, validating, or debugging fields in a SOQL/SOSL query or DML against a standard object — capabilities, relationship/subquery paths, or what fields an object has — so the query runs instead of guessing. Custom __c objects and __c fields are NOT in these assets; describe the live org for those (sf sobject describe). DO NOT TRIGGER for authoring/deploying *-meta.xml or sfdx source (use the Metadata API skill)."
+description: "Authoritative field/schema reference for 2130 STANDARD Salesforce objects — sObject and Tooling field API names, types, properties (filterable/sortable/groupable/updateable), and relationships for Account, Contact, Opportunity, Lead, Case, ApexClass, and more. Load alongside a SOQL/Apex skill when fields/types/capabilities are unverified — not for query syntax or optimization alone. TRIGGER when verifying/debugging fields in a SOQL/SOSL query or DML against a standard object. Custom __c objects/fields are NOT covered — describe the live org (sf sobject describe). DO NOT TRIGGER for authoring/deploying *-meta.xml or sfdx source (use the Metadata API skill)."
 metadata:
   version: "1.0"
   domains: ["Platform"]

package/skills/platform-data-manage/SKILL.md

@@ -1,14 +1,9 @@
 ---
 name: platform-data-manage
-description: "Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use platform-soql-query), Apex test execution (use platform-apex-test-run), or metadata deployment (use platform-metadata-deploy)."
+description: "Salesforce data operations with 130-point scoring. Use to create, update, delete, bulk import/export, generate test data, and clean up org records via sf CLI and anonymous Apex. TRIGGER on creating test data, bulk import/export, sf data CLI commands, data-factory patterns for Apex tests, or seeding/cleaning org records. DO NOT TRIGGER for SOQL query writing only (use platform-soql-query), Apex test execution (use platform-apex-test-run), or metadata deployment (use platform-metadata-deploy)."
 metadata:
-  cliTools:
-    - tool: ["jq"]
-      semver: ">=1.6.0"
-    - tool: ["python3"]
-      semver: ">=3.8.0"
-    - tool: ["sf"]
-      semver: ">=2.0.0"
+  version: "1.1"
+  domains: ["Platform"]
   relatedSkills:
     - "automation-flow-generate"
     - "platform-apex-generate"
@@ -17,8 +12,13 @@ metadata:
     - "platform-custom-object-generate"
     - "platform-metadata-deploy"
     - "platform-soql-query"
-  version: "1.1"
-  domains: ["Platform"]
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+    - tool: ["jq"]
+      semver: ">=1.6.0"
+    - tool: ["python3"]
+      semver: ">=3.8.0"
 ---
 
 # Salesforce Data Operations Expert (platform-data-manage)

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

@@ -1,6 +1,6 @@
 ---
 name: platform-flexipage-generate
-description: "Use this skill when users need to create, generate, modify, or validate Salesforce Lightning pages (FlexiPages). Trigger when users mention RecordPage, AppPage, HomePage, Lightning pages, page layouts, adding components to pages, or page customization. Also use when users say things like 'create a Lightning page', 'add a component to a page', 'customize the record page', 'generate a FlexiPage', or when they're working with FlexiPage XML files and need help with components, regions, or deployment errors. Always use this skill for any FlexiPage-related work, even if they just mention 'page' in the context of Salesforce. DO NOT TRIGGER when users ask about Visualforce pages, Aura components without FlexiPage context, page layout assignments in the UI, or Lightning Web Component development that does not involve placing components on a FlexiPage."
+description: "Use when users create, generate, modify, or validate Salesforce Lightning pages (FlexiPages). Trigger on RecordPage, AppPage, HomePage, Lightning pages, adding components to a page, page customization (e.g. 'customize the record page'), or .flexipage-meta.xml files (regions, components, deployment errors). DO NOT TRIGGER for Visualforce pages, page layout assignments in the UI, UI Bundle/Experience Cloud site pages, or Aura/Lightning Web Component development without FlexiPage context."
 allowed-tools: Bash Read Write
 metadata:
   version: "1.1"

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

@@ -438,4 +438,4 @@ Check for:
 - Reserved words in API names
 - Relationship limits (max 2 M-D per object)
 - Name length limits
-- Duplicate names
+- Duplicate names

package/skills/platform-metadata-api-context-get/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-metadata-api-context-get
-description: "REQUIRED companion for Salesforce metadata generation — load this schema/API-context skill in the SAME turn as ANY metadata generation skill; if you load a generator, you ALSO load this. Use it whenever you create, generate, add, edit, or author metadata or a *-meta.xml file: custom object, custom field, formula field, picklist, lookup, master-detail, validation rule, permission set, profile, custom tab, lightning record page, flexipage, list view, custom application, flow, layout, record type, sharing rules, report, and 604 Metadata API types. It provides the authoritative schema, fields, field properties, required flags, allowed enum values, and XML structure so generated *-meta.xml deploys cleanly — skipping it causes hallucinated element names and deploy failures. Trigger on *-meta.xml, metadata schema, api context, 'Salesforce metadata', or 'sfdx project'. DO NOT use for SOQL, DML, runtime sObject access, or Tooling API records."
+description: "REQUIRED companion for Salesforce metadata generation — load this schema/API-context skill in the SAME turn as ANY metadata generator (if you load a generator, you ALSO load this). Use whenever you create, generate, edit, or author metadata or a *-meta.xml file (custom object, field, flow, and 604 Metadata API types): it gives authoritative schema, required flags, and XML structure so files deploy cleanly. Trigger on *-meta.xml, metadata schema, api context. DO NOT use for SOQL, DML, runtime sObject access, or Tooling API records."
 metadata:
   version: "1.0"
   domains: ["Platform"]

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

@@ -1,6 +1,6 @@
 ---
 name: platform-metadata-retrieve
-description: "ALWAYS USE THIS SKILL to retrieve metadata from an org to your local project using the sf project retrieve start command. Supports multiple retrieval modes: retrieve all remote changes, retrieve by source directory, retrieve by metadata type with wildcards, retrieve by manifest (package.xml), or retrieve by package name. Use when the user asks to retrieve, pull, sync, or download metadata, Apex classes, custom objects, or org changes. Supports source format (default) or metadata format (ZIP). DO NOT TRIGGER for deploying metadata (use platform-metadata-deploy skill), listing metadata, or generating package.xml. NEVER use MCP tools - always use this skill and the Bash tool with sf project retrieve start."
+description: "ALWAYS USE THIS SKILL to retrieve metadata from an org to your local project with sf project retrieve start. Supports retrieval by all changes, source directory, metadata type (wildcards), manifest (package.xml), or package name, in source or metadata (ZIP) format. Use when the user asks to retrieve, pull, sync, or download metadata, Apex classes, or custom objects. DO NOT TRIGGER for deploying metadata (use platform-metadata-deploy), listing metadata, or generating a package.xml (use platform-manifest-generate). NEVER use MCP tools."
 metadata:
   version: "1.0"
   domains: ["Platform", "Developer Experience"]

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

@@ -186,4 +186,4 @@ Before deploying, verify:
 
 ## Deployment
 
-Deploy using Salesforce CLI
+Deploy using Salesforce CLI

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

@@ -1,6 +1,6 @@
 ---
 name: platform-report-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Lightning Report metadata. Trigger when users mention reports, creating reports, report metadata, .report-meta.xml files, tabular reports, summary reports, matrix reports, joined reports, report columns, report groupings, report filters, report charts, cross-filters, bucket fields, report formulas, or report time frame filters. Also use when users say things like 'create a report', 'generate a report', 'build a report on Accounts', 'add a chart to my report', or when they encounter deployment errors for .report-meta.xml files. Do NOT trigger for: creating or modifying Custom Report Type metadata (.reportType-meta.xml — use platform-custom-report-type-generate), creating dashboards, creating list views, running or viewing existing reports in the UI, or SOQL queries."
+description: "Use when users create, generate, or validate Salesforce Lightning Report metadata (.report-meta.xml) — tabular, summary, matrix, or joined reports with columns, groupings, filters, charts, cross-filters, buckets, formulas, or time-frame filters. Triggers on \"create a report\", \"build a report\", \"add a chart\", or .report-meta.xml deploy errors. Do NOT trigger for Custom Report Type metadata (use platform-custom-report-type-generate), dashboards, list views, running reports in the UI, or SOQL."
 metadata:
   version: "1.0"
   domains: ["Platform"]

package/skills/platform-salesforce-connect-adapter-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-salesforce-connect-adapter-generate
-description: "Custom Apex adapter generation for Salesforce Connect — connects any external REST API to Salesforce as live, queryable External Objects without ETL or data copying. TRIGGER when: user wants to connect a non-standard external API to Salesforce, asks to write a DataSource.Provider or DataSource.Connection, wants to surface external data as Salesforce records, says \"connect my API to Salesforce without copying data\", or asks whether custom Apex is the right approach for any system. Also trigger on: \"custom adapter\", \"ExternalId field\", \"DataSource namespace\". DO NOT TRIGGER when: user is configuring a standard adapter they already have and is NOT asking about custom Apex (e.g., OData endpoint setup, Snowflake connector config). DO NOT TRIGGER when: user wants to copy or bulk-sync data — use platform-data-manage. DO NOT TRIGGER for Apex callouts outside Connect — use platform-apex-generate or integration-connectivity-generate."
+description: "Custom Apex adapter generation for Salesforce Connect — connects any external REST API to Salesforce as live, queryable External Objects without ETL or copying. TRIGGER when: connecting a non-standard external API, writing a DataSource.Provider/Connection or a `.cls`/`.cls-meta.xml` custom adapter class, adding a `.namedCredential-meta.xml` for the adapter's callout, surfacing external data as records, \"custom adapter\", \"ExternalId field\", \"DataSource namespace\", or whether custom Apex fits. DO NOT TRIGGER when: a standard adapter is already configured (OData, Snowflake), for copy/bulk-sync (use platform-data-manage), or for Apex callouts outside Connect (use platform-apex-generate or integration-connectivity-generate)."
 metadata:
   version: "1.0"
   minApiVersion: "66.0"
@@ -26,7 +26,7 @@ Route the user through building a complete custom Salesforce Connect Apex adapte
 
 **In scope:** Generating `DataSource.Connection` and `DataSource.Provider` Apex classes, Named Credential metadata, deployment via sf CLI, and step-by-step Setup registration guidance for any REST API.
 
-**Out of scope:** Configuring standard adapters (OData, Snowflake, GraphQL — those have their own flows). Generating the External Data Source metadata file (not deployable via sf CLI — must be registered manually in Setup). Writing Apex that calls external APIs outside the Salesforce Connect framework (use [platform-apex-generate](../platform-apex-generate/SKILL.md) or [integration-connectivity-generate](../integration-connectivity-generate/SKILL.md)).
+**Out of scope:** Configuring standard adapters (OData, Snowflake, GraphQL — those have their own flows). Generating the External Data Source metadata file (not deployable via sf CLI — must be registered manually in Setup). Writing Apex that calls external APIs outside the Salesforce Connect framework (use the platform-apex-generate or integration-connectivity-generate skills).
 
 ## Before starting
 
@@ -37,11 +37,11 @@ Confirm two things. If either is missing, ask before proceeding.
 | The user wants to… | Right tool |
 |---|---|
 | Query external data live without copying it — read-only or read-write, appears as Salesforce records | **This skill** |
-| Copy or sync data into Salesforce on a schedule | [platform-data-manage](../platform-data-manage/SKILL.md) |
+| Copy or sync data into Salesforce on a schedule | the platform-data-manage skill |
 | Connect to OData, GraphQL, DynamoDB, Athena, or Cross-Org | Standard adapter setup — no Apex needed, different flow |
 | Connect to Snowflake via Salesforce's native Snowflake adapter (direct Snowflake protocol) | Built-in Snowflake adapter — no Apex needed |
 | Access Snowflake (or any database) data via a REST or HTTP API | **This skill** — Snowflake REST endpoint → custom Apex adapter |
-| Call an external API from Apex or Flow logic | [platform-apex-generate](../platform-apex-generate/SKILL.md) or [integration-connectivity-generate](../integration-connectivity-generate/SKILL.md) |
+| Call an external API from Apex or Flow logic | the platform-apex-generate skill or [integration-connectivity-generate](../integration-connectivity-generate/SKILL.md) |
 | Expose Salesforce data to an external system | [integration-connectivity-generate](../integration-connectivity-generate/SKILL.md) |
 | Receive real-time pushed data or subscribe to external events | Not Salesforce Connect — Connect is pull-only. Use Platform Events or Change Data Capture instead |
 | Sync or copy data for analytics or bulk processing | Data Cloud or ETL — Connect is zero-copy virtualization only |